Skip to content
This repository has been archived by the owner on Jan 16, 2023. It is now read-only.

Support _NET_WM_PID #398

Open
Earnestly opened this issue May 26, 2020 · 0 comments · May be fixed by #403
Open

Support _NET_WM_PID #398

Earnestly opened this issue May 26, 2020 · 0 comments · May be fixed by #403

Comments

@Earnestly
Copy link

When using tools like wmctrl -lp the PID for sxiv windows are displayed as 0 indicating that "the application owning the window does not support it."

For example:

$ wmctrl -lp
0x01e00001  0 0         N/A sxiv
0x0220000d  0 999255 teapot wmctrl -lp

This makes it more difficult to assign or change the window and its properties through scripts as multiple instances can't be differentiated so simply. I assume this is due to the lack of _NET_WM_PID.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant