Manlio Perillo <> writes:

>> As long as all of the above stops completion at directory boundary,
>> I think the above sounds like a sensible thing to do.  e.g. when
>> "ls-files" gives Documentation/Makefile and Documentation/git.txt,
>> "git cmd Doc<TAB>" first would give "git cmd Documentation/" and
>> then the second <TAB> would offer these two paths as choices.  That
>> way, the user can choose to just execute "git cmd Documentation/"
>> without even looking at these individual paths.
> Right, this is what bash usually do.
> However I don't know how to implement this with git.

That sounds like a regression to me.

>> I am not sure how you would handle the last parameter to "git mv",
>> though.  That is by definition a path that does not exist,
>> i.e. cannot be completed.
> Right, the code should be changed.
> No completion should be done for the second parameter.

I deliberately wrote "the last" not "the second", as you can do

        $ mkdir X
        $ git mv COPYING README X/.

You do need to expand the second parameter to README when the user

        git mv COPYING REAMDE X

then goes back with \C-b to "M", types \C-d three times to remove
"MDE", and then finally says <TAB>, to result in

        git mv COPYING README X

To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
More majordomo info at

Reply via email to