Le Fri, 03 Jan 2014 20:41:56 -0500,
Dan Espen <des...@verizon.net> a écrit :
> Dominique Michel <dominique.mic...@vtxnet.ch> writes:
>
> > Le Fri, 03 Jan 2014 10:34:24 -0500,
> > Dan Espen <des...@verizon.net> a écrit :
> >
> >> Dominique Michel <dominique.mic...@vtxnet.ch> writes:
> >>
> >> > Le Fri, 3 Jan 2014 15:07:52 +0100,
> >> > Dominique Michel <dominique.mic...@vtxnet.ch> a écrit :
> >> >
> >> >> It seam like file and directory names with characters like {}
> >> >> or () into their names confuse very easily fvwm. At the
> >> >> beginning, I was thinking it was fvwm-menu-directory that get
> >> >> confused by them, but after running the same command into a
> >> >> console, it appear the menu generated by it is correct in any
> >> >> cases. So the issue is in fvwm itself.
> >>
> >> Sorry, I've read your post twice and still don't understand.
> >> Please send a single fvwm command that doesn't work as you expect.
> >
> > A resumed fvwm code that fail is:
> >
> > DestroyFunc FuncFvwmMenuMovieDirectory
> > AddToFunc FuncFvwmMenuMovieDirectory
> > + I PipeRead 'case \"$0\" in \
> > "/home/alian/Vídeos"*) myexec="fvwm-crystal.mplayer-wrapper file
> > dom";;
>
> I rather not install fvwm-crystal.
>
The menu failure I get have nothing to do with that
fvwm-crystal.mplayer-wrapper call. You can replace that command with any
command that suit you, in that case "mplayer" or "mplayer -ao alsa"
should work.
Dominique
