Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/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
Date: Mon, 3 Jan 2005 10:51:29 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: The tcsh manual vs tcsh initialization; fix for slow startup
Message-ID: <20050103095129.GB12820@cygbert.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <ECEEJLCHJDLKMHGOACFJIEGLCDAA DOT mbax AT stanford DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ECEEJLCHJDLKMHGOACFJIEGLCDAA.mbax@stanford.edu>
User-Agent: Mutt/1.4.2i

On Jan  1 04:46, Michael Bax wrote:
> 1.
> The tcsh manual states:
> 	onintr is ignored if the shell is running detached and in system
> 	startup files (see FILES), where interrupts are disabled anyway.
> 
> But:
> 	>grep onintr /etc/csh.cshrc
> 	onintr -
> 	  onintr
> 
> Is the manual incorrect or is the initialization file conceptually flawed?

It doesn't hurt, does it?

> 2.
> The tcsh manual also states:
> 	-f  The shell ignores ~/.tcshrc, and thus starts faster.
> 
> But -f also causes the shell to ignore /etc/csh.* and .login.  Is the
> specification or the implementation at fault?

This is a question you should ask the tcsh developers.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          mailto:cygwin AT cygwin DOT com
Red Hat, Inc.

--
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/