代码拉取完成，页面将自动刷新
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
<title>usr_90 - Vim Documentation</title>
<meta name="Generator" content="Vim/8.0">
<meta name="plugin-version" content="vim8.0">
<meta name="syntax" content="help">
<meta name="settings" content="no_pre,use_css,expand_tabs">
<link rel="stylesheet" href="style.css" type="text/css" />
<script src="jquery.min.js" type="text/javascript"></script>
<script src="mark-current-page.js" type="text/javascript"></script>
</head>
<body>
<header>
<div class="header">
<a href="http://vim-jp.org/">vim-jp</a>
/ <a href="http://vim-jp.org/vimdoc-en/">vimdoc-en</a>
/ usr_90<br />
<a name="top"></a><h1>usr_90 - Vim Documentation</h1>
<a href="index.html">Return to main</a>
<span class="EnglishJapaneseLink">
<span class="CurrentLanguage">English</span>
</span>
</div>
</header>
<nav>
<dl>
<dt>BASIC</dt>
<dd><ul>
<li><a href="quickref.html">quickref</a></li>
<li><a href="sponsor.html">sponsor</a></li>
</ul></dd>
<dt>USER MANUAL</dt>
<dd><ul>
<li><a href="usr_toc.html">usr_toc</a></li>
</ul></dd>
<dt>Getting Started</dt>
<dd><ul>
<li><a href="usr_01.html">usr_01</a></li>
<li><a href="usr_02.html">usr_02</a></li>
<li><a href="usr_03.html">usr_03</a></li>
<li><a href="usr_04.html">usr_04</a></li>
<li><a href="usr_05.html">usr_05</a></li>
<li><a href="usr_06.html">usr_06</a></li>
<li><a href="usr_07.html">usr_07</a></li>
<li><a href="usr_08.html">usr_08</a></li>
<li><a href="usr_09.html">usr_09</a></li>
<li><a href="usr_10.html">usr_10</a></li>
<li><a href="usr_11.html">usr_11</a></li>
<li><a href="usr_12.html">usr_12</a></li>
</ul></dd>
<dt>Editing Effectively</dt>
<dd><ul>
<li><a href="usr_20.html">usr_20</a></li>
<li><a href="usr_21.html">usr_21</a></li>
<li><a href="usr_22.html">usr_22</a></li>
<li><a href="usr_23.html">usr_23</a></li>
<li><a href="usr_24.html">usr_24</a></li>
<li><a href="usr_25.html">usr_25</a></li>
<li><a href="usr_26.html">usr_26</a></li>
<li><a href="usr_27.html">usr_27</a></li>
<li><a href="usr_28.html">usr_28</a></li>
<li><a href="usr_29.html">usr_29</a></li>
<li><a href="usr_30.html">usr_30</a></li>
<li><a href="usr_31.html">usr_31</a></li>
<li><a href="usr_32.html">usr_32</a></li>
</ul></dd>
<dt>Tuning Vim</dt>
<dd><ul>
<li><a href="usr_40.html">usr_40</a></li>
<li><a href="usr_41.html">usr_41</a></li>
<li><a href="usr_42.html">usr_42</a></li>
<li><a href="usr_43.html">usr_43</a></li>
<li><a href="usr_44.html">usr_44</a></li>
<li><a href="usr_45.html">usr_45</a></li>
</ul></dd>
<dt>Making Vim Run</dt>
<dd><ul>
<li><a href="usr_90.html">usr_90</a></li>
</ul></dd>
<dt>General subjects</dt>
<dd><ul>
<li><a href="intro.html">intro</a></li>
<li><a href="index.html">help</a></li>
<li><a href="helphelp.html">helphelp</a></li>
<li><a href="vimindex.html">index</a></li>
<li><a href="tags.html">tags</a></li>
<li><a href="howto.html">howto</a></li>
<li><a href="tips.html">tips</a></li>
<li><a href="message.html">message</a></li>
<li><a href="quotes.html">quotes</a></li>
<li><a href="todo.html">todo</a></li>
<li><a href="debug.html">debug</a></li>
<li><a href="develop.html">develop</a></li>
<li><a href="uganda.html">uganda</a></li>
</ul></dd>
<dt>Basic editing</dt>
<dd><ul>
<li><a href="starting.html">starting</a></li>
<li><a href="editing.html">editing</a></li>
<li><a href="motion.html">motion</a></li>
<li><a href="scroll.html">scroll</a></li>
<li><a href="insert.html">insert</a></li>
<li><a href="change.html">change</a></li>
<li><a href="indent.html">indent</a></li>
<li><a href="undo.html">undo</a></li>
<li><a href="repeat.html">repeat</a></li>
<li><a href="visual.html">visual</a></li>
<li><a href="various.html">various</a></li>
<li><a href="recover.html">recover</a></li>
</ul></dd>
<dt>Advanced editing</dt>
<dd><ul>
<li><a href="cmdline.html">cmdline</a></li>
<li><a href="options.html">options</a></li>
<li><a href="pattern.html">pattern</a></li>
<li><a href="map.html">map</a></li>
<li><a href="tagsrch.html">tagsrch</a></li>
<li><a href="quickfix.html">quickfix</a></li>
<li><a href="windows.html">windows</a></li>
<li><a href="tabpage.html">tabpage</a></li>
<li><a href="syntax.html">syntax</a></li>
<li><a href="spell.html">spell</a></li>
<li><a href="diff.html">diff</a></li>
<li><a href="autocmd.html">autocmd</a></li>
<li><a href="filetype.html">filetype</a></li>
<li><a href="eval.html">eval</a></li>
<li><a href="channel.html">channel</a></li>
<li><a href="fold.html">fold</a></li>
</ul></dd>
<dt>Special issues</dt>
<dd><ul>
<li><a href="print.html">print</a></li>
<li><a href="remote.html">remote</a></li>
<li><a href="term.html">term</a></li>
<li><a href="digraph.html">digraph</a></li>
<li><a href="mbyte.html">mbyte</a></li>
<li><a href="mlang.html">mlang</a></li>
<li><a href="arabic.html">arabic</a></li>
<li><a href="farsi.html">farsi</a></li>
<li><a href="hebrew.html">hebrew</a></li>
<li><a href="russian.html">russian</a></li>
<li><a href="ft_ada.html">ft_ada</a></li>
<li><a href="ft_sql.html">ft_sql</a></li>
<li><a href="hangulin.html">hangulin</a></li>
<li><a href="rileft.html">rileft</a></li>
</ul></dd>
<dt>GUI</dt>
<dd><ul>
<li><a href="gui.html">gui</a></li>
<li><a href="gui_w32.html">gui_w32</a></li>
<li><a href="gui_x11.html">gui_x11</a></li>
</ul></dd>
<dt>Interfaces</dt>
<dd><ul>
<li><a href="if_cscop.html">if_cscop</a></li>
<li><a href="if_lua.html">if_lua</a></li>
<li><a href="if_mzsch.html">if_mzsch</a></li>
<li><a href="if_perl.html">if_perl</a></li>
<li><a href="if_pyth.html">if_pyth</a></li>
<li><a href="if_tcl.html">if_tcl</a></li>
<li><a href="if_ole.html">if_ole</a></li>
<li><a href="if_ruby.html">if_ruby</a></li>
<li><a href="debugger.html">debugger</a></li>
<li><a href="workshop.html">workshop</a></li>
<li><a href="netbeans.html">netbeans</a></li>
<li><a href="sign.html">sign</a></li>
</ul></dd>
<dt>Versions</dt>
<dd><ul>
<li><a href="vi_diff.html">vi_diff</a></li>
<li><a href="version4.html">version4</a></li>
<li><a href="version5.html">version5</a></li>
<li><a href="version6.html">version6</a></li>
<li><a href="version7.html">version7</a></li>
<li><a href="version8.html">version8</a></li>
</ul></dd>
<dt>Remarks about specific systems</dt>
<dd><ul>
<li><a href="os_390.html">os_390</a></li>
<li><a href="os_amiga.html">os_amiga</a></li>
<li><a href="os_beos.html">os_beos</a></li>
<li><a href="os_dos.html">os_dos</a></li>
<li><a href="os_mac.html">os_mac</a></li>
<li><a href="os_mint.html">os_mint</a></li>
<li><a href="os_msdos.html">os_msdos</a></li>
<li><a href="os_os2.html">os_os2</a></li>
<li><a href="os_qnx.html">os_qnx</a></li>
<li><a href="os_risc.html">os_risc</a></li>
<li><a href="os_unix.html">os_unix</a></li>
<li><a href="os_vms.html">os_vms</a></li>
<li><a href="os_win32.html">os_win32</a></li>
</ul></dd>
<dt>Standard plugins</dt>
<dd><ul>
<li><a href="pi_getscript.html">pi_getscript</a></li>
<li><a href="pi_gzip.html">pi_gzip</a></li>
<li><a href="pi_logipat.html">pi_logipat</a></li>
<li><a href="pi_netrw.html">pi_netrw</a></li>
<li><a href="pi_paren.html">pi_paren</a></li>
<li><a href="pi_tar.html">pi_tar</a></li>
<li><a href="pi_vimball.html">pi_vimball</a></li>
<li><a href="pi_zip.html">pi_zip</a></li>
</ul></dd>
<dt>Filetype plugins</dt>
<dd><ul>
<li><a href="pi_spec.html">pi_spec</a></li>
</ul></dd>
<dt>Others</dt>
<dd><ul>
<li><a href="vim_faq.html">vim_faq</a></li>
</ul></dd>
</dl>
</nav>
<article class="Vimdoc VimdocJa">
<div id='vimCodeElement'>
<a class="Constant" href="usr_90.html" name="usr_90.txt">usr_90.txt</a> For <span class="Identifier">Vim version 8.0.</span> Last change: 2008 Sep 10<br>
<br>
VIM USER MANUAL - by Bram Moolenaar<br>
<br>
Installing Vim<br>
<br>
<a class="Constant" href="usr_90.html#install" name="install">install</a><br>
Before you can use Vim you have to install it. Depending on your system it's<br>
simple or easy. This chapter gives a few hints and also explains how<br>
upgrading to a new version is done.<br>
<br>
<a class="Identifier" href="usr_90.html#90.1">90.1</a> Unix<br>
<a class="Identifier" href="usr_90.html#90.2">90.2</a> MS-Windows<br>
<a class="Identifier" href="usr_90.html#90.3">90.3</a> Upgrading<br>
<a class="Identifier" href="usr_90.html#90.4">90.4</a> Common installation issues<br>
<a class="Identifier" href="usr_90.html#90.5">90.5</a> Uninstalling Vim<br>
<br>
Previous chapter: <a class="Identifier" href="usr_45.html">usr_45.txt</a> Select your language<br>
Table of contents: <a class="Identifier" href="usr_toc.html">usr_toc.txt</a><br>
<br>
<span class="PreProc">==============================================================================</span><br>
<a class="Constant" href="usr_90.html#90.1" name="90.1">90.1</a> Unix<br>
<br>
First you have to decide if you are going to install Vim system-wide or for a<br>
single user. The installation is almost the same, but the directory where Vim<br>
is installed in differs.<br>
For a system-wide installation the base directory "/usr/local" is often<br>
used. But this may be different for your system. Try finding out where other<br>
packages are installed.<br>
When installing for a single user, you can use your home directory as the<br>
base. The files will be placed in subdirectories like "bin" and "shared/vim".<br>
<br>
<br>
FROM A PACKAGE<br>
<br>
You can get precompiled binaries for many different UNIX systems. There is a<br>
long list with links on this page:<br>
<br>
<span class="Constant"><a href="http://www.vim.org/binaries.html">http://www.vim.org/binaries.html</a></span> <br>
<br>
Volunteers maintain the binaries, so they are often out of date. It is a<br>
good idea to compile your own UNIX version from the source. Also, creating<br>
the editor from the source allows you to control which features are compiled.<br>
This does require a compiler though.<br>
<br>
If you have a Linux distribution, the "vi" program is probably a minimal<br>
version of Vim. It doesn't do syntax highlighting, for example. Try finding<br>
another Vim package in your distribution, or search on the web site.<br>
<br>
<br>
FROM SOURCES<br>
<br>
To compile and install Vim, you will need the following:<br>
<br>
- A C compiler (GCC preferred)<br>
- The GZIP program (you can get it from <span class="Constant">www.gnu.org</span>)<br>
- The Vim source and runtime archives<br>
<br>
To get the Vim archives, look in this file for a mirror near you, this should<br>
provide the fastest download:<br>
<br>
<span class="Constant">ftp://ftp.vim.org/pub/vim/MIRRORS</span> <br>
<br>
Or use the home site ftp.vim.org, if you think it's fast enough. Go to the<br>
"unix" directory and you'll find a list of files there. The version number is<br>
embedded in the file name. You will want to get the most recent version.<br>
You can get the files for Unix in two ways: One big archive that contains<br>
everything, or four smaller ones that each fit on a floppy disk. For version<br>
6.1 the single big one is called:<br>
<br>
<span class="PreProc">vim-6.1.tar.bz2</span><br>
<br>
You need the bzip2 program to uncompress it. If you don't have it, get the<br>
four smaller files, which can be uncompressed with gzip. For Vim 6.1 they are<br>
called:<br>
<br>
<span class="PreProc">vim-6.1-src1.tar.gz</span><br>
<span class="PreProc">vim-6.1-src2.tar.gz</span><br>
<span class="PreProc">vim-6.1-rt1.tar.gz</span><br>
<span class="PreProc">vim-6.1-rt2.tar.gz</span><br>
<br>
<br>
COMPILING<br>
<br>
First create a top directory to work in, for example:<br>
<br>
<div class="helpExample"> mkdir ~/vim<br>
cd ~/vim</div>
<br>
Then unpack the archives there. If you have the one big archive, you unpack<br>
it like this:<br>
<br>
<div class="helpExample"> bzip2 -d -c path/vim-6.1.tar.bz2 | tar xf -</div>
<br>
Change "path" to where you have downloaded the file.<br>
<br>
<div class="helpExample"> gzip -d -c path/vim-6.1-src1.tar.gz | tar xf -<br>
gzip -d -c path/vim-6.1-src2.tar.gz | tar xf -<br>
gzip -d -c path/vim-6.1-rt1.tar.gz | tar xf -<br>
gzip -d -c path/vim-6.1-rt2.tar.gz | tar xf -</div>
<br>
If you are satisfied with getting the default features, and your environment<br>
is setup properly, you should be able to compile Vim with just this:<br>
<br>
<div class="helpExample"> cd vim61/src<br>
make</div>
<br>
The make program will run configure and compile everything. Further on we<br>
will explain how to compile with different features.<br>
If there are errors while compiling, carefully look at the error messages.<br>
There should be a hint about what went wrong. Hopefully you will be able to<br>
correct it. You might have to disable some features to make Vim compile.<br>
Look in the Makefile for specific hints for your system.<br>
<br>
<br>
TESTING<br>
<br>
Now you can check if compiling worked OK:<br>
<br>
<div class="helpExample"> make test</div>
<br>
This will run a sequence of test scripts to verify that Vim works as expected.<br>
Vim will be started many times and all kinds of text and messages flash by.<br>
If it is alright you will finally see:<br>
<br>
<span class="PreProc">test results:</span><br>
<span class="PreProc">ALL DONE</span><br>
<br>
If you get "TEST FAILURE" some test failed. If there are one or two messages<br>
about failed tests, Vim might still work, but not perfectly. If you see a lot<br>
of error messages or Vim doesn't finish until the end, there must be something<br>
wrong. Either try to find out yourself, or find someone who can solve it.<br>
You could look in the <a class="Identifier" href="intro.html#maillist-archive">maillist-archive</a> for a solution. If everything else<br>
fails, you could ask in the vim <a class="Identifier" href="intro.html#maillist">maillist</a> if someone can help you.<br>
<br>
<br>
INSTALLING<br>
<a class="Constant" href="usr_90.html#install-home" name="install-home">install-home</a><br>
If you want to install in your home directory, edit the Makefile and search<br>
for a line:<br>
<br>
<span class="PreProc">#prefix = $(HOME)</span><br>
<br>
Remove the # at the start of the line.<br>
When installing for the whole system, Vim has most likely already selected<br>
a good installation directory for you. You can also specify one, see below.<br>
You need to become root for the following.<br>
<br>
To install Vim do:<br>
<br>
<div class="helpExample"> make install</div>
<br>
That should move all the relevant files to the right place. Now you can try<br>
running vim to verify that it works. Use two simple tests to check if Vim can<br>
find its runtime files:<br>
<br>
<div class="helpExample"> :help<br>
:syntax enable</div>
<br>
If this doesn't work, use this command to check where Vim is looking for the<br>
runtime files:<br>
<br>
<div class="helpExample"> :echo $VIMRUNTIME</div>
<br>
You can also start Vim with the "-V" argument to see what happens during<br>
startup:<br>
<br>
<div class="helpExample"> vim -V</div>
<br>
Don't forget that the user manual assumes you Vim in a certain way. After<br>
installing Vim, follow the instructions at <a class="Identifier" href="usr_01.html#not-compatible">not-compatible</a> to make Vim work<br>
as assumed in this manual.<br>
<br>
<br>
SELECTING FEATURES<br>
<br>
Vim has many ways to select features. One of the simple ways is to edit the<br>
Makefile. There are many directions and examples. Often you can enable or<br>
disable a feature by uncommenting a line.<br>
An alternative is to run "configure" separately. This allows you to<br>
specify configuration options manually. The disadvantage is that you have to<br>
figure out what exactly to type.<br>
Some of the most interesting configure arguments follow. These can also be<br>
enabled from the Makefile.<br>
<br>
--prefix=<span class="Special">{directory}</span> Top directory where to install Vim.<br>
<br>
--with-features=tiny Compile with many features disabled.<br>
--with-features=small Compile with some features disabled.<br>
--with-features=big Compile with more features enabled.<br>
--with-features=huge Compile with most features enabled.<br>
See <a class="Identifier" href="various.html#+feature-list">+feature-list</a> for which feature<br>
is enabled in which case.<br>
<br>
--enable-perlinterp Enable the Perl interface. There are<br>
similar arguments for ruby, python and<br>
tcl.<br>
<br>
--disable-gui Do not compile the GUI interface.<br>
--without-x Do not compile X-windows features.<br>
When both of these are used, Vim will<br>
not connect to the X server, which<br>
makes startup faster.<br>
<br>
To see the whole list use:<br>
<br>
<div class="helpExample"> ./configure --help</div>
<br>
You can find a bit of explanation for each feature, and links for more<br>
information here: <a class="Identifier" href="eval.html#feature-list">feature-list</a>.<br>
For the adventurous, edit the file "feature.h". You can also change the<br>
source code yourself!<br>
<br>
<span class="PreProc">==============================================================================</span><br>
<a class="Constant" href="usr_90.html#90.2" name="90.2">90.2</a> MS-Windows<br>
<br>
There are two ways to install the Vim program for Microsoft Windows. You can<br>
uncompress several archives, or use a self-installing big archive. Most users<br>
with fairly recent computers will prefer the second method. For the first<br>
one, you will need:<br>
<br>
- An archive with binaries for Vim.<br>
- The Vim runtime archive.<br>
- A program to unpack the zip files.<br>
<br>
To get the Vim archives, look in this file for a mirror near you, this should<br>
provide the fastest download:<br>
<br>
<span class="Constant">ftp://ftp.vim.org/pub/vim/MIRRORS</span> <br>
<br>
Or use the home site ftp.vim.org, if you think it's fast enough. Go to the<br>
"pc" directory and you'll find a list of files there. The version number is<br>
embedded in the file name. You will want to get the most recent version.<br>
We will use "61" here, which is version 6.1.<br>
<br>
gvim61.exe The self-installing archive.<br>
<br>
This is all you need for the second method. Just launch the executable, and<br>
follow the prompts.<br>
<br>
For the first method you must chose one of the binary archives. These are<br>
available:<br>
<br>
gvim61.zip The normal MS-Windows GUI version.<br>
gvim61ole.zip The MS-Windows GUI version with OLE support.<br>
Uses more memory, supports interfacing with<br>
other OLE applications.<br>
vim61w32.zip 32 bit MS-Windows console version. For use in<br>
a Win NT/2000/XP console. Does not work well<br>
on Win 95/98.<br>
vim61d32.zip 32 bit MS-DOS version. For use in the<br>
Win 95/98 console window.<br>
vim61d16.zip 16 bit MS-DOS version. Only for old systems.<br>
Does not support long filenames.<br>
<br>
You only need one of them. Although you could install both a GUI and a<br>
console version. You always need to get the archive with runtime files.<br>
<br>
vim61rt.zip The runtime files.<br>
<br>
Use your un-zip program to unpack the files. For example, using the "unzip"<br>
program:<br>
<br>
<div class="helpExample"> cd c:\<br>
unzip path\gvim61.zip<br>
unzip path\vim61rt.zip</div>
<br>
This will unpack the files in the directory "c:\vim\vim61". If you already<br>
have a "vim" directory somewhere, you will want to move to the directory just<br>
above it.<br>
Now change to the "vim\vim61" directory and run the install program:<br>
<br>
<div class="helpExample"> install</div>
<br>
Carefully look through the messages and select the options you want to use.<br>
If you finally select "do it" the install program will carry out the actions<br>
you selected.<br>
The install program doesn't move the runtime files. They remain where you<br>
unpacked them.<br>
<br>
In case you are not satisfied with the features included in the supplied<br>
binaries, you could try compiling Vim yourself. Get the source archive from<br>
the same location as where the binaries are. You need a compiler for which a<br>
makefile exists. Microsoft Visual C works, but is expensive. The Free<br>
Borland command-line compiler 5.5 can be used, as well as the free MingW and<br>
Cygwin compilers. Check the file src/INSTALLpc.txt for hints.<br>
<br>
<span class="PreProc">==============================================================================</span><br>
<a class="Constant" href="usr_90.html#90.3" name="90.3">90.3</a> Upgrading<br>
<br>
If you are running one version of Vim and want to install another, here is<br>
what to do.<br>
<br>
<br>
UNIX<br>
<br>
When you type "make install" the runtime files will be copied to a directory<br>
which is specific for this version. Thus they will not overwrite a previous<br>
version. This makes it possible to use two or more versions next to<br>
each other.<br>
The executable "vim" will overwrite an older version. If you don't care<br>
about keeping the old version, running "make install" will work fine. You can<br>
delete the old runtime files manually. Just delete the directory with the<br>
version number in it and all files below it. Example:<br>
<br>
<div class="helpExample"> rm -rf /usr/local/share/vim/vim58</div>
<br>
There are normally no changed files below this directory. If you did change<br>
the "filetype.vim" file, for example, you better merge the changes into the<br>
new version before deleting it.<br>
<br>
If you are careful and want to try out the new version for a while before<br>
switching to it, install the new version under another name. You need to<br>
specify a configure argument. For example:<br>
<br>
<div class="helpExample"> ./configure --with-vim-name=vim6</div>
<br>
Before running "make install", you could use "make -n install" to check that<br>
no valuable existing files are overwritten.<br>
When you finally decide to switch to the new version, all you need to do is<br>
to rename the binary to "vim". For example:<br>
<br>
<div class="helpExample"> mv /usr/local/bin/vim6 /usr/local/bin/vim</div>
<br>
<br>
MS-WINDOWS<br>
<br>
Upgrading is mostly equal to installing a new version. Just unpack the files<br>
in the same place as the previous version. A new directory will be created,<br>
e.g., "vim61", for the files of the new version. Your runtime files, vimrc<br>
file, viminfo, etc. will be left alone.<br>
If you want to run the new version next to the old one, you will have to do<br>
some handwork. Don't run the install program, it will overwrite a few files<br>
of the old version. Execute the new binaries by specifying the full path.<br>
The program should be able to automatically find the runtime files for the<br>
right version. However, this won't work if you set the $VIMRUNTIME variable<br>
somewhere.<br>
If you are satisfied with the upgrade, you can delete the files of the<br>
previous version. See <a class="Identifier" href="usr_90.html#90.5">90.5</a>.<br>
<br>
<span class="PreProc">==============================================================================</span><br>
<a class="Constant" href="usr_90.html#90.4" name="90.4">90.4</a> Common installation issues<br>
<br>
This section describes some of the common problems that occur when installing<br>
Vim and suggests some solutions. It also contains answers to many<br>
installation questions.<br>
<br>
<br>
Q: I Do Not Have Root Privileges. How Do I Install Vim? (Unix)<br>
<br>
Use the following configuration command to install Vim in a directory called<br>
$HOME/vim:<br>
<br>
<div class="helpExample"> ./configure --prefix=$HOME</div>
<br>
This gives you a personal copy of Vim. You need to put $HOME/bin in your<br>
path to execute the editor. Also see <a class="Identifier" href="usr_90.html#install-home">install-home</a>.<br>
<br>
<br>
Q: The Colors Are Not Right on My Screen. (Unix)<br>
<br>
Check your terminal settings by using the following command in a shell:<br>
<br>
<div class="helpExample"> echo $TERM</div>
<br>
If the terminal type listed is not correct, fix it. For more hints, see<br>
<a class="Identifier" href="usr_06.html#06.2">06.2</a>. Another solution is to always use the GUI version of Vim, called<br>
gvim. This avoids the need for a correct terminal setup.<br>
<br>
<br>
Q: My Backspace And Delete Keys Don't Work Right<br>
<br>
The definition of what key sends what code is very unclear for backspace <span class="Special"><BS></span><br>
and Delete <span class="Special"><Del></span> keys. First of all, check your $TERM setting. If there is<br>
nothing wrong with it, try this:<br>
<br>
<div class="helpExample"> :set t_kb=^V<BS><br>
:set t_kD=^V<Del></div>
<br>
In the first line you need to press <span class="Special">CTRL-V</span> and then hit the backspace key.<br>
In the second line you need to press <span class="Special">CTRL-V</span> and then hit the Delete key.<br>
You can put these lines in your vimrc file, see <a class="Identifier" href="usr_05.html#05.1">05.1</a>. A disadvantage is<br>
that it won't work when you use another terminal some day. Look here for<br>
alternate solutions: <a class="Identifier" href="options.html#:fixdel">:fixdel</a>.<br>
<br>
<br>
Q: I Am Using RedHat Linux. Can I Use the Vim That Comes with the System?<br>
<br>
By default RedHat installs a minimal version of Vim. Check your RPM packages<br>
for something named "Vim-enhanced-version.rpm" and install that.<br>
<br>
<br>
Q: How Do I Turn Syntax Coloring On? How do I make plugins work?<br>
<br>
Use the example vimrc script. You can find an explanation on how to use it<br>
here: <a class="Identifier" href="usr_01.html#not-compatible">not-compatible</a>.<br>
<br>
See chapter 6 for information about syntax highlighting: <a class="Identifier" href="usr_06.html">usr_06.txt</a>.<br>
<br>
<br>
Q: What Is a Good vimrc File to Use?<br>
<br>
See the <span class="Constant">www.vim.org</span> Web site for several good examples.<br>
<br>
<br>
Q: Where Do I Find a Good Vim Plugin?<br>
<br>
See the Vim-online site: <span class="Constant"><a href="http://vim.sf.net">http://vim.sf.net</a></span>. Many users have uploaded useful<br>
Vim scripts and plugins there.<br>
<br>
<br>
Q: Where Do I Find More Tips?<br>
<br>
See the Vim-online site: <span class="Constant"><a href="http://vim.sf.net">http://vim.sf.net</a></span>. There is an archive with hints<br>
from Vim users. You might also want to search in the <a class="Identifier" href="intro.html#maillist-archive">maillist-archive</a>.<br>
<br>
<span class="PreProc">==============================================================================</span><br>
<a class="Constant" href="usr_90.html#90.5" name="90.5">90.5</a> Uninstalling Vim<br>
<br>
In the unlikely event you want to uninstall Vim completely, this is how you do<br>
it.<br>
<br>
<br>
UNIX<br>
<br>
When you installed Vim as a package, check your package manager to find out<br>
how to remove the package again.<br>
If you installed Vim from sources you can use this command:<br>
<br>
<div class="helpExample"> make uninstall</div>
<br>
However, if you have deleted the original files or you used an archive that<br>
someone supplied, you can't do this. Do delete the files manually, here is an<br>
example for when "/usr/local" was used as the root:<br>
<br>
<div class="helpExample"> rm -rf /usr/local/share/vim/vim61<br>
rm /usr/local/bin/eview<br>
rm /usr/local/bin/evim<br>
rm /usr/local/bin/ex<br>
rm /usr/local/bin/gview<br>
rm /usr/local/bin/gvim<br>
rm /usr/local/bin/gvim<br>
rm /usr/local/bin/gvimdiff<br>
rm /usr/local/bin/rgview<br>
rm /usr/local/bin/rgvim<br>
rm /usr/local/bin/rview<br>
rm /usr/local/bin/rvim<br>
rm /usr/local/bin/rvim<br>
rm /usr/local/bin/view<br>
rm /usr/local/bin/vim<br>
rm /usr/local/bin/vimdiff<br>
rm /usr/local/bin/vimtutor<br>
rm /usr/local/bin/xxd<br>
rm /usr/local/man/man1/eview.1<br>
rm /usr/local/man/man1/evim.1<br>
rm /usr/local/man/man1/ex.1<br>
rm /usr/local/man/man1/gview.1<br>
rm /usr/local/man/man1/gvim.1<br>
rm /usr/local/man/man1/gvimdiff.1<br>
rm /usr/local/man/man1/rgview.1<br>
rm /usr/local/man/man1/rgvim.1<br>
rm /usr/local/man/man1/rview.1<br>
rm /usr/local/man/man1/rvim.1<br>
rm /usr/local/man/man1/view.1<br>
rm /usr/local/man/man1/vim.1<br>
rm /usr/local/man/man1/vimdiff.1<br>
rm /usr/local/man/man1/vimtutor.1<br>
rm /usr/local/man/man1/xxd.1</div>
<br>
<br>
MS-WINDOWS<br>
<br>
If you installed Vim with the self-installing archive you can run<br>
the "uninstall-gui" program located in the same directory as the other Vim<br>
programs, e.g. "c:\vim\vim61". You can also launch it from the Start menu if<br>
installed the Vim entries there. This will remove most of the files, menu<br>
entries and desktop shortcuts. Some files may remain however, as they need a<br>
Windows restart before being deleted.<br>
You will be given the option to remove the whole "vim" directory. It<br>
probably contains your vimrc file and other runtime files that you created, so<br>
be careful.<br>
<br>
Else, if you installed Vim with the zip archives, the preferred way is to use<br>
the "uninstal" program (<span class="Todo">note</span> the missing l at the end). You can find it in<br>
the same directory as the "install" program, e.g., "c:\vim\vim61". This<br>
should also work from the usual "install/remove software" page.<br>
However, this only removes the registry entries for Vim. You have to<br>
delete the files yourself. Simply select the directory "vim\vim61" and delete<br>
it recursively. There should be no files there that you changed, but you<br>
might want to check that first.<br>
The "vim" directory probably contains your vimrc file and other runtime<br>
files that you created. You might want to keep that.<br>
<br>
<span class="PreProc">==============================================================================</span><br>
<br>
Table of contents: <a class="Identifier" href="usr_toc.html">usr_toc.txt</a><br>
<br>
Copyright: see <a class="Identifier" href="usr_01.html#manual-copyright">manual-copyright</a> vim:tw=78:ts=8:ft=help:norl:<br>
</div>
</article>
<footer>
<a href="#top">Return to the top</a> - <a href="index.html">Return to main</a>
<span class="EnglishJapaneseLink">
<span class="CurrentLanguage">English</span>
</span>
<br />
<div style="text-align:right;">
Hosted by <a href="https://github.com/vim-jp/vimdoc-en">vimdoc-en project</a><br />
If you met any problem, please report it to <a href="https://github.com/vim-jp/vimdoc-en/issues">issue</a>.<br />
</div>
</footer>
<!--<script src="js/check-referrer.js" type="text/javascript"></script>-->
</body>
</html>
<!-- vim:set ts=8 sts=2 sw=2 tw=0 et: -->
此处可能存在不合适展示的内容，页面不予展示。您可通过相关编辑功能自查并修改。
如您确认内容无涉及 不当用语 / 纯广告导流 / 暴力 / 低俗色情 / 侵权 / 盗版 / 虚假 / 无价值内容或违法国家有关法律法规的内容，可点击提交进行申诉，我们将尽快为您处理。
马建仓 AI 助手