me again :)
this is most likely a river only bug, as the window manager is responsible for handling surfaces & the screen.
i want to just inform you about this issue.
https://github.com/riverwm/river/issues/574
if you set the anchor=bottom-right in fnott.ini, new notifications will stack up from the bottom to the top.
when there is no more space for the next notification, river will crash panic with integer overflow.
what i wanted to ask you.. how much work would it require to add a config option like max-notifications to display only a certain number of notifications ?
mako is doing it in a clever way to display notifications until max is reached, then adds a notification below with the count of additional notifications eg: (4 more). clicking notifications loops through all remaining ones & displays them.
see:
me again :)
this is most likely a river only bug, as the window manager is responsible for handling surfaces & the screen.
i want to just inform you about this issue.
[https://github.com/riverwm/river/issues/574](https://github.com/riverwm/river/issues/574)
if you set the `anchor=bottom-right` in fnott.ini, new notifications will stack up from the bottom to the top.
when there is no more space for the next notification, river will crash panic with integer overflow.
**what i wanted to ask you..** how much work would it require to add a config option like `max-notifications` to display only a certain number of notifications ?
mako is doing it in a clever way to display notifications until max is reached, then adds a notification below with the count of additional notifications eg: `(4 more)`. clicking notifications loops through all remaining ones & displays them.
see:
