From: Bart Schaefer <schaefer@brasslantern.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: '$1' indexing.
Date: Fri, 23 Dec 2011 12:56:14 -0800 [thread overview]
Message-ID: <111223125614.ZM17220@torch.brasslantern.com> (raw)
In-Reply-To: <4EF3E2BA.4000306@eastlink.ca>
On Dec 22, 6:08pm, Ray Andrews wrote:
}
} ... 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'.
Yes, that was the intended behavior and that's what the patch implements.
It's already been checked in to the source repository for next release.
} 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')
There are very few places where you ought to need "eval" -- more likely
you should simply have replaced ${var} with ${=var} in those places.
} So what is the current state of zsh development? How many workers are
} there? Is zsh ascendant? Is ground being gained against bash?
There are three or four people who regularly work on the shell plus a
couple of others who maintain the ports for various linux distributions
and jump in when bugs get filed against their dists. Beyond that there
are a number of others who contribute sporadically. We could use some
more regular people; during zsh's most rapid development years we had
several university students working on it, but C is no longer the most-
studied language so that source of energy has faded.
I wouldn't say any particular shell is "gaining ground" at this point,
and none of the developers of any of the shells really looks on it as
a competition anyway.
next prev parent reply other threads:[~2011-12-23 20:56 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
2011-12-23 20:56 ` Bart Schaefer [this message]
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=111223125614.ZM17220@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=rayandrews@eastlink.ca \
--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).