Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: zparseopts no longer accepts long options

X-seq: zsh-workers 54443
From: dana <dana@xxxxxxx>
To: "Vin Shelton" <ethersoft@xxxxxxxxx>
Cc: "Zsh Hackers' List" <zsh-workers@xxxxxxx>
Subject: Re: zparseopts no longer accepts long options
Date: Fri, 01 May 2026 12:36:46 -0500
Archived-at: <https://zsh.org/workers/54443>
Feedback-id: i9be146f9:Fastmail
In-reply-to: <CACeGjnX1F6Mn7LN8gW85ta0O2_Djfv2ZoQPkqKm1uuTWqt+KGg@mail.gmail.com>
List-id: <zsh-workers.zsh.org>
References: <CACeGjnX1F6Mn7LN8gW85ta0O2_Djfv2ZoQPkqKm1uuTWqt+KGg@mail.gmail.com>

On Fri 1 May 2026, at 12:09, Vin Shelton wrote:
> smaug% zparseopts -D -E -extra=arg1
> zparseopts: bad option: -e

this is due to w/54376, which changed zparseopts to use the standard
option-parsing facilities. in short you now need to protect long-option
specs with - or -- as in `zparseopts -D -E - -extra=arg1`

(this is ofc mentioned as an incompatibility in the README)

i laid out my thinking for this in the post and didn't get any
objections there or on irc, but lmk if you want to discuss further

dana

References:
- zparseopts no longer accepts long options
  - From: Vin Shelton

Messages sorted by: Reverse Date, Date, Thread, Author