From: "Bart Schaefer" <schaefer@brasslantern.com>
To: TGAPE! <tgape@cyberramp.net>
Cc: zsh-workers@math.gatech.edu
Subject: Re: Docs fix
Date: Mon, 26 Oct 1998 20:21:23 -0800 [thread overview]
Message-ID: <981026202123.ZM12435@candle.brasslantern.com> (raw)
In-Reply-To: <199810262202.WAA06805@dal-tsa33-1.cyberramp.net>
On Oct 26, 10:02pm, TGAPE! wrote:
> Subject: Re: Docs fix
> >
> >> Not exactly. "$@" keeps empty arguments and independent of option and
> >> IFS settings, neither of which is true for $*.
> >
> > Yes, but as I was just explaining privately to Phil, the context of his
> > change is "what zsh construct is most like using \!* in csh aliases?"
> >
> > The best answer is $*, because you have to use \!*:q to get "$@" behavior
> > in csh. An argument could be made that $==* is even better, but not "$@".
>
> Who cares if it is the behavior that is most equivalent, when the
> behavior is not what they want?!?
The context here is the question about converting csh aliases to zsh.
Csh aliases DO HAVE the equivalent of the "$@" construct. It's \!*:q.
If one has a CORRECTLY WORKING ALIAS that uses \!* without the :q, then
using "$@" in the replacement zsh function will *NOT* do what one wants,
in at least some circumstances.
In ANY OTHER CONTEXT, *especially* in shells scripts, everything that is
being said about "$@" being better is *absolutely* correct. But it is
NOT correct in the FAQ question where Phil's patch changes it!
> But, to quote Zoltan,
>
> > It's good habbit to use "$@". The use of $* is almost always wrong
> > in bourne/korn shell scripts still people use that all the time.
A zsh function intended to replace a csh alias is not a bourne/korn script.
Otherwise I completely agree.
> Showing people how to mimic the broken behavior of their old shells is
> not necessarily a good way to win converts or friends. However, I do
> think the FAQ should be modified to mention that no, this isn't the the
> exact same behavior, this is better.
Sigh. Look. The FAQ cannot possibly explain all circumstances in which
"$@" is correct. When it's correct, it's better; when it's wrong, it's
not better.
> Btw, can you show even *one* case where a csh user really wants $*
> functionality and not "$@"?
Sure. Warning, csh syntax follows.
alias do "\!* >&! did &"
alias dopr '\!* | lpr -J "\!:1"'
If you replace $* with "$@" when converting those aliases, you end up
quoting the word in the command position, which causes unexptected side
effects.
> And, even if $* by default acted exactly
> like "$@", it's a good idea to script so as to be complient with as many
> shells as is reasonable.
This is all wonderful advice, but completely out of context for the place
that Phil's patch made the change.
next prev parent reply other threads:[~1998-10-27 4:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-10-26 23:03 Phil Pennock
1998-10-26 23:53 ` Bart Schaefer
1998-10-27 1:25 ` Zoltan Hidvegi
1998-10-27 2:27 ` Bart Schaefer
1998-10-26 22:02 ` TGAPE!
1998-10-27 4:05 ` Phil Pennock
1998-10-27 4:21 ` Bart Schaefer [this message]
1998-10-27 5:13 ` Zoltan Hidvegi
1998-10-28 4:53 ` Bart Schaefer
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=981026202123.ZM12435@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=tgape@cyberramp.net \
--cc=zsh-workers@math.gatech.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).