-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
:V* commands blocking tab complete #178
Comments
How are you getting a capitalized command completed from a lowercase input? |
I assumed that it was a default option, but after a search I discovered that it was the It seems weird to me that this applies to commands, but since the |
@Rycieos, |
That would explain why it made the issue go away. I'll reopen this then, since having lazy search is extremely handy. Does anyone know why it is applying to command tab completion instead of just a search? |
I think this code is responsible for the behaviour in question. But I don't understand whether it's planned or accidental, because documentation differs from the code. I personally find the behaviour useful sometimes (e.g. |
That is a handy feature, I use vim-fugitive as well, and did not know that that was possible with I have removed the commands mentioned in this issue from my version of pathogen (Rycieos/vim-pathogen@90220d5e144ceee1b5d83a64703bdd120efe6968), which fixes the problem for me. I will leave it up to @tpope to resolve or close this issue. As for the setting having weird reaching effects, I agree. I have created vim/vim#991 on this topic. |
This is so annoying. I really hate tab completing incorrectly The open PR #138 in 2014 says you are waiting for v3.0 to remove these commands. But then a year later in 2015 in 84a3dd0 the Which also means that the pathogen README is incorrect.. @tpope Are the |
I brought them back because I was trying to be diligent about semver and save the removal for 3.0. But it's a dumb user facing feature with a clear migration path so fine, y'all win. |
As seen in commit b4f20ff and noted in that commits comments, the commands for V* are still in pathogen, only seeming to exist to explain that they are now in a different plugin. Because these commands are registered, they prevent autocompletion of the same builtin commands.
Ex: type
:vsp<TAB>
Expected: vim completes to
:vsplit
Actual: vim does not complete and prints two possibilities:
Vsplit vsplit
Removing these commands would fix the problem.
The text was updated successfully, but these errors were encountered: