Skip to content
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

Allow follow mode to be modified by the rule #770

Open
DusanLesan opened this issue Oct 26, 2020 · 4 comments
Open

Allow follow mode to be modified by the rule #770

DusanLesan opened this issue Oct 26, 2020 · 4 comments
Labels

Comments

@DusanLesan
Copy link

The use case I want is to have monitor = 0 for all notifications except for those that match the rule. I want those to follow the keyboard. Basically I want to mark status bar notifications to follow keyboard but other notifications to remain on primary screen to preserve privacy in case of screen sharing

Example:

[date]
    summary = "date"
    format = "<span stretch="semiexpanded" size="15000">%b</span>"
    background = "#383a3b"
    follow = keyboard
@tsipinakis
Copy link
Member

To do this dunst needs to be able to handle multiple window/display setups simultaneously. Since a basic assumption is that there is only 1 notification window this would take a lot of effort to implement currently.

I'll keep this open, but I don't expect this to be picked up soon.

@fwsmit fwsmit added this to the v2.0 milestone Jun 7, 2021
@DusanLesan
Copy link
Author

@tsipinakis @fwsmit I have another idea that might make this issue obsolete if it is possible. I would like to use dunstctl to control follow value during runtime (no saving in config). We would probably need two dunstctl commands, one to get config entry value (or just follow) and one to set it. That would allow me to control Dunst from my wm. For example I would use it like so:
[ "$(dunstctl get follow)" = "keyboard" ] && dunstctl set follow "none" || dunstctl set follow "keyboard"

@fwsmit
Copy link
Member

fwsmit commented Oct 23, 2021

It would be cool to set variables via dunstctl, but I think multiple windows has a higher priority, since that solves more issues. You can, of course, already do the same thing in a hacky way by changing the config file and restarting dunst.

@DusanLesan
Copy link
Author

@fwsmit Please keep this idea in mind as it may be useful for cases other than following. Regarding the hacky solution, I am already doing that since I created the issue. In my case I only need to kill dunst as it is started automatically when needed.

@fwsmit fwsmit removed this from the v2.0 milestone Apr 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants