The default setting of "10" results in a notification that remains on the screen for only about half a second. When I set lauf_notify_timeout to "100", it'll remain there for ~6 seconds. I think the problem is in lauf at line 48/53. AFAIK there is no such thing as "milaseconds". There are only milliseconds (1000ms = 1s). notify-send --help says that you has to pass the value in milliseconds. Therefore the conversion factor must be 1000.
Apart from that easy-to-fix issue I'm really enjoying your launcher!
Not sure where I came up with 60 from O.o, I must've been stoned when implementing them. I dunno... I'll burn one, then fix, and push thanks for the report.
The default setting of "10" results in a notification that remains on the screen for only about half a second. When I set lauf_notify_timeout to "100", it'll remain there for ~6 seconds. I think the problem is in lauf at line 48/53. AFAIK there is no such thing as "milaseconds". There are only milliseconds (1000ms = 1s).
notify-send --help
says that you has to pass the value in milliseconds. Therefore the conversion factor must be 1000.Apart from that easy-to-fix issue I'm really enjoying your launcher!