From: Greywolf <greywolf@starwolf.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] tcsh 6.21.00-1
Date: Tue, 18 Jun 2019 02:27:00 -0000 [thread overview]
Message-ID: <2ec62274-cf38-5fff-4fb8-f0093d9ba408@starwolf.com> (raw)
In-Reply-To: <c25fbe33-05bd-ab4a-0f11-90907ef3cf59@SystematicSw.ab.ca>
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
next prev parent reply other threads:[~2019-06-18 2:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 9:48 Corinna Vinschen
2019-06-17 12:11 ` Jose Isaias Cabrera
2019-06-17 13:13 ` Csaba Raduly
2019-06-17 13:18 ` Jose Isaias Cabrera
2019-06-17 16:11 ` Brian Inglis
2019-06-18 2:27 ` Greywolf [this message]
2019-06-18 16:31 ` Jose Isaias Cabrera
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2ec62274-cf38-5fff-4fb8-f0093d9ba408@starwolf.com \
--to=greywolf@starwolf.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).