adam/vim
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update runtime files.

Browse Source
This commit is contained in:
Bram Moolenaar
2019-12-26 14:35:26 +01:00
parent 767340574b
commit 5666fcd0bd
48 changed files with 234 additions and 249 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
runtime/doc/usr_05.txt
View File

@ -44,7 +44,7 @@ For Unix and Macintosh this file is always used and is recommended:
~/.vimrc ~
For MS-DOS and MS-Windows you can use one of these:
For MS-Windows you can use one of these:
$HOME/_vimrc ~
$VIM/_vimrc ~
@ -476,7 +476,6 @@ Then copy the file to your plugin directory:
Amiga s:vimfiles/plugin
Macintosh $VIM:vimfiles:plugin
Mac OS X ~/.vim/plugin/
RISC-OS Choices:vimfiles.plugin
Example for Unix (assuming you didn't have a plugin directory yet): >
@ -535,9 +534,9 @@ The underscore is used to separate the name of the filetype from the rest,
which can be anything. If you use "otherstuff.vim" it wouldn't work, it would
be loaded for the "otherstuff" filetype.
On MS-DOS you cannot use long filenames. You would run into trouble if you
add a second plugin and the filetype has more than six characters. You can
use an extra directory to get around this: >
On MS-DOS like filesystems you cannot use long filenames. You would run into
trouble if you add a second plugin and the filetype has more than six
characters. You can use an extra directory to get around this: >
mkdir $VIM/vimfiles/ftplugin/fortran
copy thefile $VIM/vimfiles/ftplugin/fortran/too.vim
@ -586,7 +585,7 @@ the "mkdir" commands if you already have the directory.) >
:!mkdir ~/.vim/plugin
:!cp /tmp/doit.vim ~/.vim/plugin
The "cp" command is for Unix, on MS-DOS you can use "copy".
The "cp" command is for Unix, on MS-Windows you can use "copy".
Now create a "doc" directory in one of the directories in 'runtimepath'. >