Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
From: "H. James de St. Germain" <germain AT cs DOT utah DOT edu>
To: cygwin AT cygwin DOT com
Cc: cygwin AT cygwin DOT com
In-reply-to: <Pine.GSO.4.56.0401081633300.18895@slinky.cs.nyu.edu> (message from Igor Pechtchanski on Thu, 8 Jan 2004 16:44:56 -0500 (EST))
Subject: Re: control-spacebar
References: <20040108204601 DOT C1DDB3C063 AT juggler DOT cs DOT utah DOT edu> <Pine DOT GSO DOT 4 DOT 56 DOT 0401081550250 DOT 8635 AT slinky DOT cs DOT nyu DOT edu> <Pine DOT GSO DOT 4 DOT 56 DOT 0401081633300 DOT 18895 AT slinky DOT cs DOT nyu DOT edu>
Message-Id: <20040108220309.E7E393C063@juggler.cs.utah.edu>
Date: Thu,  8 Jan 2004 15:03:09 -0700 (MST)


To follow up on using rxvt:

I have changed by cygwin.bat to have

  rxvt -e tcsh -l   

as the final line. (Yes I (currently) like some of the old tcsh
properties over bash (though I've used both over time))  (But
doesn't everyone just work in emacs anyway?)

Then when you start cygwin, it pops up an rxvt terminal for you.

NOTE: in the past I have had 

  setenv CYGWIN "tty" 

in my resource file (.tcshrc) and this causes the rxvt to core dump
upon exit.  Removing this line seems to have fixed the problem.

Now the only problem I have is that rxvt thinks its an X window
so I have to type "emacs -nw" everytime... not a big deal.

Again, my thanks to Igor and the user/developer community for
supporting all of us.

cheers
  jim


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/