From: Mikael Magnusson <mikachu@gmail.com>
To: Jun T <takimoto-j@kba.biglobe.ne.jp>
Cc: zsh-workers@zsh.org
Subject: Re: "${*:offset:length}" and ksh93/bash compatibility
Date: Wed, 16 Mar 2022 16:57:32 +0100 [thread overview]
Message-ID: <CAHYJk3TLZ8krzG3foQTUmMgdNUjDqXUWqsXJFK0wY_WA4Gfo1A@mail.gmail.com> (raw)
In-Reply-To: <68098B63-701D-4DDF-9A44-2B1DC80FA0D2@kba.biglobe.ne.jp>
On 3/16/22, Jun T <takimoto-j@kba.biglobe.ne.jp> wrote:
>
>> 2022/03/14 0:22, Mikael Magnusson <mikachu@gmail.com> wrote:
>>
>> I realized that this is not limited to $*,
>>
>> zsh% a=(one two three); echo "${a[@]:0:2}"
>> one two
>> zsh% a=(one two three); echo "${a[*]:0:2}"
>> on
>
> The following patch seems to work for
> "${*:1:2}" "${@:1:2}" "$a[@]:0:2}" "${a[*]:0:2}"
>
> For example (with or without KSH_ARRAYS):
>
> zsh% printf '<%s>\n' "${a[@]:0:2}"
> <one>
> <two>
>
> If KSH_ARRAYS is not set, "$a:0:2" behaves like "${a[*]:0:2}".
>
> I don't know if there are better/simpler solutions.
> 'make check' passes, but please do some tests to see if there
> are any bad side effects.
It's certainly a lot simpler than my idea, and also seems to work in
the cases I could come up with. I guess if KSH_ARRAYS is not set, then
there is no expectation of bash compatibility anyway so whatever we do
there is fine.
--
Mikael Magnusson
next prev parent reply other threads:[~2022-03-16 15:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 7:50 Stephane Chazelas
2022-03-10 12:48 ` Mikael Magnusson
2022-03-10 14:25 ` Peter Stephenson
2022-03-13 15:22 ` Mikael Magnusson
2022-03-13 18:21 ` Bart Schaefer
2022-03-13 19:23 ` Mikael Magnusson
2022-03-13 20:57 ` Bart Schaefer
2022-03-16 5:57 ` Jun T
2022-03-16 15:57 ` Mikael Magnusson [this message]
2022-03-23 8:08 ` Jun T
2022-03-23 10:23 ` Mikael Magnusson
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=CAHYJk3TLZ8krzG3foQTUmMgdNUjDqXUWqsXJFK0wY_WA4Gfo1A@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=takimoto-j@kba.biglobe.ne.jp \
--cc=zsh-workers@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).