Just annotations of little "how to's", so I know I can find how to do something I've already done when I need to do it again, in case I don't remember anymore, which is not unlikely. Hopefully they can be useful to others, but I can't guarantee that it will work, or that it won't even make things worse.
Dealing with gxmessage windows on wmctrl
Posted 01-12-2020 at 04:25 PM by the dsc
If you ever see yourself wanting to manipulate gxmessage dialogs/windows with wmctrl for some reason, you may notice the name of the window set by gxmessage itself is kind of ignored, depending on the parameters you'd use on wmctrl. It will instead still behave as if the window title was "Gxmessage," or yet "gxmessage.Gxmessage," depending on wmctrl parameters. Which is troublesome if you have more than one.
I thought it would be needed to grep the title from a "wmctrl -l" listing and then strip out what's not the window ID, but there's at least one simple solution:
But the title apparently CANNOT be given as a variable, such as:
For whatever reason, it won't work that way. Maybe without the quotes? I don't know.
I thought it would be needed to grep the title from a "wmctrl -l" listing and then strip out what's not the window ID, but there's at least one simple solution:
Code:
wmctrl -F -a "CaSe-SeNsitivE custom gxmessage title" -b add,skip_taskbar
Code:
gxmtitle="CaSe-SeNsitivE custom gxmessage title" wmctrl -F -a "$gxmtitle" -b add,skip_taskbar
Total Comments 0