sorin-ionescu / irssi-growl Goto Github PK

It would be way better to deal with notifications in a forked process so Irssi doesn't stop waiting until a timeout occurs.

https://github.com/shabble/irssi-docs/wiki/Guide#wiki-Dealing_with_Blocking_IO

When receiving a Highlighted Message, the notification consists only of a colon (:) as in this screenshot: http://cloud.oishiide.su/2y252w3v242a3O1W0J2J

Hi,

I have found a problem with se-latin1 and 1.0.6. When i get a MSG in private or in public with åäö i get "growl: Could not notify, connection refused."

Regards
Jonas Byström

Apparently the Growl::GNTP has a fairly high connection timeout and irssi runs the script in the main irssi thread. Thus when the script sends a notification to a host that doesn't respond the call to Growl::GNTP will hang, and whole irssi will freeze, for the duration of the timeout. The timeout seems to be 3min, at least for me.

Would it be possible to either run the notification in another thread? Or decrease the timeout somehow? User kfdms similar project kfdm/irssi-growl seems to circumvent the problem by checking the connection before calling Growl::GNTPs notify.