Ubuntu vim virtual directory

where is the ubuntu vim plugin directory. I need to remove the autoclose.vim plugin to fix the problem described here: Arrow keys type in capital letters instead of moving the cursor

+2
vim
03 Oct 2018-11-21T00:
source share
3 answers

Check :h runtimepath complete description of the possible locations for your folder (given that you are not using the bundle plugin). Here is an excerpt:

  *'runtimepath'* *'rtp'* *vimfiles* 'runtimepath' 'rtp' string (default: Unix, Mac OS X: "$HOME/.vim, $VIM/vimfiles, $VIMRUNTIME, $VIM/vimfiles/after, $HOME/.vim/after" ... global {not in Vi} This is a list of directories which will be searched for runtime files: filetype.vim filetypes by file name |new-filetype| scripts.vim filetypes by file contents |new-filetype-scripts| autoload/ automatically loaded scripts |autoload-functions| colors/ color scheme files |:colorscheme| compiler/ compiler files |:compiler| doc/ documentation |write-local-help| ftplugin/ filetype plugins |write-filetype-plugin| indent/ indent scripts |indent-expression| keymap/ key mapping files |mbyte-keymap| lang/ menu translations |:menutrans| menu.vim GUI menus |menu.vim| plugin/ plugin scripts |write-plugin| print/ files for printing |postscript-print-encoding| spell/ spell checking files |spell| syntax/ syntax files |mysyntaxfile| tutor/ files for vimtutor |tutor| And any other file searched for with the |:runtime| command. The defaults for most systems are setup to search five locations: 1. In your home directory, for your personal preferences. 2. In a system-wide Vim directory, for preferences from the system administrator. 3. In $VIMRUNTIME, for files distributed with Vim. *after-directory* 4. In the "after" directory in the system-wide Vim directory. This is for the system administrator to overrule or add to the distributed defaults (rarely needed) 5. In the "after" directory in your home directory. This is for personal preferences to overrule or add to the distributed defaults or system-wide settings (rarely needed). ... 
+6
Oct 03 '11 at 21:40
source share

You must follow Eric'comment.

However, I have these lines in my .vimrc:

- EDIT -

I know that this answer is not selected, but I learned something thanks to the comments of ZyX, so this is editing.

The lines below should be written as follows:

 nnoremap <Esc>A <up> nnoremap <Esc>B <down> nnoremap <Esc>C <right> nnoremap <Esc>D <left> inoremap <Esc>A <up> inoremap <Esc>B <down> inoremap <Esc>C <right> inoremap <Esc>D <left> 

I am afraid that many people make the same mistake as me: the original solution to the output code seems to be everywhere on the network from Vim wiki to SO through a lot of forums.

- END EDIT -

 nnoremap <type ctrl+v then Esc to obtain a single char that looks like ^[>A <up> nnoremap <type ctrl+v then Esc to obtain a single char that looks like ^[>B <down> nnoremap <type ctrl+v then Esc to obtain a single char that looks like ^[>C <right> nnoremap <type ctrl+v then Esc to obtain a single char that looks like ^[>D <left> inoremap <type ctrl+v then Esc to obtain a single char that looks like ^[>A <up> inoremap <type ctrl+v then Esc to obtain a single char that looks like ^[>B <down> inoremap <type ctrl+v then Esc to obtain a single char that looks like ^[>C <right> inoremap <type ctrl+v then Esc to obtain a single char that looks like ^[>D <left> 

and there was no need to remove the plugin.

0
04 Oct 2018-11-11T00:
source share

Instead of reading the rules on 'runtimepath' , I think getting a list of all installed scripts is easier:

 :scriptnames 

This will show the full path to each script that vim has loaded. If there are few of them, then you can determine the one you are looking for ( autoclose.vim for OP).

If the list is long, you can write the output of scriptnames to register a (or any other), paste it into an empty buffer and search for the name of your plugin:

 :redir @a :scriptnames :redir END :new :put a :/autoclose\.vim 
0
Feb 15 '16 at 19:42
source share



All Articles