zparseopts and longopts

zparseopts and longopts

[Atte Peltomaki]

Howdy hackers,

I'm seeing erratic behaviour when using zparseopts together with GNU
long options which have additional dashes and the first part before the
dash is common. Example:

---clip---
#!/bin/zsh
zparseopts -E -D -- -gnu:=gnu -gnu-tard:=gnutard
print -- $gnu\\n$gnutard
---clap---

Executing as intended:

% ./test.zsh --gnu argh --gnu-tard rms
--gnu argh
--gnu-tard rms

Executing with imaginary new option:

% ./test.zsh --gnu argh --gnu-tard rms --gnu-tard-added-even-longer-opt whyohwhy
--gnu argh
--gnu-tard -added-even-longer-opt

-- 
Atte Peltomäki
     atte.peltomaki@iki.fi <> http://kameli.org
"Your effort to remain what you are is what limits you"

Re: zparseopts and longopts

[Bart Schaefer]

On Thu, May 12, 2016 at 4:16 AM, Atte Peltomaki <atte.peltomaki@iki.fi> wrote:
> Executing with imaginary new option:
>
> % ./test.zsh --gnu argh --gnu-tard rms --gnu-tard-added-even-longer-opt whyohwhy
> --gnu argh
> --gnu-tard -added-even-longer-opt

Well, you've told zparseopts that --gnu-tard is an option that takes a
mandatory argument, and you have not told zparseopts that
--gnu-tard-add... is an option, and the argument of an option is
allowed to appear in the same word as the option itself (so that -a2
is the same as -a 2), so zparseopts believes -add... is the argument
of the option you told it about.

Re: zparseopts and longopts

[Atte Peltomaki]

On Fri, May 13, 2016 at 04:25:28AM -0700, Bart Schaefer wrote:
> On Thu, May 12, 2016 at 4:16 AM, Atte Peltomaki <atte.peltomaki@iki.fi> wrote:
> > Executing with imaginary new option:
> >
> > % ./test.zsh --gnu argh --gnu-tard rms --gnu-tard-added-even-longer-opt whyohwhy
> > --gnu argh
> > --gnu-tard -added-even-longer-opt
> 
> Well, you've told zparseopts that --gnu-tard is an option that takes a
> mandatory argument, and you have not told zparseopts that
> --gnu-tard-add... is an option, and the argument of an option is
> allowed to appear in the same word as the option itself (so that -a2
> is the same as -a 2), so zparseopts believes -add... is the argument
> of the option you told it about.

Makes sense, but also makes it impossible to use zparseopts with a
caller that may spontaneously add options and expect scripts to work
unmodified.

-- 
Atte Peltomäki
     atte.peltomaki@iki.fi <> http://kameli.org
"Your effort to remain what you are is what limits you"