FVWM: style command ignored

2011-02-02 Thread Pierre Frenkiel
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, titl

Re: FVWM: style command ignored

2011-02-02 Thread Thomas Adam
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

FVWM: Focus Policy Issue with Java Application

2011-02-02 Thread Joe Riel
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 Pol

Re: FVWM: Focus Policy Issue with Java Application

2011-02-02 Thread Thomas Adam
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 d

Re: FVWM: Focus Policy Issue with Java Application

2011-02-02 Thread Thomas Adam
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 i

Re: FVWM: Focus Policy Issue with Java Application

2011-02-02 Thread Thomas Adam
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