From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: [BUG] getopts OPTIND
Date: Wed, 10 Jan 2018 09:05:57 +0000 [thread overview]
Message-ID: <20180110090557.5a064295@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <0877C4E8-4CA3-453F-A16B-99E576F60E8D@dana.is>
On Tue, 9 Jan 2018 16:48:17 -0600
dana <dana@dana.is> wrote:
> On 9 Jan 2018, at 10:22, Francisco de Zuviría Allende <franciscodezuviria@gmail.com> wrote:
> >Execution in bash: ... OPTIND is 5, next -a
> >execution in zsh: ... OPTIND is 4, next -r
>
> I think this fixes it? At least, zsh gives the same output as bash and dash when
> i do this. Peter's left an ominous warning about changes to this function that
> deserves recognition though...
I've completely lost track of the cases that are real compatibility
problems and which are just broken, because, as just got quoted, the
code is pretty hair-raising anyway.
If we think we can get away with wrapping this change in
isset(POSIXBUILTINS) that will make it easier. It doesn't sound like it
can be wrong in that case, anyway.
pws
next prev parent reply other threads:[~2018-01-10 9:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 16:22 Francisco de Zuviría Allende
2018-01-09 22:48 ` dana
2018-01-09 22:57 ` Bart Schaefer
2018-01-09 23:58 ` dana
2018-01-10 1:32 ` Francisco de Zuviría Allende
2018-01-10 9:05 ` Peter Stephenson [this message]
2021-04-13 23:28 ` dana
2021-04-14 13:04 ` [BUG] getopts OPTIND - yash's behaviour Daniel Shahaf
2021-04-14 13:08 ` [BUG] getopts OPTIND Daniel Shahaf
2021-04-18 5:16 ` dana
2021-04-20 21:31 ` Daniel Shahaf
2021-05-03 23:38 ` dana
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=20180110090557.5a064295@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--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).