From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: bash conversion trouble.
Date: Sat, 25 Feb 2017 08:24:15 -0800 [thread overview]
Message-ID: <32f48d32-2b11-045e-5925-8f112783f1e2@eastlink.ca> (raw)
In-Reply-To: <170225075521.ZM22115@torch.brasslantern.com>
On 25/02/17 07:55 AM, Bart Schaefer wrote:
> On Feb 25, 3:26pm, Peter Stephenson wrote:
> }
> } setopt ksharrays
> }
> } simulates this, but obviously if you want consistency with other
> } functions, don't even think sbout it.
>
> Also typically do
>
> setopt localoptions ksharrays
>
> so the zero-based-ness doesn't leak out to the rest of the shell. If
> you're in a standalone script you won't be sourcing, that's not needed.
>
Just curious: why would that have been changed? It's the sort of thing
that would obviously make trouble, and of course if there's a good
reason for it, that's too bad, but what's the good reason? These zero
or one based counting issues are everywhere and I've never been able to
see why one is to be preferred over the other, tho zero might seem more
computery and one would be more 'natural' I suppose.
next prev parent reply other threads:[~2017-02-25 16:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-25 1:35 Ray Andrews
2017-02-25 4:41 ` Bart Schaefer
2017-02-25 15:13 ` Ray Andrews
2017-02-25 15:26 ` Peter Stephenson
2017-02-25 15:55 ` Bart Schaefer
2017-02-25 16:24 ` Ray Andrews [this message]
2017-02-25 17:02 ` Bart Schaefer
2017-02-25 19:13 ` Ray Andrews
2017-02-25 20:09 ` Bart Schaefer
2017-02-26 5:05 ` Ray Andrews
2017-02-26 17:19 ` Bart Schaefer
2017-02-26 18:03 ` Ray Andrews
2017-02-26 21:10 ` Shell history (Re: bash conversion trouble.) Bart Schaefer
2017-02-26 23:23 ` Ray Andrews
2017-02-28 15:56 ` bash conversion trouble Stephane Chazelas
2017-02-28 19:27 ` Ray Andrews
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=32f48d32-2b11-045e-5925-8f112783f1e2@eastlink.ca \
--to=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).