2010/1/7 <[email protected]>: > Thomas Adam <[email protected]> writes: > >> 2010/1/7 <[email protected]>: >>> >>> The recent change to the read logic causes a problem for me. >>> Here's a part of my .fvwm2rc: >>> >>> read .fvwmrc.tile >>> read .fvwmrc.mouse >>> >>> Those really are relative paths... >> >> Indeed -- I am at work, so attaching a patch with this email. I can't >> reproduce the problem myself, but does the patch attached fix it? If >> so, I'll clean it up later. > > There's no hurry on my part to fix it. > I've got a local fix in place. > > I'm not sure why you made the change. > > Doesn't fopen "FVWM_DATADIR/./file" work?
I am sure it would do -- but since "-f" passing on the command line just uses "Read" internally, you can't do: fvwm -f some_file or: fvwm -f ./some_file ... and mean CWD -- since FVWM assumes that to be relative to FVWM_USERDIR -- that's fine. But that check should still happen, as it's cumbersome having to keep doing: fvwm -f $(pwd)/somefile It's been annoying me now for about a year. -- Thomas Adam
