-
Notifications
You must be signed in to change notification settings - Fork 222
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lnotify 0.3.4 is incompatible with procps-ng 3.3.12 #339
Comments
@kevr I think this is your plugin. What is the |
I wonder if we should: (a) just remove it:
Or (b) make it user configurable? I'm not clear what the intent is here (e.g., as currently written, this code will suppress notifications whenever I'm using an |
I have the same issue fwiw @larsks |
The python "lnotify" plugin had some problematic code that would suppress notifications if the active window was named "tilda", "xterm", or "gnome-terminal". This list was not user-configurable, and the code implementing this feature was broken due to weechat#339 (incompatible with common versions of ps) and weechat#334 (python3 bytes-vs-string incompatibility). This commit removes the problematic code. Closes: weechat#334 Closes: weechat#339
Yes, I would say so. The choice of window titles seems completely I would be quite surprised if anyone is actually relying on this (now |
The
lnotify
script usesps
to determine the name of the currently running window, but it uses command line arguments that are not supported by the version ofps
in many distributions. The generate command line looks like:And fails like this:
Note this is a different failure than the one reported in #334.
The text was updated successfully, but these errors were encountered: