X-Recipient: archive-cygwin@delorie.com
DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=gHAT62mZM4iL4a51
	ksDnmHtszk3XQUIykT0+xKwlrd6KeCjgXT0UZU0z5fRYfoZ3ngnoOK1kg5gyDdfK
	IyMbpHu2g19QLaCrAnWEkGM/5rQYSX9SEBpiCBRbfpk1WlU9CI/XtXcZwYWIulIr
	e7W52NA20N4lYlS2x0N1x+GQSpk=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=MwmAS64ZO6HzNHgfYKZPVL
	Tw3vA=; b=ZVPwqvVHyoDWBCWlzapoRvnkXOl6AbxTj4nIedpK3SV9tpa3yp5M9Z
	FGo0b1Drx9EN1mk+2UQC9HNUjAGmMNOSCq2iZdhWMsYJvdzlARe+8gjOGpgmR+AH
	v5W4VdoHde+QglbdQyvPB2GmYFAAdXrKQKnnYhrJyb0SWE2xTQzjY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=BAYES_00,KAM_NUMSUBJECT,SPF_PASS autolearn=no version=3.3.1 spammy=prototyping, 4.2, earth, students
X-HELO: eddie.starwolf.com
Subject: Re: [ANNOUNCEMENT] tcsh 6.21.00-1
To: cygwin@cygwin.com
References: <announce.20190617114548.32299-1-corinna-cygwin@cygwin.com> <DB7PR01MB538635A91B6AD46AF72E46D4DEEB0@DB7PR01MB5386.eurprd01.prod.exchangelabs.com> <CAEhDDbALQSuTO1aky95F_-cPd0R0WwXZE3H2mM=hD1h5w5SYPg@mail.gmail.com> <c25fbe33-05bd-ab4a-0f11-90907ef3cf59@SystematicSw.ab.ca>
From: Greywolf <greywolf@starwolf.com>
Message-ID: <2ec62274-cf38-5fff-4fb8-f0093d9ba408@starwolf.com>
Date: Mon, 17 Jun 2019 19:27:45 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.1
MIME-Version: 1.0
In-Reply-To: <c25fbe33-05bd-ab4a-0f11-90907ef3cf59@SystematicSw.ab.ca>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 2019-06-17 09:11, Brian Inglis wrote:
> 
> On 2019-06-17 07:13, Csaba Raduly wrote:
>> On Mon, Jun 17, 2019 at 2:12 PM Jose Isaias Cabrera  wrote:
>>> Just wondering... Does anyone still uses tcsh?  That was my favorite shell
>>> before bash.
>> There are always pockets of resistance, hiding out in the mountains
>> (-: server rooms, etc :-)
> 
> Some of us were lured to csh on SunOS by mentions of C-like features (still
> looking for those) and used tcsh on other systems, before coming to our senses
> when POSIX standardized based on Bourne/Korn shell features, and appreciating
> the kitchen sink inclusive implementation of interactive shell features provided
> by bash.
> 

Some of us were lured to csh on BSD 4.2 because sh was primitive as all 
get-out -- no functions, no aliases; the only thing it had going for it was 
better signal trapping.  Where I was, a few students implemented 'dsh', a 
follow-on to 'csh', which had ESC-based pathname, user, ~user, and envariable 
expansion (ran in cbrk mode), and a few other things (and some really goofy 
error messages).  I inherited it and immediately declared it dead upon the 
arrival on scene by tcsh, which I then abandoned once I discovered bash, since 
I wanted to have a CLI which resembled my primary prototyping language.

[ksh, on the other hand, is welcome to fall off the face of the earth at any 
unannounced moment...]

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

