Tobias Ellinghaus (2017-Apr-01, excerpt):
> We had an issue with fvwm2 a while ago, it was due to broken scripts
> shipped with it or something like that. See
> http://fvwm.org/documentation/manpages/fvwm.html
> and search for "urgency hint". It will tell you how to fix your system.
After all it was a setup of my machine instead of a DT bug. FVWM does
not have a taskbar, and thus lacks canonical means to display urgency.
So one has to resort to other solutions. For me, the following
addition fixed it:
~$ grep -A10 urgent .fvwm/config
# Don't give focus to windows that wanna be "urgent", but instead
# display a message via notification deamon, xmessage, or stdout, or
# do nothing.
DestroyFunc UrgencyFunc
AddToFunc UrgencyFunc
+ I exec notify-send 'Urgent: $[w.name]'
#+ I exec xmessage '$[w.name]'
#+ I echo 'Urgent: $[w.name]'
#+ I Nop
Thak you very much!
Stefan
--
http://stefan-klinger.de o/X
Send plain text messages only, not exceeding 32kB. /\/
\
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]
