Workaround bug in terminal-notifier by adding configurable timeout
Repository details (npshell)
- Project page
- npshell
- Project log category
- npshell (121 entries)
- Repository
- @joelpurra/npshell
- Owner
- @joelpurra
- Issues
- Issues on Github
- Contributors
- Contributors on Github
- Project status
- ⏲️ This project has had recent commits.
- 📂 This project is open.
- 🌠 This project is popular.
- Repository activity period
- 🗓—
- Commits
- 121 commits
- Stars
- 15 stars
Commit details (e247423f)
- Author
- Joel Purra
- Authored at
- Committer
- Joel Purra
- Committed at
Commit message
Workaround bug in terminal-notifier by adding configurable timeout
- Previously, the notifications would only work once.
- This seems to be related to
terminal-notifiernot exiting automatically after displaying the notification.- The issue is related to a bug where
terminal-notifieris waiting for the user to close or otherwise give input to the notification, as if it was an alert with actions.- The bug has not been fixed upstream since it was first reported several months ago.
- One workaround is to add a timeout, so the notification "closes itself".
- Made the timeout configurable through
configNotificationTimeout.See
Raw text
Workaround bug in terminal-notifier by adding configurable timeout - Previously, the notifications would only work once. - This seems to be related to `terminal-notifier` not exiting automatically after displaying the notification. - The issue is related to a bug where `terminal-notifier` is waiting for the user to close or otherwise give input to the notification, as if it was an alert with actions. - The bug has not been fixed upstream since it was first reported several months ago. - One workaround is to add a timeout, so the notification "closes itself". - Made the timeout configurable through `configNotificationTimeout`. See - https://github.com/julienXX/terminal-notifier/issues/223