2009/3/15 jpwe...@imonk.com:
This has been bugging me for a few weeks and I haven't figured
out what happened or how to fix it. It used to work until recently
and it still works at my employer (on redhat) but not my current
ubuntu at home.
With
Style * SnapAttraction 12
I've moved this discussion to a separate thread.
jpwe...@imonk.com wrote:
On Sun, Mar 15, 2009 at 12:44:27AM +0100, Dominik Vogt wrote:
On Sat, Mar 14, 2009 at 12:24:57PM -0700, jpwe...@imonk.com wrote:
On Sat, Mar 14, 2009 at 12:15:03AM +0100, Dominik Vogt wrote:
On Tue, Mar 10, 2009
My email service got got messed up yesterday so I am sending this message again.
The fvwm mail archive appears to be way behind, so I can't tell it it
went though.
I've switched my subscription to a gmail account.
On Sun, Mar 15, 2009 at 12:44:27AM +0100, Dominik Vogt wrote:
On Sat, Mar
On Sun, Mar 15, 2009 at 07:00:05PM +, Mikhael Goikhman wrote:
On 15 Mar 2009 00:34:16 +0100, Dominik Vogt wrote:
[snip]
To be interactive the module should both listen to fvwm and to the input
(mouse, keyboard) in the same event loop. Don't you agree?
Yes. And why does this rule
I've found the lists.math.uh.edu archive which is not the same as
what is shown on the fvwm.org page. Apparently my emails did
show up, but I haven't been receiving them at my gmail or my
older account.
Perhaps the fvwm.org contact page needs to be updated to get the
proper archive and any other
16 Mar 2009 01:11:21 -
@@ -2076,8 +2076,23 @@
/* snap to screen egdes */
if ((fw-snap_mode SNAP_SCREEN) fw-snap_proximity 0)
{
+ /* TA: 20090315: Make sure windows being told to snap to a
+ * screen; honour Xinerama screens separately -- and don't
+ * treat the screen area as one
