- vim or neovim?
- Output of
vim --version or nvim --version:
- Output of
:echo has("python"):
- Output of
:echo has("python3"):
- Output of
:echo &pythondll(only vim, not neovim):
- Output of
:echo &pythonthreedll(only vim, not neovim):
- Output of
:py print(sys.version):
- Output of
:py3 print(sys.version):
- Output of
:echo g:Lf_Debug_Cmd:
- Operating system:
- Configurations related to LeaderF in vimrc:
Describe your question, feature request, or bug.
Steps to reproduce
Assume the tag names are: tag1, tag2, tag3.
In past, after :LeaderfTag, then input "tag". I can use "up/down" key to choose the one I want. If I find I type sth wrong, say I type "tbg". I can use backspace key to undo the change.
Now, after :LeaderfTag, then input "tag". I HAVE TO press tab key. Then use "up/down" key to choose the one I want. After press tab key, if I find I type sth wrong, say I type "tbg". I've to type i to goto to i mode to type backspace.
I think the new feature is not convenient. Basically, I've to type extra more to do the same thing as before. Is this change by design? If yes, may you please provide a global flag to switch to previous mode?
Thanks.
Actual behaviour
Expected behaviour
vim --versionornvim --version::echo has("python")::echo has("python3")::echo &pythondll(only vim, not neovim)::echo &pythonthreedll(only vim, not neovim)::py print(sys.version)::py3 print(sys.version)::echo g:Lf_Debug_Cmd:Describe your question, feature request, or bug.
Steps to reproduce
Assume the tag names are: tag1, tag2, tag3.
In past, after :LeaderfTag, then input "tag". I can use "up/down" key to choose the one I want. If I find I type sth wrong, say I type "tbg". I can use backspace key to undo the change.
Now, after :LeaderfTag, then input "tag". I HAVE TO press tab key. Then use "up/down" key to choose the one I want. After press tab key, if I find I type sth wrong, say I type "tbg". I've to type i to goto to i mode to type backspace.
I think the new feature is not convenient. Basically, I've to type extra more to do the same thing as before. Is this change by design? If yes, may you please provide a global flag to switch to previous mode?
Thanks.
Actual behaviour
Expected behaviour