You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not a bug report against a single script, more a comment about some of the notification scripts in the repo. There are a lot of them, many for various use cases, but also many similar for the same uses cases, and many of them doesn't work properly.
I tested all the scripts I could find which create notifications on the local machine on Linux. Most of them didn't work properly, so here are some findings:
anotify.py, notify.py, weenotify.py
I experienced all of these consistently causing WeeChat to hang when running /quit. I had to kill WeeChat with sigkill. All of these use the notify2 library in python, so there's probably some issue with using this in WeeChat. Not sure if it's some specific issue on my machine or if it has to do with the versions used. Tested on Arch Linux with WeeChat 2.9, Python 3.8.5 and notify2 0.3.1.
lnotify.py
Calls xdotool and ps in a blocking way. I have experienced WeeChat hanging with this because xdotool ran into some error and ran for a long time. Error messages from xdotool is also printed directly to stdout, which causes garbled display in WeeChat (until you press ctrl-l).
notify_send.pl
Calls an executable which is defined in the config with the arguments you want to pass for buffer name, message, etc., but passes each word as a separate argument to the executable, so I couldn't get it to work properly. E.g. the default command notify-send $type: $name &>/dev/null is excecuted as notify-send '$type:' '$name' '&>/dev/null', which makes notify-send error with the message "Invalid number of options.". It also calls notify-send in a blocking way, so it may hang WeeChat.
chanotify.py
Only supports IRC. Apart from that, seems to be the only of these scripts which actually work properly.
notifym.pl
Only supports IRC. It also calls notify-send in a blocking way, so it may hang WeeChat.
windicate.py
Seems to only support Ubuntu, so I didn't test this. But I see that it calls wmctrl and python in a blocking way.
inotify.py, notification.py
Only supports Python 2.
Triggers
I also tested the trigger in the wiki, and that works great, both for IRC and other messages.
Maybe some of the scripts should be removed from the repo?
WeeChat version: 2.9
The text was updated successfully, but these errors were encountered:
lnotify.py and all of the other local notification scripts for linux in
the repo have issues (see weechat/scripts#433),
so recommend the trigger in the wiki instead, which seems to work great.
That's a very good report. I do like to use notification scripts in weechat, and I noticed the same issue while using anotify.py
I was trying to figure out the cause of the problem but it seems to require a deeper understanding of weechat.
I hope we can find a work around soon.
This is not a bug report against a single script, more a comment about some of the notification scripts in the repo. There are a lot of them, many for various use cases, but also many similar for the same uses cases, and many of them doesn't work properly.
I tested all the scripts I could find which create notifications on the local machine on Linux. Most of them didn't work properly, so here are some findings:
anotify.py, notify.py, weenotify.py
I experienced all of these consistently causing WeeChat to hang when running
/quit
. I had to kill WeeChat with sigkill. All of these use the notify2 library in python, so there's probably some issue with using this in WeeChat. Not sure if it's some specific issue on my machine or if it has to do with the versions used. Tested on Arch Linux with WeeChat 2.9, Python 3.8.5 and notify2 0.3.1.lnotify.py
Calls
xdotool
andps
in a blocking way. I have experienced WeeChat hanging with this becausexdotool
ran into some error and ran for a long time. Error messages fromxdotool
is also printed directly to stdout, which causes garbled display in WeeChat (until you press ctrl-l).notify_send.pl
Calls an executable which is defined in the config with the arguments you want to pass for buffer name, message, etc., but passes each word as a separate argument to the executable, so I couldn't get it to work properly. E.g. the default command
notify-send $type: $name &>/dev/null
is excecuted asnotify-send '$type:' '$name' '&>/dev/null'
, which makesnotify-send
error with the message "Invalid number of options.". It also callsnotify-send
in a blocking way, so it may hang WeeChat.chanotify.py
Only supports IRC. Apart from that, seems to be the only of these scripts which actually work properly.
notifym.pl
Only supports IRC. It also calls
notify-send
in a blocking way, so it may hang WeeChat.windicate.py
Seems to only support Ubuntu, so I didn't test this. But I see that it calls
wmctrl
andpython
in a blocking way.inotify.py, notification.py
Only supports Python 2.
Triggers
I also tested the trigger in the wiki, and that works great, both for IRC and other messages.
Maybe some of the scripts should be removed from the repo?
The text was updated successfully, but these errors were encountered: