You are not logged in.
Is there a way to have, for instance, the summary style in bold?
We could have some tag to put in the format line, for example "<b>%s</b> %b"
No, currently not. But it might get added in the future.
@everyone:
I've implemented the separator for notifications. Here are the relevant options:
[separator]
#enable drawing of separator line
enable = no
#width of separator line in relation to window width
width = 0.8
#height of separator line in relation to line height
height = 0.3
# color can either be "foreground" to use the foreground color or
# "auto" to generate a fitting color depending on the background color
color = auto
And on a different note: if there are notifications you don't want to get displayed at all, you can create a rule which sets the format to "" (empty string) .
Offline
Hey Knopwob,
I just updated dunst-git and I can now use the separator. It looks really good, but there's one "complaind":
The spacing between the text and the separator is a bit too much for my taste. I have set Dunst to use the same font as I have in DWM, so the notification nicely overrides the bar. When I get two notifications, however, the first notification gets 'stretched' because of the spacing between the text and the separator and suddenly is higher than my statusbar.
Also, there's a slightly unclear explanation in the config.def.h:
int line_height = 0; /* a line height < font height will be raised to font height */
Shouldn't that be like "If line height < font height, it will be raised to font height".
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
The spacing between the text and the separator is a bit too much for my taste. I have set Dunst to use the same font as I have in DWM, so the notification nicely overrides the bar. When I get two notifications, however, the first notification gets 'stretched' because of the spacing between the text and the separator and suddenly is higher than my statusbar.
The separator (foreground + background) has the same height as a line with text. Within the configs you can only change the dimensions of the foreground line, not the background.
Do you want the height of the background (and with that the height of the whole line) to be configurable as well?
Also, there's a slightly unclear explanation in the config.def.h:
int line_height = 0; /* a line height < font height will be raised to font height */
Shouldn't that be like "If line height < font height, it will be raised to font height".
Yes, your version sounds clearer. I'll change that. Thank you
Offline
Do you want the height of the background (and with that the height of the whole line) to be configurable as well?
Yes please. Preferable, I'd like it if I could set a separator 1px under the current "end" of the notification.
Yes, your version sounds clearer. I'll change that. Thank you
Great, finally I contributed some
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
Hi, I've been using Dunst for a bit, it's wayy cleaner-looking than having lots of different notifications (Pidgin and Skype for example have their own little bubble-types) I like
I've got a small gripe, and that's when I make dunst appear on my 2nd monitor (With mouse/keyboard follow, or simply telling it to appear on it instead of the first one) It doesn't appear.
I think this is because my right monitor is slightly lower physically (And therefore set slightly lower in Xorg settings) And so Dunst appears a couple of inches 'above' my screen (Level with the left monitor's top edge). Is this something that can be worked around in Dunst, or something I'm going to have to fix in my own display settings?
EDIT:
Weirdly this issue disappears with the -git version, but not the normal version!
I updated to -git after reading about the seperator update, so I guess this is a none-issue
Last edited by Reded (2012-09-09 06:13:56)
"Some humans would do anything to see if it was possible to do it. If you put a large switch in some cave somewhere, with a sign on it saying "End-of-the-World Switch. PLEASE DO NOT TOUCH", the paint wouldn't even have time to dry."
Offline
Hi, I've been using Dunst for a bit, it's wayy cleaner-looking than having lots of different notifications (Pidgin and Skype for example have their own little bubble-types) I like
I've got a small gripe, and that's when I make dunst appear on my 2nd monitor (With mouse/keyboard follow, or simply telling it to appear on it instead of the first one) It doesn't appear.
I think this is because my right monitor is slightly lower physically (And therefore set slightly lower in Xorg settings) And so Dunst appears a couple of inches 'above' my screen (Level with the left monitor's top edge). Is this something that can be worked around in Dunst, or something I'm going to have to fix in my own display settings?
EDIT:
Weirdly this issue disappears with the -git version, but not the normal version!
I updated to -git after reading about the seperator update, so I guess this is a none-issue
It's not weird at all. There have been some bugfixes in that regard since that version
The next release will come out when I'm finished with the linewrapping stuff which hopefully will happen within the next 1-2 weeks.
Offline
knopwob wrote:Do you want the height of the background (and with that the height of the whole line) to be configurable as well?
Yes please. Preferable, I'd like it if I could set a separator 1px under the current "end" of the notification.
I'm currently thinking about scrapping the current design of the separator and make it just one constant line through the whole line length. Like a border around the message but only at the bottom. The old separator may look nice but it needs too much configuration options.
I've already experimented with frames around the notifications but that always looked ugly when two notifications have different colors.
EDIT: I've implemented the new separator. This is incompatible to the old config format. Sorry for that
Last edited by knopwob (2012-09-09 09:04:14)
Offline
I'm currently thinking about scrapping the current design of the separator and make it just one constant line through the whole line length. Like a border around the message but only at the bottom. The old separator may look nice but it needs too much configuration options.
I've already experimented with frames around the notifications but that always looked ugly when two notifications have different colors.
EDIT: I've implemented the new separator. This is incompatible to the old config format. Sorry for that
Yes! This is perfect! Thank you Knopwob
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
Hey Knopwob,
I just noticed you had released 0.4.0 so I thought I'd update the git version I use. However, it doesn't seem to work. When I relaunch dunst and use notify-send, it just shows the standard blue dunst message in the top-left corner. I figured it might be my config.h so I started fresh with a new config.def.h, but still the same result. Can you take a look and see if anything's wrong? Here's my config.h:
EDIT: Nevermind, I just started with a fresh PKGBUILD from AUR and it seems to work now. Weird
Last edited by Unia (2012-09-27 14:59:57)
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
Hey Knopwob,
I just noticed you had released 0.4.0 so I thought I'd update the git version I use. However, it doesn't seem to work. When I relaunch dunst and use notify-send, it just shows the standard blue dunst message in the top-left corner. I figured it might be my config.h so I started fresh with a new config.def.h, but still the same result. Can you take a look and see if anything's wrong? Here's my config.h:
EDIT: Nevermind, I just started with a fresh PKGBUILD from AUR and it seems to work now. Weird
It sounds like you have a default dunstrc lying around somewhere which dunst picked up. You can disable the reading of config files complety by building dunst with:
CFLAGS=-DSTATIC_CONFIG make
Offline
Unia wrote:Hey Knopwob,
I just noticed you had released 0.4.0 so I thought I'd update the git version I use. However, it doesn't seem to work. When I relaunch dunst and use notify-send, it just shows the standard blue dunst message in the top-left corner. I figured it might be my config.h so I started fresh with a new config.def.h, but still the same result. Can you take a look and see if anything's wrong? Here's my config.h:
EDIT: Nevermind, I just started with a fresh PKGBUILD from AUR and it seems to work now. Weird
It sounds like you have a default dunstrc lying around somewhere which dunst picked up. You can disable the reading of config files complety by building dunst with:
CFLAGS=-DSTATIC_CONFIG make
Nope, I had already done that. I've never even touched a dunstrc
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
knopwob wrote:Unia wrote:Hey Knopwob,
I just noticed you had released 0.4.0 so I thought I'd update the git version I use. However, it doesn't seem to work. When I relaunch dunst and use notify-send, it just shows the standard blue dunst message in the top-left corner. I figured it might be my config.h so I started fresh with a new config.def.h, but still the same result. Can you take a look and see if anything's wrong? Here's my config.h:
EDIT: Nevermind, I just started with a fresh PKGBUILD from AUR and it seems to work now. Weird
It sounds like you have a default dunstrc lying around somewhere which dunst picked up. You can disable the reading of config files complety by building dunst with:
CFLAGS=-DSTATIC_CONFIG make
Nope, I had already done that. I've never even touched a dunstrc
Oh well, as long as it works now
Offline
Exactly
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
Hi.
I get a "There's already another notification-daemon running" when I try to start dunst. I've already removed xfce4-notifyd.
If I type notify-send some message at the console the message does pop up however.
What other notification daemon might be running?
Offline
Hi.
I get a "There's already another notification-daemon running" when I try to start dunst. I've already removed xfce4-notifyd.
If I type notify-send some message at the console the message does pop up however.What other notification daemon might be running?
Install and run htop and see if another notifier is running. Maybe you could also run killall notification-daemon, but not sure on that.
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
Install and run htop and see if another notifier is running. Maybe you could also run killall notification-daemon, but not sure on that.
I don't see anything related to notifications in htop.
From running killall notification-daemon I get notification-daemon: no process found
Offline
Dunst behaves same way as, for example, xfce4-notifyd. It means that you don't need to start it at all, since it's recieving notifications through dbus using org.freedesktop.Notifications interface.
Offline
So how do I check to see if it's running properly?
Offline
So how do I check to see if it's running properly?
notify-send "If you read this from Dunst, it's running properly"
Obviously, run that from a terminal emulator
Last edited by Unia (2012-10-04 17:35:00)
If you can't sit by a cozy fire with your code in hand enjoying its simplicity and clarity, it needs more work. --Carlos Torres
Offline
porcupene wrote:So how do I check to see if it's running properly?
notify-send "If you read this from Dunst, it's running properly"
Obviously, run that from a terminal emulator
Never mind that, I just received a notification for an email in Thunderbird. Dunst works! Thanks people!
One last question: is there a way to make the notifications not disappear until clicked? It's the main reason I replaced xfce4-notifyd since it only allows a maximum time of 480 seconds before the notifications disappear.
Offline
Yes, this can be configured in dunstrc.
cp /usr/share/dunstrc ~/.config/dunst/dunstrc
For an example.
Offline
I think I have found some odd behaviour with one line geometry.
I haven't updated dunst for some time, so I decided to do fresh compile of aur package and adapt config to new options and changes.
The problem:
a) If I send 10 notifications with same text one after another, there is no hidden indicator until I close one notification (I think this is intended, but it makes no sense neither in one line mode or standard geometry).
The next one (same text) shows hidden count, but it shows only 6 hidden, instead of 8.
b) Sometimes after idle timeout in config and after sending notifications from a) notification pops out of nothing showing age even though I'm using computer at the time.
c) I send 10 different notifications (numbers 1 through 10), and only first one is shown, and after closing it other 9 notifications never show up.
d) Sometiimes sending notification just closes one that is already shown .
e) History only shows the last one - it doesn't cycle.
For this I have used completely stock config, except for geometry which is "0x1-100+0".
3x30 default geometry works as expected. Only thing that would IMHO make more sense is showing hidden count on the first notification after sending new one that is same as already displayed one (a).
@porcupene, there are timeout variables in config, just below colors.
EDIT: on version from community with x1 geometry sending new notification just closes previously shown one and history bind most of the time does nothing.
Last edited by Šaran (2012-10-05 14:35:20)
Offline
This is fantastic! I tried some of the dzen-based notifications out there, but they were usually troublesome to set up so I just went back to my current solution (colibri). dunst was very easy to use (just install and run) and the configuration straightforward. I love the "follow keyboard focus" feature. Thank you for sharing this knopwob!
Some questions/requests I came up with while using it:
1. [Request] A -dock option (like dzen) would be nice, I filed an issue here: https://github.com/knopwob/dunst/issues/68
2. [Request] Would it be possible to specify color in "format"? I want different colors for my %s and %b, however, I realize that it's not that easy to add since it would clash with the colors specified by urgency. There are different solutions to this, but I'm not sure what the best (simplest) one is.
3. How are the keybindings supposed to work? Are they "global" shortcuts, or do they only function if dunst has focus? I can't get them to work but it's probably because of my system (xmonad + custom layout), it'll make it easier to investigate if I understood it better.
4. In the rules section, I set some notifications to be marked as critical. I expected those to have timeout = 0 (as specified in [urgency_critical]), but it seems like they get the normal timeout = 10. Is that intended or should I file an issue?
5. [Request] What do you think about the possibility to set a custom separator color instead of just "foreground" and "auto"?
(I use dunst 0.4.0 from [community].)
Again, thank you for your excellent work!
Offline
Keybinds are global, and they get interpreted just fine on my system running monsterwm.
I think 4. is a bug.
Offline
@Saran: I'll look into your Issues later today/tomorrow. I'm currently pretty busy.
This is fantastic! I tried some of the dzen-based notifications out there, but they were usually troublesome to set up so I just went back to my current solution (colibri). dunst was very easy to use (just install and run) and the configuration straightforward. I love the "follow keyboard focus" feature. Thank you for sharing this knopwob!
I'm glad you like it.
Some questions/requests I came up with while using it:
1. [Request] A -dock option (like dzen) would be nice, I filed an issue here: https://github.com/knopwob/dunst/issues/68
I'll look into it this weekend.
2. [Request] Would it be possible to specify color in "format"? I want different colors for my %s and %b, however, I realize that it's not that easy to add since it would clash with the colors specified by urgency. There are different solutions to this, but I'm not sure what the best (simplest) one is.
This might happen at some point, but it's no priority atm. I have too look into how much work it would be to integrade this into the way dunst renders the text.
3. How are the keybindings supposed to work? Are they "global" shortcuts, or do they only function if dunst has focus? I can't get them to work but it's probably because of my system (xmonad + custom layout), it'll make it easier to investigate if I understood it better.
The dunst window doesn't need to have the focus for the keybindings to work. If you run dunst manually in a terminal it should print an error if one of its keybindings conflicts with other programs.
The keybindings to close notifications obviously only work when notifications are displayed but the history key should always work. (As long as there are notifications in the history. Dunst only keeps the history in ram. In other words: the history is lost after you restart dunst)
4. In the rules section, I set some notifications to be marked as critical. I expected those to have timeout = 0 (as specified in [urgency_critical]), but it seems like they get the normal timeout = 10. Is that intended or should I file an issue?
It should work as you expect it. Does the rule match at all? Are for example the colors for urgent notifications applied to that notification? Posting your dunstrc might help as well.
5. [Request] What do you think about the possibility to set a custom separator color instead of just "foreground" and "auto"?
I thought about it, but the setting would have to be added to every point where you can change colors. E.g. to every urgency tupe and to the rules. I was just too lazy to implement this and hoped that nobody would want that feature
Maybe I'll do this this weekend... maybe...
Offline