From: Danek Duvall <duvall@comfychair.org>
To: Zsh users list <zsh-users@sunsite.dk>
Subject: Re: egrep with zsh as /bin/sh - wordsplitting
Date: Thu, 13 Jan 2005 13:23:51 -0800 [thread overview]
Message-ID: <20050113212351.GD11826@lorien.comfychair.org> (raw)
In-Reply-To: <2005-01-13T17-30-35@devnull.michael-prokop.at>
On Thu, Jan 13, 2005 at 09:50:18PM +0100, Michael Prokop wrote:
> Why does the original egrep version use ${1+"$@"} and not
> "$@" or "${1+"$@"}"?
My understanding is that if you write "$@", then with no arguments, in some
shells it becomes "" (i.e., an argument, but with no length), and that's
not actually what you want. ${1+"$@"} only adds something if there are any
arguments.
I don't know if this is a problem on any modern shell, though.
Danek
next prev parent reply other threads:[~2005-01-13 21:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-13 20:50 Michael Prokop
2005-01-13 21:23 ` Danek Duvall [this message]
2005-01-14 8:43 ` Stephane Chazelas
2005-01-14 17:15 ` Michael Prokop
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=20050113212351.GD11826@lorien.comfychair.org \
--to=duvall@comfychair.org \
--cc=zsh-users@sunsite.dk \
/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).