This is the mail archive of the
mailing list for the Cygwin project.
Re: Weird behavior of tcsh.exe?
- From: Corinna Vinschen <corinna-cygwin at cygwin dot com>
- To: cygwin at cygwin dot com
- Date: Sun, 4 Mar 2012 18:20:30 +0100
- Subject: Re: Weird behavior of tcsh.exe?
- References: <firstname.lastname@example.org>
- Reply-to: cygwin at cygwin dot com
On Mar 4 06:55, sborer wrote:
> Hi, I'm not sure if this is a bug or some kind of feature, but it seems like
> the behavior of tcsh.exe somewhat depends on its file name.
> running the line:
> tcsh.exe -c 'echo "d:\a\b\c"'
> results in the output: "d". As if escaping of the argument occurred.
> if i copy tcsh.exe to a different name not starting with tcsh.exe, for
> example ntcsh.exe, then running:
> ntcsh.exe -c 'echo "d:\a\b\c"'
> results in the output: "d:\a\b\c"
> Is this intentional? (Are there inside the code of tcsh.exe some lines that
> actually check its filename and determine its behavior accordingly?)
Yes. If the name is tcsh, it behaves as tcsh, as csh otherwise.
As for the builtin echo command, the tcsh variant allows SysV and
BSD-style, the non-tcsh version only BSD-style.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple