Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-Id: <4.3.1.2.20010913143328.03034b30@pop.ma.ultranet.com>
X-Sender: lhall AT pop DOT ma DOT ultranet DOT com
X-Mailer: QUALCOMM Windows Eudora Version 4.3.1
Date: Thu, 13 Sep 2001 14:36:14 -0400
To: belg4mit AT MIT DOT EDU, cygwin AT cygwin DOT com
From: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>
Subject: Re: Running tcsh in rxvt
In-Reply-To: <200109131822.OAA21315@cab-calloway.mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"

At 02:22 PM 9/13/2001, Jerrad Pierce wrote:
>What's the best way to do this?
>If you do rxvt -e tcsh (say from a shortcut).
>The user's dotfile is not parsed (seemingly because home etc. don't get
>correctly set from passwd), plus tab completion and history don't work.
>
>I've got:
>         bash --login -i -c "/bin/rxvt -e tcsh" &
>
>But it seems like there really ought to be a way to avoid the seemingly
>unnecessary invocation of bash and having it hanging around afterwards...


What's the matter with "rxvt -e tcsh -l" ?


>Of course:
>         rxvt -e bash --login -i #from the rxvt documentation
>doesn't work properly when invoking from outside of the cygwin environment
>either; i.e. not from an exiisting bash --login -i session.


How so?  Works fine for me.



Larry Hall                              lhall AT rfk DOT com
RFK Partners, Inc.                      http://www.rfk.com
118 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/