It doesn't appear that the built-in Style command appname string (which accepts '*' & '?' wildcards; see mlvwm(1) manual page) can match against the WM_WINDOW_ROLE X window property. I believe it currently only matches against WM_CLASS or WM_NAME.
There are many X11 applications that have different types of windows which should have different styles, including the menu bar itself as well as various window features. For example, Claws Mail has WM_CLASS(STRING) = "claws-mail", "Claws-mail" set on all windows, but the WM_WINDOW_ROLE differs by the various window types:
The main account/mailbox view has WM_WINDOW_ROLE(STRING) = "mainwindow"
A new message has WM_WINDOW_ROLE(STRING) = "compose"
Opening an existing message has WM_WINDOW_ROLE(STRING) = "messageview"
A window with a mainwindow role should have different menu bar options than messageview or compose. So, it'd be very helpful to be able to define multiple Style commands for the same WM_CLASS, but differing WM_WINDOW_ROLE.
It appears that WM_WINDOW_ROLE is part of the ICCCM specification, see section 5. Session Management.
It doesn't appear that the built-in
Style
commandappname
string (which accepts '*' & '?' wildcards; see mlvwm(1) manual page) can match against theWM_WINDOW_ROLE
X window property. I believe it currently only matches againstWM_CLASS
orWM_NAME
.There are many X11 applications that have different types of windows which should have different styles, including the menu bar itself as well as various window features. For example, Claws Mail has
WM_CLASS(STRING) = "claws-mail", "Claws-mail"
set on all windows, but theWM_WINDOW_ROLE
differs by the various window types:WM_WINDOW_ROLE(STRING) = "mainwindow"
WM_WINDOW_ROLE(STRING) = "compose"
WM_WINDOW_ROLE(STRING) = "messageview"
A window with a
mainwindow
role should have different menu bar options thanmessageview
orcompose
. So, it'd be very helpful to be able to define multipleStyle
commands for the sameWM_CLASS
, but differingWM_WINDOW_ROLE
.It appears that
WM_WINDOW_ROLE
is part of the ICCCM specification, see section 5. Session Management.