Exclude xmore notification from `notification_limit` count

[etrnal70]

This is something that bothers me for quite some time. I think xmore shouldn't count as normal notification because it's size is also smaller than the normal one. I believe most user also expect to have the n number of notification in notification_limit with xmore as additional info. Or maybe add an option to exclude it ?

[sewnie]

have you tried urgency/rules in dunstrc?

[etrnal70]

Can you show me some examples ? I thought rules can only be applied to notifications from application

[fwsmit]

I can understand the current implementation isn't the most logical one. So to make the problem clear, here's an example: notification_limit = 2

dunstify "n1"
dunstify "n2"

Which results in both implementations in:

[n1]
[n2]

But when you add 1 more notification, things get weird

dunstify "n3"

Current behaviour:

[n1]
[xmore]

Expected behaviour:

[n1]
[n2]
[xmore]

I don't think this can be fixed with rules

[etrnal70]

I see. Is this planned to be fixed in the future ?

[fwsmit]

No I don't have any plans about that.

[fwsmit]

About the proposed behaviour vs current behaviour, I don't think either one is necessarily more logical, since with the proposed behaviour you will show 3 notifications with a xmore notification instead of showing an actual notification that might fit in the same space. Maybe it would be more logical to have a maximum window height and show an xmore notification if the height is exceeded.

[bynect]

I think adding a proper warning in the documentation of notification_limit is enough