Stop overwriting notifications timeout #226

Closed
opened 2025-10-14 15:43:10 -06:00 by navan · 0 comments
Owner

Originally created by @freswa on 7/31/2024

Here is a hardcoded timeout value set for all notifications. Usually there is a setting in the notification daemon, that handles the duration. Is there any particular reason this is hardcoded and not left to the notification daemon?

*Originally created by @freswa on 7/31/2024* [Here](https://github.com/ulyssa/iamb/blob/main/src/notifications.rs#L85) is a hardcoded timeout value set for all notifications. Usually there is a setting in the notification daemon, that handles the duration. Is there any particular reason this is hardcoded and not left to the notification daemon?
navan closed this issue 2025-10-14 15:43:11 -06:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github/iamb#226
No description provided.