Repository navigation
non-main option for quick-terminal-screen configuration
#7514
Replies: 3 comments
|
The problem is then which monitor/output device should we use? On Linux at least while you can move the window to a different monitor you have to decide which one to use exactly. We could just iterate through the list of monitors and find the first one that the quick terminal isn't on, but I'm not sure if that's always what you want. A better option might be to use the monitor's connector ID like |
|
Yes, it's a good question. I guess that the "best" solution would be for the user to specify a priority list of monitor IDs and the implementation will choose the first of which which is not the current "main". But, honestly I think that would be an overkill. IMO an adequate solution will be to just iterate the monitors list in a deterministic order and choose the first one that's not the current "main". For 2-monitor setups, this solution will be always be "correct", and I think that it will also be good for the large majority of setups which use more than 2 monitors. |
|
I referenced this in a similar discussion that entails pinning the quick terminal to always appear on a specified display. #8076 |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I (and others I know) mostly use the quick terminal for calculations/checks that are related to what I'm currently doing on the "main" screen.
Therefore, I would find it very useful to have an option to show the quick terminal on a screen that is not the "main" (where the keyboard input currently is), so that it won't obstruct what's there.
All reactions