Keep sorting for completions

[terlar]

If I have a completion method that returns results in the relevant order, I'd like to have the possibility to keep this order instead of sorting alphabetically.

Perhaps a switch that tells the completion to leave this alone?

[terlar]

I can explain a use case for this. For example the completions that use git branches and tags.

Right now if I run git checkout <Tab> then all the tags will appear first and amongst them the oldest ones first since they have a lower number. In my use case those are the least likely to be checked out.

Because of this I created a completion that returned branches and tags in order of relevance.

• First local branches
• Then tags and branches in order of last commit

The benefit of this is that I quickly can see the branches I work on in the completion, see which branches are active on the remote and finally which tags are most recent without having to scan through all the old ones.

[danielcompton]

This would be a really great feature, I also have the same problem where tags are sorted ahead of branches.

[ridiculousfish]

I wonder how bad it would be to only sort file completions. I'll take a crack at this.

[krader1961]

FYI: Some completion scripts do not deduplicate their output and instead rely on the existing fish sorting of the suggestions to do so. So if this is ever implemented we need to decided whether to retain de-duping of the suggestions without sorting them or require that such completions handle the de-duping on their own.

[mqudsi]

I just ran into this with git commit --fixup, where fish actually ends up sorting all commits ever by sha1 instead of showing them in reverse order, rendering completions useless here.