"Go to..." functions behaviour

[KalleStenberg]

Type: Bug

I have two different machines I use with VS Code. I have turned on Settings Sync and have tried to the best of my ability to verify that the settings are identical on both machines. Same extensions as well.
On machine 1: I right click a function call (where the function is defined in the same file) in my Python code and select "Go to Definition" (or press F12), and the editor jumps me to the defined function inside the same tab that I was in. This is the desired result I am looking for.
On machine 2 however, when I do this same procedure the editor instead opens a NEW tab (with the same file) in preview mode. I do not want this.
The Preview settings and Go to Location settings are identical (again, as far as I can see) on both machines, so why are they behaving differently?

VS Code version: Code 1.86.0 (0504748, 2024-01-31T10:28:19.990Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item	Value
CPUs	12th Gen Intel(R) Core(TM) i7-12850HX (24 x 2419)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled
Load (avg)	undefined
Memory (System)	31.61GB (20.81GB free)
Process Argv	--crash-reporter-id eef7c005-7a67-4fad-8545-5a90e02beadd
Screen Reader	no
VM	0%

Extensions (13)

Extension	Author (truncated)	Version
gitlens	eam	14.7.0
qlik	Gim	0.5.0
todo-tree	Gru	0.0.226
git-graph	mhu	1.30.0
autopep8	ms-	2023.8.0
debugpy	ms-	2024.1.10371006
pylint	ms-	2023.10.1
python	ms-	2024.0.1
vscode-pylance	ms-	2023.12.1
autodocstring	njp	0.6.1
postman-for-vscode	Pos	0.18.0
intellicode-api-usage-examples	Vis	0.2.8
vscodeintellicode	Vis	1.2.30

A/B Experiments

vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscoreces:30445986
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:30899288
c4g48928:30535728
azure-dev_surveyone:30548225
vscrp:30673768
962ge761:30951796
pythongtdpath:30769146
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
pythontestfixt:30902429
pythonregdiag2:30936856
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
accentitlementsc:30887149
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
dsvsc019bcf:30953938
d34g3935:30958340
b5d27386:30958190
3ef8e399:30949928
e3gdj431:30958358

[KalleStenberg]

I figured it out. It behaved like that because the files I was working on was on a virtual drive.
For different reasons my code needed to have a specific path, so I mounted a folder to a new drive using the subst.exe command. When I then tried to go to the definition of a function VSCode wanted to open the actual real path to the file instead of the "fake" one on the virtual drive.
I don't know if this is something worth "fixing" or adding support for, but this issue I consider to be done. Sorry!