Regression: files opened from command line (incl. PDF viewers for SyncTeX) opening in a fixed window

[ghost]

Since the latest update, any files opened from the command with MacOS' open or the code executable itself do not anymore open in the previously active window/workspace (let alone a reasonable window as proposed in #76262): they open in some fixed window (first one in the list?). This makes VSCode completely unusable in combination with the command line. Moreover, that window keeps collecting a large list of Source Control Providers corresponding to all the files that were wrongly opened in it, instead of the window corresponding to that project.

Related to the rejected enhancement #76262 which proposed to improve the command line integration—now with this regression any pretension of being able to open files from the command line at all has been completely lost. Or one can only have a single window and single workspace open.

Addition: It's also 200% impossible to use VSCode with a SyncTeX backward search from PDF documents: the files open again in the fixed window instead of the one already containing the document or that was previously active.

[ghost]

Since file open dialogs are clumsy compared to the command line, the best way to open files in VSCode now is code -n filename and then drag-and-drop the file from the newly opened window to the correct window. Very clumsy!

[ghost]

And so it goes again. Bugs are ignored, being functional does not matter, only instagrammability does. Back to good old terminal-based editors of the age my path then goes.

[ghost]

Stack Overflow is a hostile joke, by the way.

[ghost]

Fuck you jerks.