You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is both the option to force the active window to be float'ed or to unmanage it completely. However, if the window is closed and reopened (for example, child windows of an application), it goes back to being managed.
I suggest the ability to signal to Komorebi to not manage that window again for the current session.
This functionality slightly overlaps with the komorebic ignore-rule ... command, so I have a couple suggestions for how it could work. Commands for ignore could be duplicated/subbed for the float related commands.
Add new command: komorebic toggle-ignore-rule
Add an option to unmanage: komorebic unmanage --session komorebic toggle-float --session
New command/add an option to ignore-rule: komorebic ignore-rule-active [title|exe|etc...] komorebic ignore-rule active komorebic ignore-rule --active
etc..
One of my pain-points for Komorebi is when applications open child windows that I have no desire to be managed or tiled due to them being a message-type, dialog, or modal type of window. However, the process for figuring out the title, exe, or class for that widow is a massive distraction to whatever I'm working on. I can already utilize the unmanage and toggle-float commands, but many of these types of windows are opened repeatedly in a short time-span, which makes it increasingly frustrating.
Of course, I have the option for creating my own shell-script to find the active window, get whatever property, then issue the correct komorebic command to add a rule, but this feels like a feature that should be included.
Alternatives Considered
Checked to make sure both toggle-float and unmanage do not persist for the current session.
Currently in the process of writing a little shell script to automate this for the short-term.
The text was updated successfully, but these errors were encountered:
Feature requests on this repository are only open to current GitHub sponsors on the $5/month tier and above, people with a valid individual commercial use license, and approved contributors.
This issue has been automatically closed until one of those pre-requisites can be validated.
@Pugsworth Can you drop me an email at the address listed on the licensing page from the email associated with your license so that I can verify your GitHub handle? I don't see your GitHub handle associated with an active license, but I do see a few active licenses without associated GitHub handles 👀
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Eligibility
Individual Commercial Use License
Suggestion
There is both the option to force the active window to be float'ed or to unmanage it completely. However, if the window is closed and reopened (for example, child windows of an application), it goes back to being managed.
I suggest the ability to signal to Komorebi to not manage that window again for the current session.
This functionality slightly overlaps with the
komorebic ignore-rule ...
command, so I have a couple suggestions for how it could work. Commands for ignore could be duplicated/subbed for the float related commands.Add new command:
komorebic toggle-ignore-rule
Add an option to unmanage:
komorebic unmanage --session
komorebic toggle-float --session
New command/add an option to ignore-rule:
komorebic ignore-rule-active [title|exe|etc...]
komorebic ignore-rule active
komorebic ignore-rule --active
etc..
One of my pain-points for Komorebi is when applications open child windows that I have no desire to be managed or tiled due to them being a message-type, dialog, or modal type of window. However, the process for figuring out the title, exe, or class for that widow is a massive distraction to whatever I'm working on. I can already utilize the unmanage and toggle-float commands, but many of these types of windows are opened repeatedly in a short time-span, which makes it increasingly frustrating.
Of course, I have the option for creating my own shell-script to find the active window, get whatever property, then issue the correct komorebic command to add a rule, but this feels like a feature that should be included.
Alternatives Considered
Checked to make sure both
toggle-float
andunmanage
do not persist for the current session.Currently in the process of writing a little shell script to automate this for the short-term.
The text was updated successfully, but these errors were encountered: