Re: Completion confusion around the _arguments -A flag

[Mal Graty <mal@xxxxxxx>]

Thanks Dana

For reference, in case it rings a bell for anyone, I'm seeing this on a
vanilla Ubuntu 18.04 install. I'll have a poke around for anything that
might be altering default behaviour though, thanks for confirming I'm
not mad :)

On 25 July 2018 at 17:36, dana <dana@xxxxxxx> wrote:

> On 22 Jul 2018, at 10:16, Mal Graty <mal@xxxxxxx> wrote:
> >I have a binary (call it foo) with two, mutually exclusive, optional flags
> >(that must come first) and a required arg. The problem I'm having is that
> >when omitting both flags and using just the arg the completion tries to
> add
> >one of the flags after it. Reading the docs lead me to the -A flag,
> however
> >it doesn't seem to be preventing the flag completion despite being after
> >the first arg. I'm hoping I've just overlooked something but for the life
> >of me I can't see it.
>
> For whatever it's worth, i don't see anything obviously wrong with your
> function, and it works fine when i test it on 5.5. Maybe you have an option
> enabled that changes the behaviour, idk
>
> dana
>
>