Re: FVWM: Newbie question

From: Paul D. Smith <pausmith_at_nortelnetworks.com>
Date: 31 May 2000 14:40:04 -0400

%% "Dave (Grizz) Glaser" <dsglaser_at_mtu.edu> writes:

>> OK. Modify your .xinitrc so that it redirects stdout and stderr to a
>> file (maybe ~/.fvwm-errors or something) so you can see any messages
>> FVWM is generating.

  dg> How? I tried .../fvwm >& fvwm-errors but it just puked on me.

Again, I assume you mean ".../fvwm2" here.
                                  ^

What exactly does "puked on me" mean? It's impossible to help without
proper descriptions of behavior.

I suspect the problem is that .xinitrc is a traditional Bourne shell
script. The >& token is a C shell (bletch ptooey) feature... although
some Bourne-based shells, like bash, allow it too.

The equivalent to the above, in sh syntax, is:

  .../fvwm2 > fvwm-errors 2>&1

-- 
-------------------------------------------------------------------------------
 Paul D. Smith <psmith_at_baynetworks.com>         Network Management Development
 "Please remain calm...I may be mad, but I am a professional." --Mad Scientist
-------------------------------------------------------------------------------
   These are my opinions---Nortel Networks takes no responsibility for them.
--
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 May 31 2000 - 13:41:23 BST