On 26 Jan 2006 22:01:28 +0100, Friedrich Delgado Friedrichs wrote: > > Dominik Vogt schrieb: > > If you set the environment variable FVWM_USERDIR to a directory > > name, fvwm uses this directory instead of $HOME/.fvwm. > > I can't really check right now (because I'm at home) but I doubt that > this will provide anything more than an awkward workaround. > > If I move my fvwm home out of my $HOME permanently, I'd have to sync > it to the local disk every time I change to a different workstation.
Well, syncing it may be just one cp command in fvwm wrapper. > If you mean I should reset FVWM_USERDIR temporarily before starting > FvwmConsole (e.g. via a function) I guess that this will cause all > kinds of side effects e.g. when I test fvwm configuration snippets in > FvwmConsole. This approach is possible too. The only side effect would be you can't have shared FvwmConsole history (it will be local to the machine). Create this ~/bin/MyFvwmConsole script: #!/bin/bash export FVWM_USERDIR=/tmp/$USER/fvwm mkdir -p $FVWM_USERDIR exec $FVWM_MODULEDIR/FvwmConsole "$@" and start the module as "Module $[HOME]/bin/MyFvwmConsole". > But I can try tomorrow and see if there's any good way to do this. > > Or should I simply post a simple patch to fvwm-workers? You may post a patch to add a directory option to both FvwmConsole and FvwmConsoleC[.pl], but just adding support for $TMP var would be bad, since this would clutter filename space and add side effects for those who have this var defined for other purposes. Maybe supporting $FVWM_TMP centrally is better, but I would not start this change now. Regards, Mikhael.
