Roland Fredenhagen

This could be a shared interface that at least fish and bash could use. For bash this would allow the same output as currently, and it would support the full...

I was actually stumbling on this trying to design a shard set of options for dynamic completions. Would we support the use case of conflicting groups? I see two ways...

I had a problem probably related to this, I wanted to close a window on pressing ESC but when the text input was focused the update event loop did not...

> > I had a problem probably related to this, I wanted to close a window on pressing ESC but when the text input was focused the update event loop...

As a workaround for anyone stumbling on this looking for a solution: ```fish complete -x -c my_app -a '(complete -C "__fish_complete_path "(commandline --current-token))' ``` This will behave like `-F`

makes sense. IMO it would be great to have something less verbose than the complete -C call.

> Just wanted to write the same comment, so instead my suggestion: If its easier I would be happy if swords are taken out of tool switch, I would prefer...

I'll also look into implementing a switch to attack weapon, where you can set your preferred attack weapon (Axe/hoe/shovel).

@maruohon should this be a seperate tweak? e.g. `autoSwitchToWeapon`?

Should what entities trigger the switch be configurable (e.g. to exclude your dog/cat you don't want to kill accidentally)?