Hello -
We need this at our site: If you run FvwmM4 on unsuspecting
users, "FvwmM4 -m4-prefix" prevents problems with "include", but
there are still problems with $HOME in an exec becoming $/home/user.
With the following patch, no default behavior is changed, but
if FvwmM4 is also star
> "TP" == Tim Phipps <[EMAIL PROTECTED]> writes:
TP> Just gone to update to the latest and there are no snapshots for
TP> September.
Drat. I upgraded my machine and while I copied my home directory I forgot
to copy my crontab. This of course screwed up multiple things.
I just built a snaps
Hi All,
Just gone to update to the latest and there are no snapshots for
September.
Cheers,
Tim.
--
Visit the official FVWM web page at http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, sen
On Fri, Sep 07, 2001 at 03:44:35AM +0200, Dominik Vogt wrote:
> On Thu, Sep 06, 2001 at 01:50:55PM +0200, Olivier Chapuis wrote:
> > Dominik can you send me (again) an insure++ "Machine id". I will
> > try to get for you a one day license before the end of the
> > negotiation to be sure that insure
Hi !
I suggest the following change in FScreen.c (or something equivalent):
cvs diff -r 1.5 FScreen.c
Index: FScreen.c
===
RCS file: /home/cvs/fvwm/fvwm/libs/FScreen.c,v
retrieving revision 1.5
diff -r1.5 FScreen.c
319c319
< sc
On Wed, Sep 05, 2001 at 07:05:16PM -0400, Kurunkad, Raju wrote:
> Hi,
>
> I finished compiling FVWM 2.4.0 on UNIX SVR4. It runs OK, but when I try to
> exit, it dumps core. The core file contains very limited info even though
> FvwmButtons is compiled with -g. This is the stack trace that gdb disp
