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
From: "Michael Bax" <mbax AT stanford DOT edu>
To: <cygwin AT cygwin DOT com>
Subject: The tcsh manual vs tcsh initialization; fix for slow startup
Date: Sat, 1 Jan 2005 04:46:45 -0800
Message-ID: <ECEEJLCHJDLKMHGOACFJIEGLCDAA.mbax@stanford.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

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?

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?

3.
On a Pentium I-level computer, tcsh takes an aggravatingly long time to
process the initialization files.  I found that commenting out the lines
that call
	source /etc/profile.d/complete.tcsh
in /etc/csh.cshrc (or deleting the file /etc/profile.d/complete.tcsh) sped
up this process dramatically.

Cheers
Michael


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