[BUG]: double monocle a lone window on a desktop results in it having no container #339

Closed
opened 2026-01-05 14:49:51 +01:00 by adam · 1 comment
Owner

Originally created by @raggi on GitHub (Apr 14, 2024).

Describe the bug

If you toggle monocle twice on a window that is the sole window in the sole workspace on a monitor, the toggle on/off works (after the fix for the panic described in #757), but the monitor is left with no workspace, and the window is left orphaned, so it can no longer be focused by commands.

To Reproduce
Steps to reproduce the behavior:

  1. Open a single window on a single monitor
  2. Toggle monocle twice
  3. Focus a window on a second monitor
  4. Observe inability to focus original window, as there is no container in that direction
  5. Focus the orphaned window, observe inability to focus windows in other directions due to "no container"

Expected behavior
The window should have a container after it is restored from monocle.

Additional context
There is some kind of logic bug that would cause a panic, that is described in #757, that will be fixed independently - but may now further hide the bug.

Originally created by @raggi on GitHub (Apr 14, 2024). **Describe the bug** If you toggle monocle twice on a window that is the sole window in the sole workspace on a monitor, the toggle on/off works (after the fix for the panic described in #757), but the monitor is left with no workspace, and the window is left orphaned, so it can no longer be focused by commands. **To Reproduce** Steps to reproduce the behavior: 1. Open a single window on a single monitor 2. Toggle monocle twice 3. Focus a window on a second monitor 4. Observe inability to focus original window, as there is no container in that direction 5. Focus the orphaned window, observe inability to focus windows in other directions due to "no container" **Expected behavior** The window should have a container after it is restored from monocle. **Additional context** There is some kind of logic bug that would cause a panic, that is described in #757, that will be fixed independently - but may now further hide the bug.
adam added the bug label 2026-01-05 14:49:51 +01:00
adam closed this issue 2026-01-05 14:49:51 +01:00
Author
Owner

@LGUG2Z commented on GitHub (Apr 21, 2024):

@RaptDept this is technically "fixed" here, but the fix could be improved:

6fce630be5

@LGUG2Z commented on GitHub (Apr 21, 2024): @RaptDept this is technically "fixed" here, but the fix could be improved: https://github.com/LGUG2Z/komorebi/commit/6fce630be537bbeeb50ad38287843a5d12f60d08
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#339