An alternative to have things done automagically would be to add the
line
applyrules(c);
after
updatetitle(c);
in propertynotify() in dwm.c
You can then do all sorts of fun things to your windows (dynamically)
by momentarily changing their titles.
On May 27, 2009, at 1:46 AM, Anselm R Garbe wrote:
Hi,
the problem is that R sets the properties at a later point (once the
window has been mapped).
I propose to add the following key handler to your config.h
static void reapplyrules(const Arg *arg) {
Client *c;
for(c = clients; c; c = c->next)
applyrules(c);
}
And bind that to something like Mod1-r. This will reapply all rules to
all windows when executed (might be handy for other things as well).
Kind regards,
Anselm
2009/5/27 Wu, Yue <vano...@gmail.com>:
On Tue, May 26, 2009 at 03:05:57PM +0200, yy wrote:
2009/5/26 Jeremy Jay <dinkuma...@gmail.com>:
I guess I should have been more explicit:
{ NULL, NULL, "R Graphics", 0, True },
Then,
{ NULL, NULL, "R", 0, True },
should have worked. It probably didn't because the window title is
set
after rules have been applied. It is amazing that after a dozen
messages we still don't know which is the class of the window, and
in
particular if setting it to the right value in the rules fix the
problem. No issue about rules should be answered before knowing the
output of:
xprop |awk '
/^WM_CLASS/{sub(/.* =/, "instance:"); sub(/,/, "\nclass:");
print}
/^WM_NAME/{sub(/.* =/, "title:"); print}'
Kind regards,
PS: Sorry for editing the subject, but I think wmii guys will be
thankful.
--
- yiyus || JGL .
Thanks for advice, the result of command says:
title: "R Graphics: Device 2 (ACTIVE)"
So I tried:
{ NULL, NULL, "R Graphics: Device 2 (ACTIVE)",
0, True },
But it still doesn't work :( And the problem with "R Graphics:
Device 2
(ACTIVE)"(assume if it works) is that 2 can be changed to other
number, so I
have to create as much rules as the number range can be used, so
it's not so
practical.
