itowlson

@kate-goldenring It looks like it only works if `spin` is unqualified (i.e. on the PATH). I see the same thing if I try to autocomplete via a relative path. CURSES.

I dunno if this is a bash limitation or if there is an incantation we can do to make it behave properly.

Kate reports that it now blows up on `zsh` with `_arguments:comparguments:325: can only be called from completion function` so not sure how to proceed from here... might have to call...

All right, it looks like on `zsh` you need to pipe it to a file named `_spin` and put this into `.zshrc` (assuming you put the file in a `~/completions`...

@mikkelhegn I updated the description without leaving a comment; my bad. I changed the syntax to `spin generate-completions ` because my first tester used `zsh` not `bash`. I think `fish`...

@mikkelhegn The question, for me, is: given what we now know about the limitations of doing it the quick way, and the cost of doing it a nicer way, how...

The quick way won't for plugins, though with the Clap shenanigans in #1560 it _might_ list initial plugin names - but it is purely static, derived from the Clap command...

I haven't found any documents indicating that zsh or fish completions can be written in anything other than ~shell script~ their custom languages, so this approach may be a dead...

This is back on the want list for Spin 2.1. What's the best way to figure out a path to delivery? cc @mikkelhegn @melissaklein24

If zsh is highest priority, then the approach here won't work. That puts us back to `clap_complete`, which gives us subcommand names and options, but only offers files for values...