Not sure how this could be done, thus opening an issue. In the initial testing I've been doing, I like the project but there's one thing that holds me back going into this full time - operations like git commit and node and other interactive tools also show notifications which feels like spam.
Couple of solutions that immediately come to mind:
- Black List:
export NOTIFY_BLACKLIST="git push:node:nmtui".
- White List: similar to black list, but only specify commands where notifications should trigger.
- Environment Variable: This would be wonderful if possible. Elaborating below:
Use another environment variable, say NOTIFY_ENABLED, and only when it is equal to 1 should the notifications be shown. Now, I could specify a default setting in my .bashrc for this, and then use aliases to trigger these on/off on a per command basis if I see fit. Example:
# bashrc begins
# set it to enabled by default
$ export NOTIFY_ENABLED=1
# set aliases
$ alias notoff="export NOTIFY_ENABLED=0"
$ alias noton="export NOTIFY_ENABLE=1"
# bashrc over.
# run commands
$ notoff; node; noton;
# Or something similar.
Not sure how this could be done, thus opening an issue. In the initial testing I've been doing, I like the project but there's one thing that holds me back going into this full time - operations like
git commitandnodeand other interactive tools also show notifications which feels like spam.Couple of solutions that immediately come to mind:
export NOTIFY_BLACKLIST="git push:node:nmtui".Use another environment variable, say
NOTIFY_ENABLED, and only when it is equal to 1 should the notifications be shown. Now, I could specify a default setting in my.bashrcfor this, and then use aliases to trigger these on/off on a per command basis if I see fit. Example: