On Wednesday 23 April 2003 00:31, Dan Espen wrote: > > Stupid me - of course it seems to be possible. For example > > > > DestroyFunc FuncFvwmMaximizeFullScreen > > AddToFunc FuncFvwmMaximizeFullScreen > > + I ThisWindow (Maximized) Style $n Title, BorderWidth 4, > > HandleWidth 4 + I CondCase (NoMatch) Style $n NoTitle, BorderWidth 16, > > HandleWidth 16 + I CondCase (NoMatch) Raise > > + I CondCase (NoMatch) UpdateStyles > > + I Maximize > > > > works. Now I just need to better understand the above commands and tune > > this to make it look nice. BTW, what is that "$n" variable, I couldn't > > find it in the man page? > > I would have suggested $n but I think its not a general purpose solution. > If you have one emacs frame maximized and another not maximized, the > above will change both of them.
This is not nice. Are there any hopes for "MaximizedStyle" and "UnMaximizedStyle" commands? Another solution might be to allow the window id $[w.id] as a style name in the "Style" command. Would that be hard to implement? > It may be good enough though. I usually work with 2 xemacs frames, but > I change the second frames resource name ($r) with: > > (select-frame (make-frame '((name . "uniquename")))) The problem is that EMACS was just an example. For other applications that I run in multiple instances (e.g. rxvt) this solution is, of course, not applicable. Felix -- To contact me personally don't reply but send email to felix DOT klee AT inka DOT de -- Visit the official FVWM web page at <URL: http://www.fvwm.org/>. To unsubscribe from the list, send "unsubscribe fvwm" in the body of a message to [EMAIL PROTECTED] To report problems, send mail to [EMAIL PROTECTED]
