search

nikitamalinov / vscode

Visual Studio Code
https://code.visualstudio.com
MIT License
0 stars 0 forks source link

Floating Window Navigation #1

Open nikitamalinov opened 7 months ago

nikitamalinov commented 7 months ago

I would like to request floating windows behave (in terms of navigation) as if it were it's own workspace, per se.

Meaning:

As a user, if I execute the command workbench.action.focusFirstEditorGroup I expect the focus be shifted to the currently active window's first editor group, regardless if it's a floating window or not.

Currently what happens is if I have Window A, say we call it window_for_source_editing where text is typed, and I then I also have Window B (a floating window of the same workspace) in a different monitor, say called window_for_terminal_and_outputs where window_for_terminal_and_outputs.groups[1] is a terminal in an editor area, and window_for_terminal_and_outputs.groups[0] is text output of some kind based on launched executable

To visualize:

window_for_source_editing

Window for Source Editing ------------ file1.rs file2.rs
src
file1.rs
file2.rs

window_for_terminal_and_outputs

Floating Window
someoutput.txt pwsh
-----------------------------------
foobar PS: ~/Home>Get-❚

When my cursor is actively focused on the terminal in window_for_terminal_and_outputs.groups[1] and I press CTRL+1 my brain intuitively thinks it will navigate to window_for_terminal_and_outputs.groups[0]

Instead I have to calculate where I'm at, which floating window (also consider more than 1 floating window exists) has or doesn't have that a particular group editor, it's too much thought for something that feels like it should be intuitively done based on my previous uses of vscode.

I have reviewed previous issues and the only one related I could find is https://github.com/microsoft/vscode/issues/196266

I would argue, if anything, this illuminates the need for a workspace/user setting configuration for this to toggle how editor related sizing/groups/navigation happen within floating windows since I don't want what https://github.com/microsoft/vscode/issues/196266 wants and it would be safe to assume those types of users don't want what I want

The reason this feels so unintuitive for me personally is because windows are usually managed by a window manager (or you just already have your certain OS's keybinds baked into memory), so I would think most developers are using window management keybinds to switch between windows (which these technically are). My vote is that that problem is already solved in terms of switching back and forth between floating windows and so the focus/navigation should be window aware

So the ask is to add a configuration setting to opt-in to how this currently works, defaulting to what I consider the more 'intuitive' way, or vice versa

gitauto-ai[bot] commented 7 months ago

Click the checkbox below to generate a PR!

You have 5 requests left in this cycle which refreshes on 2024-05-25 03:05:12. If you have any questions or concerns, please contact us at info@gitauto.ai.

ghost commented 7 months ago

Click the checkbox below to generate a PR!

You have 30 requests left in this cycle which refreshes on 2024-05-18 23:54:13. If you have any questions or concerns, please contact us at info@gitauto.ai.