Mikhael Goikhman <migo_at_homemail.com> writes:
> On 18 Dec 2002 15:12:56 -0800, Ben Sferrazza wrote:
> >
> > PrintInfo Colors output doesn't seem to be going to ~/.xsession-errors.
> > Maybe I should try running another fvwm process on top of the existing
> > one from the command line, but redirect its output to another file. I
> > suppose this is kind of what you were instructing me to do before with
> > the '>'. Any ideas here?
>
> If you can't redirect the fvwm stderr in the first place (why?),
Fvwm is being launched by the CDE session manager.
It gets the name of the binary to launch from an X Resource.
Perhaps the way its starting the window manager doesn't use
a shell with enough smarts to support command line redirection.
> there are several ways to do this on the fly.
>
> If (and only if) fvwm is not the last xinit program running in the
> foreground you may replace it with another fvwm that you run from any
> xterm using: "fvwm -replace >& fvwm.out" (with some shells you need
> to do "> fvwm.out 2>&1". Otherwise you may quit X by doing this.
>
> Another way that should always work is to issue "Restart xterm" from
> FvwmConsole or menus. Then when you get xterm and no decorations (since no
> window manager is run), you may start fvwm inside this xterm by executing
> "fvwm" with optional stdout/stderr redirection. Just remember to close
> this xterm to close your X session with some X setups.
Mikhael, thats cool, I wasn't aware of the -replace up until now.
Read my other mail, I don't know that PrintInfo Colors is
useful anymore. I could be wrong of course, it wouldn't be
the first time, (or the last).
--
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 Dec 18 2002 - 19:53:37 GMT