-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Let us set max width. *feature request* #69
Comments
Hmm. A Once #46 is fixed, you'll be able to specify width by matching on the application sending the notification or similar, would this be sufficient? |
Ping since #46 is closed. |
Another idea might be to allow notifications to shrink, instead of having a fixed width. This way you could then set the width to eg. 500 or more, and still have smaller notifications displayed nicely without much whitespace. |
@vilhalmer OK, so what about it not being a px dimension but a character count length? Then you would expand till, you reach the defined int parameter and then you would force a breakline. max-line-chars ? @Gigg1ty I don't get it, you just described the behavior that would be achieved by working max-width :D |
Not a fan of this. Doesn't play well with non-monospace fonts, duplicates functionality. |
@freed00m Um, i guess you are right 😅 But my thinking was that a |
@emersion that's true. |
Can we introduce a shrink option in mako like @Gigg1ty suggested? Let the width and height implementation remain as it is. |
Ideal would be something like dunst has, |
Yes, I too would be happy to have shrinking for the width parameter and the normal setting of width. So 300 and then anything lower gets shrunk like it would with height. |
Will this be implemented someday? |
I'm also looking forward to the day this gets implemented. |
Hi,
I use both long and short notification in terms of line lenght. I can set width but that's looking ugly for short notification.
See screenshot of what I mean, or maybe honoring the line break and calculate the lenght of the longest line?
The text was updated successfully, but these errors were encountered: