-
-
Notifications
You must be signed in to change notification settings - Fork 122
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
actions: add "loop" variants of "switch-{next,previous,left,right,up,down}" #787
Conversation
Thanks @davvid! This would need to be an option though (e.g. in preferences) to enable/disable this behaviour. It doesn't "feel" right to me, although maybe it's just because I prefer, and am used to the original behaviour. Others might like this though, so would consider accepting this if it's made a user option (with default behaviour as it is currently). Cheers, Jay. |
Reach out if you need a hand in adding this to preferences! |
Just adding this here for context as to why wrap-around was not implemented previously: #278 |
Alrighty, I added a preference for the loop-around so that it's opt-in. Thanks for the context. I updated everything except for Thanks for being open to adding this feature. cheers! |
This works fine as is, so from my side would be fine to merge (after generating the schema). |
Would it make sense to add this as a different action (no default keybinding) instead of a setting?
On February 21, 2024 5:21:52 PM UTC, Matthias Seiffert ***@***.***> wrote:
This works fine as is, so from my side would be fine to merge (after generating the schema).
--
Reply to this email directly or view it on GitHub:
#787 (comment)
You are receiving this because you are subscribed to this thread.
Message ID: ***@***.***>
--
To respect your time, I try to write short, functional emails.
|
I thought I was doing something wrong here as I couldn't get this to work. Then I realised this works for From the description I would expect this to also work for I guess it comes down to if this behaviour (if enabled) only makes sense for |
This is another option, and would have been much easier to implement (sorry @davvid!). I guess keybinds would allow uses to assign keybinds for both use cases (or just one by replacing the defaults if you always wanted wrap around). See comment #787 (comment) - keybinds would make more sense here (keybinds for |
Good stuff, yeah these do feel like distinct actions. I'll take a stab at that when I get a chance later this or next week. Another nice thing is we won't need to change the schemas or add more options to the UI. |
3cf4f3d
to
6c77e4a
Compare
I've split these out to separate actions and regenerated the schemas. Let me know what you think. |
…down}" The "switch-next", "switch-prev" and related actions currently do nothing once they reach the last window in the action's direction. Add "loop" variants of these actions that loop around when the last window is reached. The new actions are "switch-previous-loop", "switch-next-loop", "switch-left-loop", "switch-right-loop", "switch-up-loop" and "switch-down-loop".
6c77e4a
to
e785ef1
Compare
generally referred to as "wrap around" in PaperWM).
Thanks @davvid - just reordered and simplified keybind descriptions. Planning on merging this one into develop and doing a release for this soon. |
The "switch-next", "switch-prev" and related actions currently do
nothing once they reach the last window in the action's direction.
Add "loop" variants of these actions that loop around when the last
window is reached.
The new actions are "switch-previous-loop", "switch-next-loop",
"switch-left-loop", "switch-right-loop", "switch-up-loop" and
"switch-down-loop".