On 23 May 2003 12:56:34 +0200, Klaus Zeitler wrote:
>
> I added "Module FvwmCommand" to my startup and tried:
> FvwmCommand FuncFvwmMenuDirectory "/"
> Same result, fvwm stalled, but now I could still use this one xterm that
> had the focus. The session error file (~/.dt/sessionlogs/sfsw51_DISPLAY=:0)
> now said "Option exec-file requires an argument". Somehow it seems as if
> that "^emacs" in:
> + I PipeRead 'fvwm-menu-directory -d "$0" --exec-file "^emacs" --check-subdir
> vanishes into thin air.
> So now I created an functions-appbind-extra with
> --- snip ---
> DestroyFunc FuncFvwmMenuDirectory
> AddToFunc FuncFvwmMenuDirectory
> + I PipeRead 'fvwm-menu-directory -d "$0" --exec-file "^emacs" --check-subdir --links --wm-icons'
> --- snip ---
> i.e. with a quoted "^emacs" and it works!
>
>
> If that error log wouldn't be overwritten when I start a new session, I'd
> have found this a lot easier. I think I'm going to save that at the end of my
> xsession file now.
>
> Still I have a few questions:
>
> 1. what's happening with that "^file" expression?
You may take a look at "man sh" on your system. I will quote it.
> 2. why/how is determined that emacs is used for text files? This is
> certainly not a problem for me, cause that's the only editor I've
> been using since 1985, but we have other users here that despise
> emacs. Isn't it possible to use the env variable EDITOR or some such
> here?
I would really like to use $EDITOR, but this variable is a bit useless in
X Window in that some of the editors open their own windows (weird) and
some work in the terminal as designed by $EDITOR. So to work for all
$EDITOR values you should always open xterm even for emacs. The caret
says not to open an xterm.
So the only way to customize this is to redefine FuncFvwmMenuDirectory
in functions-appbind-extra, you may redefine your own viewer, browser,
prefered image processors and so on in the same file too (see FAQ).
Regards,
Mikhael.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Fri May 23 2003 - 06:15:09 BST