Originally created by @da-rth on GitHub (Oct 29, 2021).
Originally assigned to: @LGUG2Z on GitHub.
This should perhaps be an on-going ticket as we discover more necessary window rules which should be applied when starting komorebi.
Currently, some example floating window rules are present in komorebi, however, a number of additional float-rules specific to both Windows 10 and Windows 11 could be applied - along with some developer-specific window rules for IDEs such as Jetbrains/Code etc. If anyone has a window rule which they believe should be added as a sane default, please include it within this discussion.
With the potential implementation of regex pattern matching based window rules (#60), I would like to propose the following rules be added to komorebi.sample.ahk
Additionally, it would be quite good to have rules for as many popular minimise-to-tray apps as possible.
Originally created by @da-rth on GitHub (Oct 29, 2021).
Originally assigned to: @LGUG2Z on GitHub.
This should perhaps be an on-going ticket as we discover more necessary window rules which should be applied when starting komorebi.
Currently, some example floating window rules are present in komorebi, however, a number of additional float-rules specific to both Windows 10 and Windows 11 could be applied - along with some developer-specific window rules for IDEs such as Jetbrains/Code etc. If anyone has a window rule which they believe should be added as a sane default, please include it within this discussion.
With the potential implementation of regex pattern matching based window rules (#60), I would like to propose the following rules be added to `komorebi.sample.ahk`
```
# Firefox / Chrome Picture-in-picture
komorebic.exe float-rule --title "Picture-in-picture"
# Jetbrains IDE pop-up windows
komorebic.exe float-rule --class "jetbrains-(.*)" --title "Welcome to (.*)"
komorebic.exe float-rule --class "jetbrains-(.*)" --title="Go to Line/Column"
komorebic.exe float-rule --class "jetbrains-(.*)" --title="Rename"
komorebic.exe float-rule --class "jetbrains-(.*)" --title="Open Project"
komorebic.exe float-rule --class "jetbrains-(.*)" --title="win0"
komorebic.exe float-rule --class "jetbrains-(.*)" --title="Welcome to (.*)"
# Task Manager
komorebic.exe float-rule --exe "taskmg.exe"
```
Additionally, it would be quite good to have rules for as many popular minimise-to-tray apps as possible.
Definitely in favour of having the sample config file catch as many rough edges as possible!
Do the current float rules for IntelliJ popups and Task Manager not work as expected (or are they different on Windows 11?)
@LGUG2Z commented on GitHub (Oct 29, 2021):
Definitely in favour of having the sample config file catch as many rough edges as possible!
Do the current float rules for [IntelliJ](https://github.com/LGUG2Z/komorebi/blob/master/komorebi.sample.with.lib.ahk#L36) popups and [Task Manager](https://github.com/LGUG2Z/komorebi/blob/master/komorebi.sample.with.lib.ahk#L38) not work as expected (or are they different on Windows 11?)
Here's one for the little blue MS Teams Notification box that appears on the bottom right hand corner of the screen when a new message comes through. Worked on W10. Can't speak to W11, but assume it's the same title and would work just fine.
; Always float Teams Notifications, matching on title
Run, komorebic.exe float-rule title "Microsoft Teams Notifications", , Hide
@xSTUDDSx commented on GitHub (Jan 8, 2022):
Here's one for the little blue MS Teams Notification box that appears on the bottom right hand corner of the screen when a new message comes through. Worked on W10. Can't speak to W11, but assume it's the same title and would work just fine.
```
; Always float Teams Notifications, matching on title
Run, komorebic.exe float-rule title "Microsoft Teams Notifications", , Hide
```
Based on some discussions in the Discord, I am working on adding a configuration generator to komorebi-core and exposing it through komorebic. This is intended to be used with a central repository (or forked personal repositories) containing options that are known to be required for different applications to run seamlessly with komorebi.
I have started populating this repository based on my own komorebi.ahk file.
The CLI can be run against the YAML file containing the applications that you want to generate rules for (probably all of them, just in case), and the resulting file is output to $KOMOREBI_HOME and can be included at the top of your komorebi.ahk file.
This way, we have to rely less on a sample file commited to the repo for applicaiton window rules and just focus on a set of key bindings for the main functionality that will be familiar to most people with previous twm experience, and the documentation can reflect where the latest application window rule definitons can be sourced from and generated.
@LGUG2Z commented on GitHub (Apr 3, 2022):
Based on some discussions in the Discord, I am working on adding a [configuration generator](https://github.com/LGUG2Z/komorebi/commit/09a24b89e540f6f228c9031a8bd26cbc028807de) to `komorebi-core` and exposing it through `komorebic`. This is intended to be used with a central repository (or forked personal repositories) containing options that are known to be required for different applications to run seamlessly with `komorebi`.
[I have started](https://github.com/LGUG2Z/komorebi-application-specific-configuration/blob/master/applications.yaml) populating this repository based on my own `komorebi.ahk` file.
The CLI can be run against the YAML file containing the applications that you want to generate rules for (probably all of them, just in case), and the resulting file is output to `$KOMOREBI_HOME` and can be included at the top of your `komorebi.ahk` file.
This way, we have to rely less on a sample file commited to the repo for applicaiton window rules and just focus on a set of key bindings for the main functionality that will be familiar to most people with previous twm experience, and the documentation can reflect where the latest application window rule definitons can be sourced from and generated.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @da-rth on GitHub (Oct 29, 2021).
Originally assigned to: @LGUG2Z on GitHub.
This should perhaps be an on-going ticket as we discover more necessary window rules which should be applied when starting komorebi.
Currently, some example floating window rules are present in komorebi, however, a number of additional float-rules specific to both Windows 10 and Windows 11 could be applied - along with some developer-specific window rules for IDEs such as Jetbrains/Code etc. If anyone has a window rule which they believe should be added as a sane default, please include it within this discussion.
With the potential implementation of regex pattern matching based window rules (#60), I would like to propose the following rules be added to
komorebi.sample.ahkAdditionally, it would be quite good to have rules for as many popular minimise-to-tray apps as possible.
@LGUG2Z commented on GitHub (Oct 29, 2021):
Definitely in favour of having the sample config file catch as many rough edges as possible!
Do the current float rules for IntelliJ popups and Task Manager not work as expected (or are they different on Windows 11?)
@xSTUDDSx commented on GitHub (Jan 8, 2022):
Here's one for the little blue MS Teams Notification box that appears on the bottom right hand corner of the screen when a new message comes through. Worked on W10. Can't speak to W11, but assume it's the same title and would work just fine.
@LGUG2Z commented on GitHub (Apr 3, 2022):
Based on some discussions in the Discord, I am working on adding a configuration generator to
komorebi-coreand exposing it throughkomorebic. This is intended to be used with a central repository (or forked personal repositories) containing options that are known to be required for different applications to run seamlessly withkomorebi.I have started populating this repository based on my own
komorebi.ahkfile.The CLI can be run against the YAML file containing the applications that you want to generate rules for (probably all of them, just in case), and the resulting file is output to
$KOMOREBI_HOMEand can be included at the top of yourkomorebi.ahkfile.This way, we have to rely less on a sample file commited to the repo for applicaiton window rules and just focus on a set of key bindings for the main functionality that will be familiar to most people with previous twm experience, and the documentation can reflect where the latest application window rule definitons can be sourced from and generated.