Closed frazar closed 2 years ago
I'm sorry I merged the previous PR prematurely. __done_notification_transient
is not even in the README and it is enabled by default. Do we even need this option?
IMHO not, but we just wanted to add a backwards compatibility layer in case this broke somebody's workflow. But you can remove it, yes.
@frazar would you like to remove this check completely in your PR? Thanks!
@frazar would you like to remove this check completely in your PR? Thanks!
Sure! Should be ok now
Since the default behavior is changing, shouldn't it be mentioned in the docs?
Since the default behavior is changing, shouldn't it be mentioned in the docs?
I will add it at least to the release notes.
I wonder if it makes sense to put it in the readme, since transient notifications are the way it was always supposed to work. One concern is wether this option might prevent some users from configuring some notification from remaining in the screen. I would imagine some systems allow users to configure this or not at all?
I might be misremembering. I just checked and have mine set to never expire in my mako
config.
I think in general the config files for each notification daemon would take precedence so it should be OK
Fixes #117