FVWM: style command ignored
hi, I have in my fvwm config several "style" lines like this one: Style "program" NoTitle, NoHandles, Sticky, WindowListSkip, NeverFocus and up to now, they all worked perfectly. A fex days ago, I added the clock program "buici-clock", and the style for this program is ignored (not sticky, title present, ...) I imagined that the dash in the name could be the cause, but the problem remains if I remove the dash (changing accordingly the program name of course) Has anybody an explanation? version : fvwm 2.5.30 running on debian Squeeze regards, -- Pierre Frenkiel
Re: FVWM: style command ignored
On Wed, Feb 02, 2011 at 03:44:45PM +0100, Pierre Frenkiel wrote: > hi, > I have in my fvwm config several "style" lines like this one: > > Style "program" NoTitle, NoHandles, Sticky, WindowListSkip, NeverFocus Style BuiciClock !Title, !Handles, Sticky, WindowListSkip, Neverfocus This matches on the class name. > and up to now, they all worked perfectly. > A fex days ago, I added the clock program "buici-clock", and the style > for this program is ignored (not sticky, title present, ...) Likely the ordering of your style lines is meaning this is being overriden. I'd need to see your config. -- Thomas Adam
FVWM: Focus Policy Issue with Java Application
A particular java-based application I use frequently (Maple) does not work well in fvwm. I use focus-follows-mouse, but when I move the mouse into the application it does not get the focus (the window is selected, but keystrokes do nothing). The java application has (from fvwm-ident): Focus Policy: Globally Active - Input Field: False - WM_TAKE_FOCUS: Present To get the application to respond to the keyboard, I have to select a menu item. Is there a way to fix this? Is this an fvwm-specific issue? The focus works fine if I use the application in Gnome desktop (configured with focus-follows-mouse). -- Joe Riel
Re: FVWM: Focus Policy Issue with Java Application
On Wed, Feb 02, 2011 at 07:49:16AM -0800, Joe Riel wrote: > A particular java-based application I use frequently (Maple) > does not work well in fvwm. I use focus-follows-mouse, but > when I move the mouse into the application it does not > get the focus (the window is selected, but keystrokes do nothing). > The java application has (from fvwm-ident): > > Focus Policy: Globally Active > - Input Field: False > - WM_TAKE_FOCUS: Present > > To get the application to respond to the keyboard, I have to select a > menu item. See the "Leniene" style option. -- Thomas Adam
Re: FVWM: Focus Policy Issue with Java Application
On Wed, Feb 02, 2011 at 03:52:06PM +, Thomas Adam wrote: > On Wed, Feb 02, 2011 at 07:49:16AM -0800, Joe Riel wrote: > > A particular java-based application I use frequently (Maple) > > does not work well in fvwm. I use focus-follows-mouse, but > > when I move the mouse into the application it does not > > get the focus (the window is selected, but keystrokes do nothing). > > The java application has (from fvwm-ident): > > > > Focus Policy: Globally Active > > - Input Field: False > > - WM_TAKE_FOCUS: Present > > > > To get the application to respond to the keyboard, I have to select a > > menu item. > > See the "Leniene" style option. s/Leniene/Lenience/ -- Thomas Adam
Re: FVWM: Focus Policy Issue with Java Application
On Wed, Feb 02, 2011 at 09:13:44AM -0800, Joe Riel wrote: > I didn't get InitialMapCommand to do anything. Echo is supposed to > print to stderr, but I don't see the message when launching the > application from the command line. Well, that would typically be in ~/.xsession-errors if X redirects there. Or somewhere else if you've explicitly sent STDERR from FVWM somewhere else (doubtful). But really, just because there might have been a typo on a given line, or you wanted to see if something had worked, the suggestion of using InitialMapCommand from me was a bit of a red herring, because the options to the style command are tokenised and run or skipped depending if something's wrong. Hence it's perfectly possible for you to do this: Style foo opfdkjfd, fdjkjlk, Sticky, l, InitialMapCommand Beep And still hear a beep for window "foo", regardless of the obvious errors on that line. That then doesn't guarantee that "opfdkjfd" worked, or was supposed to. But note that the question was meaningless anyway; you would have gotten an error to STDERR (heh -- see above as to where that might get logged). No news from FVWM is typically good news for things like style parsing -- beyond that, there's other ways of tracking down problems where you think things should be working but aren't. -- Thomas Adam -- "It was the cruelest game I've ever played and it's played inside my head." -- "Hush The Warmth", Gorky's Zygotic Mynci.
