From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11344 invoked by alias); 18 Jun 2019 02:27:51 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 11337 invoked by uid 89); 18 Jun 2019 02:27:51 -0000 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 Received: from eddie.starwolf.com (HELO eddie.starwolf.com) (69.12.250.42) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 18 Jun 2019 02:27:49 +0000 Received: from [192.168.40.76] (getinsured.com [4.16.195.116]) by eddie.starwolf.com (Postfix) with ESMTPSA id 8EF0BB5 for ; Mon, 17 Jun 2019 19:27:46 -0700 (PDT) Subject: Re: [ANNOUNCEMENT] tcsh 6.21.00-1 To: cygwin@cygwin.com References: From: Greywolf Message-ID: <2ec62274-cf38-5fff-4fb8-f0093d9ba408@starwolf.com> Date: Tue, 18 Jun 2019 02:27:00 -0000 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: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2019-06/txt/msg00164.txt.bz2 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