Score:0

Description of window properties modified by wmctrl

I found wmctrl allows for changing some "properties" of windows:

wmctrl -r <WIN> -b ( add | remove | toggle),prop1 [,prop2 ]
 Add, remove, or toggle up to two window properties simultaneously. The window that is being  
 modified must be identified with a -r action. The property change is achived by using the 
 request. The supported property names (for prop1 and prop2) are modal, sticky, maximized_vert,
 maximized_horz, shaded, skip_taskbar, skip_pager, hidden, fullscreen, above and below. Two
 properties are supported to allow operations like maximizing a window to full screen mode. 
 Note that this action is made up of exactly two shell command line arguments.

Is there any detailed description of what is each of these properties, and how does changing them affect windows behavior?
Some are obvious, and/or can be easily understood by tinkering a bit, but some are not. In any case, an official description is desirable. The only thing I found (not official) is https://blog.spiralofhope.com/1042/wmctrl-user-documentation-examples.html

Jacob Vlijm avatar
by flag
Those are not so much a wmctrl - properties, but referring to application window properties (x). Think they are all listed here as far as I can see (further below): https://specifications.freedesktop.org/wm-spec/1.3/ar01s05.html.
Score:0
pk flag

EDIT: I read a bit further at this specification and if this doesn't answer your Questions, I would only suggest to crawl through the Source-Code.

For Example

_NET_WM_STATE_SKIP_TASKBAR indicates that the window should not be included on a taskbar. This hint should be requested by the application, i.e. it indicates that the window by nature is never in the taskbar. Applications should not set this hint if _NET_WM_WINDOW_TYPE already conveys the exact nature of the window.

I think you should also note that not every Window-Manager ships with the same behaviour.

sancho.s ReinstateMonicaCellio avatar
Your *here* tells exactly the same as the link I posted, and your *there* is simply `man`. None of them gives any more detail. `man -P cat x | grep skip_` shows nothing, so I guess that is also not helpful.
sancho.s ReinstateMonicaCellio avatar
Will check that. On a quick view, the explanation does not seem very illuminating. At any rate, I suggest editing the answer, instead of adding valuable info in comments.
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.