starred/komorebi
1
0
Fork 0
mirror of https://github.com/LGUG2Z/komorebi.git synced 2026-01-11 14:40:25 +01:00
Code Issues 87 Packages Projects Releases 10 Wiki Activity

[FEAT]: monocle should apply to layout, not single window #173

New Issue
Closed
opened 2026-01-05 14:48:44 +01:00 by adam · 2 comments
adam commented 2026-01-05 14:48:44 +01:00
Owner
Copy Link

Originally created by @edgimar on GitHub (Jan 13, 2023).

I want to be able to set a workspace's layout to 'monocle' (maybe have a workspace-layout <mon> <ws> monocle command?) and then to be able to cycle focus between windows on that workspace, causing the next or previous window to be on top and fully maximized. Currently the toggle-monocle command appears to apply to a single window, and after it is activated, doing something like cycle-focus next does not change to a different window on the workspace.

Furthermore, when in this mode, focus <dir> should just cycle the windows of the workspace (e.g. with left/right and up/down both mapped to prev/next).

(I'm using version 0.1.14)

Originally created by @edgimar on GitHub (Jan 13, 2023). I want to be able to set a workspace's layout to 'monocle' (maybe have a `workspace-layout <mon> <ws> monocle` command?) and then to be able to cycle focus between windows on that workspace, causing the next or previous window to be on top and fully maximized. Currently the `toggle-monocle` command appears to apply to a single window, and after it is activated, doing something like `cycle-focus next` does not change to a different window on the workspace. Furthermore, when in this mode, `focus <dir>` should just cycle the windows of the workspace (e.g. with left/right and up/down both mapped to prev/next). (I'm using version 0.1.14)
adam added the enhancement label 2026-01-05 14:48:44 +01:00
adam closed this issue 2026-01-05 14:48:44 +01:00
adam commented 2026-01-05 14:48:45 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Jan 16, 2023):

Hey @edgimar, my memory is a little hazy so I can't remember exactly when this functionality was added, but the desired behaviour that you're describing works for me on the master branch and if it's not in 0.1.14 it will definitely make it into 0.1.15.

@LGUG2Z commented on GitHub (Jan 16, 2023): Hey @edgimar, my memory is a little hazy so I can't remember exactly when this functionality was added, but the desired behaviour that you're describing works for me on the `master` branch and if it's not in 0.1.14 it will definitely make it into 0.1.15.
adam commented 2026-01-05 14:48:45 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Feb 19, 2023):

v0.1.15 has been released.

@LGUG2Z commented on GitHub (Feb 19, 2023): v0.1.15 has been released.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.1.36
apps-behaving-badly
bug
bug
cannot-reproduce
documentation
enhancement
github_actions
i-am-stuck
i-will-definitely-work-on-this
i-will-not-work-on-this
i-will-probably-work-on-this
komorebi
komorebi-bar
komorebic
performance
pull-request
Mirrored from GitHub Pull Request
 translation
No Label enhancement
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#173
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?