There's a small file descriptor leak in CMD_Exec() in fvwm/builtins.c;
it opens /dev/null, dup2()s it to standard input, and then never closes
the original file descriptor before exec'ing the command.
The neurotically correct fix for this (in what I think is the right
fvwm coding style) is:
I have the Mouse configuration setup of (among other things):
# move window with mouse 2 on an icon or a titlebar
Mouse 2 IT NMove
In fvwm 2.4.20, the window move is initiated immediately when button 2
is pressed. In fvwm 2.5.30 (and CVS) for me, the move is delayed and
I can't seem to turn off a user state for a specific window in a
function in fvwm 2.5.30. Here is an exerpt from my current testing
fvwm-2.5.30 configuration file:
Style * State 1
*FvwmEvent: iconify ZapIconPlacement
*FvwmEvent: deiconify ZapState
I wrote:
| This doesn't happen for other buttons, eg I also have 'Mouse 1
| T N Move' and if I use mouse button 1 on window titles they move
| immediately without waiting for button-up.
I was mistaken about what I had button 1 bound to, which has led me
to a workaround. If you have the Move in
On Tue, Jul 27, 2010 at 04:55:52PM -0400, Chris Siebenmann wrote:
I wrote:
| This doesn't happen for other buttons, eg I also have 'Mouse 1
| T N Move' and if I use mouse button 1 on window titles they move
| immediately without waiting for button-up.
I was mistaken about what I had
On Tue, Jul 27, 2010 at 01:00:24PM -0400, Chris Siebenmann wrote:
[.. other stuff snipped..]
So, either I'm missing something about fvwm 2.5.30, or there's a bug
here. All things considered, the first is probably more likely -- does
anyone have any ideas?
UpdateStyles? Shouldn't be needed
On Tue, Jul 27, 2010 at 06:08:59PM -0400, Chris Siebenmann wrote:
| On Tue, Jul 27, 2010 at 01:00:24PM -0400, Chris Siebenmann wrote:
|
| [.. other stuff snipped..]
|
| So, either I'm missing something about fvwm 2.5.30, or there's a bug
| here. All things considered, the first is
