Hi, This works fine for me: For `git checkout `, fish completes only dirty (but unstaged) files, as well as commits. The completions are ordered such that the files come first. On `git checkout --` fish completes only dirty unstaged files, same on `git restore `.
With `git restore --staged` or `git reset HEAD -- ` you get completions of staged files. `git checkout` with staged paths doesn't do anything, so I'm not sure what you're missing. We should complete to something that is valid for git, otherwise it's a bug. On the rare occasion I need plain file completions I temporarily insert a `: ` at the beginning of the command. On Mon, Feb 24, 2020 at 12:43 PM Peter Flood <i...@whywouldwe.com> wrote: > Hi > > I upgraded to fish 3.1.0 last week (from 2.x, don't recall which) and > have just noticed that the `git checkout` completions don't complete > filenames/paths any more. This is really frustrating to me, it seems to > only want to complete valid git hashes/tags/branch names. I often `git > checkout <paths>...` to remove all changes, this has broken my workflow. > Is there any way I can get the old behaviour back? > > Thanks > > > > _______________________________________________ > Fish-users mailing list > Fish-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/fish-users >
_______________________________________________ Fish-users mailing list Fish-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/fish-users
