[Tcsh] Compliments to the developers and contributors.

Thu Sep 1 12:21:24 UTC 2022

It is not bad at all :-) I've been using it for more than 40 years... It is great for command line use, but not good for scripting...

christos

> On Sep 1, 2022, at 3:16 PM, M G P <tateusg at hotmail.com> wrote:
> 
> That's understandable, but some make a hell out of nothing, condemning it at all costs. I think it's wrong to take it as plain failure due to the parsing style.
> 
> 
> 
> I moved to [T]csh after realizing Bash couldn't avoid injections. I didn't take the time to check on other Bourne-like Shells (and wasn't optimistic on them), but [T]csh proved to be more reliable, though initially I was almost convinced it was a bad idea, due to the heavy criticism.
> 
> 
> 
> Wasn't for my curiosity and persistence, I'd believe [T]csh is as bad as some put.
> 
> 
> 
> 
> 
> 
> 
> 
> From: Christos Zoulas <christos at zoulas.com>
> Sent: Thursday, September 1, 2022, 06:47
> To: M G P <tateusg at hotmail.com>
> Cc: tcsh at astron.com <tcsh at astron.com>
> Subject: Re: [Tcsh] Compliments to the developers and contributors.
> 
> 
> There are lots of problems and races in the way csh (and tcsh) evaluates commands and pipelines. Some of them are really hard to fix (see https://bugs.astron.com <https://bugs.astron.com/>). Also parsing is not robust since the shell only recognizes keywords at the beginning of lines in some cases...
> 
> 
> Best,
> 
> 
> 
> christos
> 
> 
> 
>> On Aug 31, 2022, at 6:01 PM, M G P <tateusg at hotmail.com <mailto:tateusg at hotmail.com>> wrote:
>> 
>> 
>> I wrote a guide on how to use the C Shell, in the hope it'll serve as a guide on how to adequately write scripts, as well as to encourage people on not giving up: https://gist.github.com/Krush206/bfcfd760be645150bb247f051e98c9d3 <https://gist.github.com/Krush206/bfcfd760be645150bb247f051e98c9d3>
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> From: Tcsh <tcsh-bounces at astron.com <mailto:tcsh-bounces at astron.com>> on behalf of M G P <tateusg at hotmail.com <mailto:tateusg at hotmail.com>>
>> Sent: Tuesday, August 16, 2022 1:20:16 PM
>> To: tcsh at astron.com <mailto:tcsh at astron.com> <tcsh at astron.com <mailto:tcsh at astron.com>>
>> Subject: Re: [Tcsh] Compliments to the developers and contributors.
>> 
>> 
>> 
>> 
>> 
>> 
>> https://en.m.wikipedia.org/wiki/Special:MobileDiff/1102822365 <https://en.m.wikipedia.org/wiki/Special:MobileDiff/1102822365>
>> Why do they think multi-line aliases aren't possible?
>> 
>> 
>> alias function 'if -e \!$ then\
>> 
>> echo OK\
>> 
>> else\
>> 
>> echo Not OK\
>> 
>> endif'
>> 
>> function dir
>> 
>> 
>> 
>> I can also make it into a variable:
>> 
>> set function = 'if -e \!$ then\
>> 
>> echo OK\
>> 
>> else\
>> 
>> echo Not OK\
>> 
>> endif\
>> 
>> :'
>> 
>> eval $function:q dir
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> From: Tcsh <tcsh-bounces at astron.com <mailto:tcsh-bounces at astron.com>> on behalf of M G P <tateusg at hotmail.com <mailto:tateusg at hotmail.com>>
>> Sent: Monday, January 31, 2022, 05:52
>> To: tcsh at astron.com <mailto:tcsh at astron.com> <tcsh at astron.com <mailto:tcsh at astron.com>>
>> Subject: Re: [Tcsh] Compliments to the developers and contributors.
>> 
>> 
>> And I'm very proud to find another, better workaround to the criticism in the Wikipedia webpage:
>> 
>> 
>> # Always creates an empty file
>> 
>> if (! -e myfile) echo mytext > myfile
>> 
>> # Workaround
>> 
>> if (! -e myfile) eval "echo mytext > myfile"
>> 
>> My workaround <https://en.wikipedia.org/wiki/Special:MobileDiff/1069012614>:
>> 
>> ( ( : < myfile ) >& /dev/null && echo File exists. ) || ( ( echo mytext > myfile ) >& /dev/null && echo File created. ) || ( echo Cannot create file. )
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> From: Tcsh <tcsh-bounces at astron.com <mailto:tcsh-bounces at astron.com>> on behalf of M G P <tateusg at hotmail.com <mailto:tateusg at hotmail.com>>
>> Sent: Wednesday, December 22, 2021, 03:05
>> To: tcsh at astron.com <mailto:tcsh at astron.com>
>> Subject: [Tcsh] Compliments to the developers and contributors.
>> 
>> 
>> Hello.
>> 
>> Just did like to leave a comment in here, thanking the developers and contributors of Tcsh.
>> 
>> 
>> 
>> The C Shell is such a brilliant work from Bill Joy, and Tcsh makes a great enhancement and continuation to it. Furthermore, the C Shell is the only Shell out there which resembles the Thompson and Mashey Shells, which (unfortunately) were superseded by the Bourne Shell.
>> 
>> 
>> 
>> I'm not a long-time Tcsh user, however, after learning it, it really fascinated me - so much that I keep wondering how some dislike it.
>> 
>> To be fair, Tcsh taught me how to write scripts with security in mind, due its "limitations". The "limitations" imposed by the C Shell make it one of the most reliable Shells to work with, and I should not complain, but thank for that. (E.g: nesting commands is impossible; there are better ways to achieve what one want, without nesting commands.)
>> 
>> 
>> 
>> 
>> I really have no complaints to C Shell or Tcsh, but I must thank each of you who keep the development of an old brilliant gem from Bill Joy and Ken Greer up.
>> 
>> Thank you very much for your time and effort!
>> 
>> 
>> 
>> P.S: the complaints from a Perl developer in faqs.org <http://faqs.org/> are plain petty; something I learned very quickly is that most things can be worked-around with sub-shells or named FIFOs.
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> --
>> Tcsh mailing list
>> Tcsh at astron.com <mailto:Tcsh at astron.com>
>> https://mailman.astron.com/mailman/listinfo/tcsh
>> <sanitizer.log>
>> 
> 
> 
> 
> 
> 
> <sanitizer.log>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.astron.com/pipermail/tcsh/attachments/20220901/9e643d2b/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 235 bytes
Desc: Message signed with OpenPGP
URL: <https://mailman.astron.com/pipermail/tcsh/attachments/20220901/9e643d2b/attachment.asc>