> On Thu, Aug 12, 2010 at 10:03:01AM +0200, Michael Großer wrote: > > I cannot find any displayable man page. > > But, I found some kind of source file named "FvwmEvent.1.in". > > There, I found: > > Download the file -- the direct link to the raw file is here: > > http://github.com/ThomasAdam/fvwm/raw/49a53ee408cba26f7649fc4b56df0d309b485cfd/modules/FvwmEvent/FvwmEvent.1.in > > Then you have to actually run "man" over it: > > man ./FvwmEvent.1.in > > I am especially keen for you to do this, so I can ensure my troff skills > are > still OK. I know troff fairly well. :)
Yeah, now I see it. I have to enter > man ./FvwmEvent.1.in to see the man page. If I only enter > man FvwmEvent.1.in then I see nothing, because the "./" is essential... Well, I see a table with the events and the triggers. This is good. Well done. > > Are you sure that a WM_CLASS property causes both the res_class > > and the res_name event? I don't know so much about this WM_XXX stuff, > > but if I think logically, shouldn't it mean WM_NAME in the > > second event? If not, what is the difference between > > res_class and res_name? Why two events have to exist? Why > > not one? Or is one of them an alias of the other? > > No, I mean WM_CLASS -- that holds two properties therein: > > The resource name and the class name. Go see the ICCCM2. > Here I still think, that someting is wrong. I looked at ICCCM2 http://tronche.com/gui/x/icccm/sec-4.html#s-4.1.2.5 http://tronche.com/gui/x/icccm/sec-4.html#s-4.1.2.1 and detected that two properties WM_CLASS and WM_NAME are existing. In your new man page, I see: * res_class --> WM_CLASS * res_name --> WM_CLASS Why not "res_name --> WM_NAME"? I cannot see the logic... Michael
