Re: Nautilus-Fvwm interaction

2001-05-10 Thread Paul D. Smith
I read the bug referenced in the URL, and also the bugs that _that_ bug references, etc. It seems pretty clear that the Nautilus guy is a reasonable fellow, and he wants to do the right thing, but it also seems clear that he feels the ICCCM blesses the behavior he's using. As I understand it,

Re: Nautilus-Fvwm interaction

2001-05-10 Thread Michael Han
On Thu, May 10, 2001 at 12:20:10AM -0400, Paul D. Smith wrote: Here's a relevant passage from [EMAIL PROTECTED] in the response to bug #7823: http://bugzilla.eazel.com/show_bug.cgi?id=7823 My reading of the ICCCM is that if WM_HINTS.input is false, but WM_PROTOCOLS includes

Re: Patch to FvwmEvent to use hex

2001-05-10 Thread Tim Phipps
[EMAIL PROTECTED] wrote: On 08 May 2001 14:34:54 +0100, Tim Phipps wrote: Attached is a patch to make FvwmEvent pass the window-id in hex. Maybe just pass a heximal id in PassId instead of additional PassHexId? I think it is safe. Fine by me, I didn't want to upset anyone. Attached is

Re: Wait in functions is broken

2001-05-10 Thread Dominik Vogt
On Wed, May 09, 2001 at 11:12:26PM +, Mikhael Goikhman wrote: On 09 May 2001 01:48:44 +0200, Dominik Vogt wrote: On Tue, May 08, 2001 at 09:58:24PM +, Mikhael Goikhman wrote: I don't know when this started. AddToFunc TestFunction I Wait unexisting window TestFunction

Re: FvwmPager WindowColorsets not updating completely

2001-05-10 Thread Dominik Vogt
On Wed, May 09, 2001 at 03:23:52PM -0500, An Thi-Nguyen Le wrote: Version: cvs (May 8th) I ran across something strange recently with FvwmPager. 1. Set up the pager like so, and *without* mini icons: *FvwmPagerWindowColorsets 1 2 *FvwmPagerSmallFont 5x7 2. Set up colorsets 1

Re: Nautilus-Fvwm interaction

2001-05-10 Thread Dominik Vogt
On Wed, May 09, 2001 at 10:43:10PM -0700, Michael Han wrote: On Thu, May 10, 2001 at 12:20:10AM -0400, Paul D. Smith wrote: Here's a relevant passage from [EMAIL PROTECTED] in the response to bug #7823: http://bugzilla.eazel.com/show_bug.cgi?id=7823 My reading of the ICCCM is

CVS domivogt: * Fixed Globally Active input model (untested).

2001-05-10 Thread FVWM CVS
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt01/05/10 05:46:54 Modified files: . : ChangeLog fvwm : focus.c Log message: * Fixed Globally Active input model (untested). -- Visit the official FVWM web page at

Re: Nautilus-Fvwm interaction

2001-05-10 Thread Dominik Vogt
On Wed, May 09, 2001 at 06:41:11PM +0200, Tomas Ogren wrote: Hello. If you use fvwm2 and run Nautilus, bad focus stuff happens.. You won't get any keyboard focus in the Nautilus window for instance. The Nautilus people says it's an fvwm bug.. If anyone with knowledge of WM hints and focus

Re: FvwmPager WindowColorsets not updating completely

2001-05-10 Thread Dominik Vogt
On Thu, May 10, 2001 at 12:37:26PM +0200, fvwm-workers wrote: On Wed, May 09, 2001 at 03:23:52PM -0500, An Thi-Nguyen Le wrote: Version: cvs (May 8th) I ran across something strange recently with FvwmPager. 1. Set up the pager like so, and *without* mini icons:

CVS domivogt: * Fixed active icon change when window was not iconified.

2001-05-10 Thread FVWM CVS
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: domivogt01/05/10 06:48:42 Modified files: . : ChangeLog fvwm : events.c fvwm.h icons.c window_flags.h modules: ChangeLog modules/FvwmPager: FvwmPager.c

CVS migo: * FAQ: added cvs info to the patch questions, as Andr� Dahlqvist suggested

2001-05-10 Thread FVWM CVS
CVSROOT:/home/cvs/fvwm Module name:fvwm Changes by: migo01/05/10 09:00:33 Modified files: . : ChangeLog docs : ChangeLog FAQ fvwm : session.c modules: ChangeLog modules/FvwmPager: FvwmPager.c

CVS migo fvwm-web: regenerated FAQ and NEWS

2001-05-10 Thread FVWM CVS
CVSROOT:/home/cvs/fvwm Module name:fvwm-web Changes by: migo01/05/10 09:12:29 Modified files: . : ChangeLog generated : FAQ.html NEWS.html Log message: regenerated FAQ and NEWS -- Visit the official FVWM web page at

SetEnv not expanding environmental variables itself

2001-05-10 Thread An Thi-Nguyen Le
Version: cvs (as of May 10 09:35:30 CDT 2001) Maybe this is documented somewhere. Set up some environment stuff, like so: SetEnv fvwmdir ${HOME}/.fvwm SetEnv bindir $fvwmdir/bin 'Exec echo blah' should fully expand these variables, then. However, this happens: Exec echo $fvwmdir

Re: SetEnv not expanding environmental variables itself

2001-05-10 Thread An Thi-Nguyen Le
[An Thi-Nguyen Le - Thu, 10 May 2001 09:50:34 AM CDT] Version: cvs (as of May 10 09:35:30 CDT 2001) Maybe this is documented somewhere. Set up some environment stuff, like so: SetEnv fvwmdir ${HOME}/.fvwm SetEnv bindir $fvwmdir/bin 'Exec echo blah' should fully expand these

Re: SetEnv not expanding environmental variables itself

2001-05-10 Thread Dan Espen
An Thi-Nguyen Le [EMAIL PROTECTED] writes: Version: cvs (as of May 10 09:35:30 CDT 2001) Maybe this is documented somewhere. Set up some environment stuff, like so: SetEnv fvwmdir ${HOME}/.fvwm SetEnv bindir $fvwmdir/bin 'Exec echo blah' should fully expand these variables, then.

Re: SetEnv not expanding environmental variables itself

2001-05-10 Thread An Thi-Nguyen Le
[Dan Espen - Thu, 10 May 2001 10:14:34 AM CDT] Use the notation: Exec echo $[bindir] Ah. Okay. Never mind... Embarassed... -- An Thi-Nguyen Le -- Visit the official FVWM web page at URL:http://www.fvwm.org/. To unsubscribe from the list, send unsubscribe fvwm-workers in the body of a

Re: SetEnv not expanding environmental variables itself

2001-05-10 Thread Mikhael Goikhman
On 10 May 2001 09:49:41 -0500, An Thi-Nguyen Le wrote: Maybe this is documented somewhere. Yes, in the man page. Enter /environment and press 'n' several times. You will find everything you wanted to know, including the fact that only 3 commands ImagePath, ModulePath and Restart expand