Hi,
I did a test for a trivial fix for this bug, by just not
creating amissing .fvwm directory, but that resulted in breakage
further down the line: a user using fvwm for the first time would not
be able to use the fvwm or the fvwm95 forms to create an initial
.fvwm2rc file, since those functions assume an extant .fvwm
dir. While I am sure one can work through and identify these places
in the code, and create the directory as and when needed, this is
likely to take more effort.
In the meanwhile, one may just set FVWM_USERDIR to /tmp, or
something.
manoj
--
"Reality is not binding on news admins." Cathy Foulston
([EMAIL PROTECTED])
Manoj Srivastava <[EMAIL PROTECTED]> <http://www.golden-gryphon.com/>
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
