Federico Angelilli
Federico Angelilli
@winkelnp @v4n00 do you think the way I fix this in #1521 is sensible?
> Seems sensical to me, though I am very much less than familiar with the code base. I've tested on my machine and it seems to work (at least sending...
> Does the trick :) Nice. I will merge 👍
I guess that's an historical legacy. Ideally the timestamp would be milliseconds since epoch
Backward compatibility and portability permitting, this could reasonably be reworked
sorry for the late reply. did you find something new about this?
weird. I suppose this is a problem with dbus-send? dunst itself only receives the dbus message containing a uint32, so the parsing is not done by us
Thanks, I merged the pr since it was very straightforward
I immagined something like that. We don't really care about octal I guess. Maybe someone could want to use hexadecimal? but even then, I prefer to print a clear error...
I don't think this can be done directly using dunst's configuration. You could write a script that reloaded the dunst configuration (with monitor option modified) when a fullscreen app is...