From: Jose Isaias Cabrera <jicman@outlook.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: [ANNOUNCEMENT] tcsh 6.21.00-1
Date: Mon, 17 Jun 2019 12:11:00 -0000 [thread overview]
Message-ID: <DB7PR01MB538635A91B6AD46AF72E46D4DEEB0@DB7PR01MB5386.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <announce.20190617114548.32299-1-corinna-cygwin@cygwin.com>
Just wondering... Does anyone still uses tcsh? That was my favorite shell before bash.
________________________________
From: cygwin-owner@cygwin.com <cygwin-owner@cygwin.com> on behalf of Corinna Vinschen <corinna-cygwin@cygwin.com>
Sent: Monday, June 17, 2019 05:45 AM
To: cygwin@cygwin.com
Subject: [ANNOUNCEMENT] tcsh 6.21.00-1
The following packages have been uploaded to the Cygwin distribution:
* tcsh-6.21.00-1
This is a bug fix release (after 2.5 years) with no new features.
Tcsh is an enhanced but completely compatible version of csh, the C
shell. Tcsh is a command language interpreter which can be used both
as an interactive login shell and as a shell script command processor.
Tcsh includes a command line editor, programmable word completion,
spelling correction, a history mechanism, job control and a C language
like syntax.
--
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
--
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-17 12:11 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 [this message]
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
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=DB7PR01MB538635A91B6AD46AF72E46D4DEEB0@DB7PR01MB5386.eurprd01.prod.exchangelabs.com \
--to=jicman@outlook.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).