From: Ray Andrews <rayandrews@eastlink.ca>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-users@zsh.org
Subject: Re: '$1' indexing.
Date: Thu, 22 Dec 2011 18:08:58 -0800 [thread overview]
Message-ID: <4EF3E2BA.4000306@eastlink.ca> (raw)
In-Reply-To: <111222161159.ZM15011@torch.brasslantern.com>
On 22/12/11 04:11 PM, Bart Schaefer wrote:
> Hmm, you posted exactly this same thing with the subject "bug" on the
> 20th. Did you not see the replies? Yes, it's a bug, and a patch for
> it has also been posted.
>
Ooops! I just joined this list today. I forgot about the previous post,
and I didn't even know if it had been received, let alone answered. I
did post it on StackOverflow, but that is of course different. Anyway, I
see your reply and I understand what's going on. I'm too new to this to
have any strong opinion, but it seems to me that the behavior we see
would perhaps be good for '$@' where '$0' is implied, but not for an
explicit '$1'.
Glad to know that the developers are aware of it, thanks.
FWIW it seems to me that zsh has the 'right idea' when it comes to
string splitting. It's true that converting my bash scripts has involved
a more laborious coding in zsh (mostly needing to use 'eval'), but that
is the price to be paid for keeping variables unbroken unless you
specifically ask for the breakdown into words.
So what is the current state of zsh development? How many workers are
there? Is zsh ascendant? Is ground being gained against bash?
> See http://www.zsh.org/mla/workers/2011/msg01456.html for explanation
> and http://www.zsh.org/mla/workers/2011/msg01459.html for patch.
>
next prev parent reply other threads:[~2011-12-23 2:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-18 10:11 default to file completion Miek Gieben
2011-12-18 13:57 ` Mikael Magnusson
2011-12-18 15:20 ` Miek Gieben
2011-12-22 23:01 ` Miek Gieben
2011-12-22 23:42 ` '$1' indexing Ray Andrews
2011-12-23 0:11 ` Bart Schaefer
2011-12-23 2:08 ` Ray Andrews [this message]
2011-12-23 20:56 ` Bart Schaefer
2011-12-23 20:45 ` default to file completion Bart Schaefer
2011-12-25 10:32 ` Miek Gieben
2011-12-20 19:38 ` gi1242+zsh
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=4EF3E2BA.4000306@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@zsh.org \
/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).