Mikhael Goikhman <migo_at_homemail.com> writes:
> On 15 Jan 2003 13:26:23 -0700, Jeremy Slade wrote:
> >
> > Andy Arbon writes:
> > >
> > > I used to have problems with (g)mplayer. My solution was to launch an
> > > xterm which launches mplayer (Exec exec xterm -iconic -e gmplayer). This
> > > gives mplayer somewhere to display its output, which seems to keep it hap
> py.
> > >
> > > Probably not the solution to the problem, but in my case an acceptable
> > > workaround.
> >
> > I believe gmplayer has some options to suppress it's output --
> > e.g. -quiet or somesuch. That should take care of it.
>
> It does not explain anything. It is perfectly fine for any Exec'd program
> to write to stdout or stderr.
>
> Actually, probably the problem is that gmplayer is an interactive program
> and reads stdin. I just tried 2.4.14 and it does freeze when I enter:
> Exec rm -i /tmp/some-existing-file
>
> Although it is not supported to run interactive programs directly in Exec,
> this is a problem with fvwm and it is strange that it is only with 2.4.x.
> In 2.5.x it is fine if Exec'd process reads stdin except that this process
> is stuck. Anyway, as a workaround try: Exec interactive-prog </dev/null
> Or like you wrote: Exec xterm -e interactive-prog.
I haven't tried it under 2.4.14 yet, but under current CVS it acted
strange. The windows came up blank, and the little window with
the image of the player only had a title bar.
It acted completely normal when I added "&" to the end of the
command line.
I'm not sure what that means.
--
Dan Espen E-mail: dane_at_mk.telcordia.com
--
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 Wed Jan 15 2003 - 20:08:11 GMT