diff options
author | Bram Moolenaar <Bram@vim.org> | 2017-06-05 14:44:35 +0200 |
---|---|---|
committer | Bram Moolenaar <Bram@vim.org> | 2017-06-05 14:44:35 +0200 |
commit | 6aa8cea46d4179b2617daae034063dd0d8054e35 (patch) | |
tree | 25d3a8b4123803ec00dfab58f8b31b8e2c21a59f /runtime/doc | |
parent | 9472eec83c3f9c191814dc81dd82498c10b1fc9c (diff) |
Update runtime files.
Diffstat (limited to 'runtime/doc')
-rw-r--r-- | runtime/doc/arabic.txt | 40 | ||||
-rw-r--r-- | runtime/doc/autocmd.txt | 2 | ||||
-rw-r--r-- | runtime/doc/eval.txt | 3 | ||||
-rw-r--r-- | runtime/doc/ft_ada.txt | 2 | ||||
-rw-r--r-- | runtime/doc/hangulin.txt | 16 | ||||
-rw-r--r-- | runtime/doc/help.txt | 2 | ||||
-rw-r--r-- | runtime/doc/if_ole.txt | 4 | ||||
-rw-r--r-- | runtime/doc/if_perl.txt | 4 | ||||
-rw-r--r-- | runtime/doc/insert.txt | 14 | ||||
-rw-r--r-- | runtime/doc/intro.txt | 4 | ||||
-rw-r--r-- | runtime/doc/map.txt | 6 | ||||
-rw-r--r-- | runtime/doc/netbeans.txt | 4 | ||||
-rw-r--r-- | runtime/doc/options.txt | 12 | ||||
-rw-r--r-- | runtime/doc/os_beos.txt | 2 | ||||
-rw-r--r-- | runtime/doc/os_vms.txt | 10 | ||||
-rw-r--r-- | runtime/doc/os_win32.txt | 2 | ||||
-rw-r--r-- | runtime/doc/pi_getscript.txt | 4 | ||||
-rw-r--r-- | runtime/doc/print.txt | 64 | ||||
-rw-r--r-- | runtime/doc/quotes.txt | 114 | ||||
-rw-r--r-- | runtime/doc/spell.txt | 4 | ||||
-rw-r--r-- | runtime/doc/syntax.txt | 11 | ||||
-rw-r--r-- | runtime/doc/todo.txt | 59 | ||||
-rw-r--r-- | runtime/doc/usr_09.txt | 4 | ||||
-rw-r--r-- | runtime/doc/version6.txt | 4 | ||||
-rw-r--r-- | runtime/doc/version7.txt | 120 |
25 files changed, 259 insertions, 252 deletions
diff --git a/runtime/doc/arabic.txt b/runtime/doc/arabic.txt index 42fd878b5d..5d0e9f39db 100644 --- a/runtime/doc/arabic.txt +++ b/runtime/doc/arabic.txt @@ -10,11 +10,11 @@ Arabic Language support (options & mappings) for Vim *Arabic* *E800* In order to use right-to-left and Arabic mapping support, it is -necessary to compile VIM with the |+arabic| feature. +necessary to compile Vim with the |+arabic| feature. These functions have been created by Nadim Shaikli <nadim-at-arabeyes.org> -It is best to view this file with these settings within VIM's GUI: > +It is best to view this file with these settings within Vim's GUI: > :set encoding=utf-8 :set arabicshape @@ -42,7 +42,7 @@ the user interface remains the standard Vi interface. Highlights ---------- -o Editing left-to-right files as in the original VIM hasn't changed. +o Editing left-to-right files as in the original Vim hasn't changed. o Viewing and editing files in right-to-left windows. File orientation is per window, so it is possible to view the same @@ -52,7 +52,7 @@ o No special terminal with right-to-left capabilities is required. The right-to-left changes are completely hardware independent. Only Arabic fonts are necessary. -o Compatible with the original VIM. Almost all features work in +o Compatible with the original Vim. Almost all features work in right-to-left mode (there are liable to be bugs). o Changing keyboard mapping and reverse insert modes using a single @@ -66,14 +66,14 @@ o While in Arabic mode, numbers are entered from left to right. Upon o Arabic keymapping on the command line in reverse insert mode. -o Proper Bidirectional functionality is possible given VIM is +o Proper Bidirectional functionality is possible given Vim is started within a Bidi capable terminal emulator. Arabic Fonts *arabicfonts* ------------ -VIM requires monospaced fonts of which there are many out there. +Vim requires monospaced fonts of which there are many out there. Arabic requires ISO-8859-6 as well as Presentation Form-B fonts (without Form-B, Arabic will _NOT_ be usable). It is highly recommended that users search for so-called 'ISO-10646-1' fonts. @@ -96,13 +96,13 @@ o Installation of fonts for X Window systems (Unix/Linux) Usage ----- -Prior to the actual usage of Arabic within VIM, a number of settings +Prior to the actual usage of Arabic within Vim, a number of settings need to be accounted for and invoked. o Setting the Arabic fonts - + For VIM GUI set the 'guifont' to your_ARABIC_FONT. This is done - by entering the following command in the VIM window. + + For Vim GUI set the 'guifont' to your_ARABIC_FONT. This is done + by entering the following command in the Vim window. > :set guifont=your_ARABIC_FONT < @@ -115,7 +115,7 @@ o Setting the Arabic fonts you can include ':set guifont=your_ARABIC_FONT' to your .vimrc file. - + Under the X Window environment, you can also start VIM with + + Under the X Window environment, you can also start Vim with '-fn your_ARABIC_FONT' option. o Setting the appropriate character Encoding @@ -124,7 +124,7 @@ o Setting the appropriate character Encoding > :set encoding=utf-8 < - to your .vimrc file (entering the command manually into you VIM + to your .vimrc file (entering the command manually into you Vim window is highly discouraged). In short, include ':set encoding=utf-8' to your .vimrc file. @@ -137,11 +137,11 @@ o Setting the appropriate character Encoding o Enable Arabic settings [short-cut] In order to simplify and streamline things, you can either invoke - VIM with the command-line option, + Vim with the command-line option, % vim -A my_utf8_arabic_file ... - or enable 'arabic' via the following command within VIM + or enable 'arabic' via the following command within Vim > :set arabic < @@ -189,7 +189,7 @@ o Enable Arabic settings [short-cut] > :set keymap=arabic < - in your VIM window. You can also append the 'keymap' set command to + in your Vim window. You can also append the 'keymap' set command to your .vimrc file. In other words, you can include ':set keymap=arabic' to your .vimrc file. @@ -202,7 +202,7 @@ o Enable Arabic settings [short-cut] + Arabic deletion of a combined pair character - By default VIM has the 'delcombine' option disabled. This option + By default Vim has the 'delcombine' option disabled. This option allows the deletion of ALEF in a LAM_ALEF (LAA) combined character and still retain the LAM (i.e. it reverts to treating the combined character as its natural two characters form -- this also pertains @@ -211,13 +211,13 @@ o Enable Arabic settings [short-cut] > :set delcombine < - in our VIM window. You can also append the 'delcombine' set command + in our Vim window. You can also append the 'delcombine' set command to your .vimrc file. In other words, you can include ':set delcombine' to your .vimrc file. + Arabic right-to-left Mode - By default VIM starts in Left-to-right mode. 'rightleft' is the + By default Vim starts in Left-to-right mode. 'rightleft' is the command that allows one to alter a window's orientation - that can be accomplished via, @@ -253,7 +253,7 @@ o Enable Arabic settings [short-cut] > :set arabicshape < - in our VIM window. You can also append the 'arabicshape' set + in our Vim window. You can also append the 'arabicshape' set command to your .vimrc file. In other words, you can include ':set arabicshape' to your .vimrc file. @@ -261,7 +261,7 @@ o Enable Arabic settings [short-cut] Keymap/Keyboard *arabickeymap* --------------- -The character/letter encoding used in VIM is the standard UTF-8. +The character/letter encoding used in Vim is the standard UTF-8. It is widely discouraged that any other encoding be used or even attempted. @@ -294,7 +294,7 @@ o Keyboard Restrictions ------------ -o VIM in its GUI form does not currently support Bi-directionality +o Vim in its GUI form does not currently support Bi-directionality (i.e. the ability to see both Arabic and Latin intermixed within the same line). diff --git a/runtime/doc/autocmd.txt b/runtime/doc/autocmd.txt index 575e8523dc..b2d1c24fe9 100644 --- a/runtime/doc/autocmd.txt +++ b/runtime/doc/autocmd.txt @@ -610,7 +610,7 @@ FileChangedShell When Vim notices that the modification time of |timestamp| Mostly triggered after executing a shell command, but also with a |:checktime| command - or when Gvim regains input focus. + or when gvim regains input focus. This autocommand is triggered for each changed file. It is not used when 'autoread' is set and the buffer was not changed. If a diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt index 6a0013ab94..0f3d27a6c2 100644 --- a/runtime/doc/eval.txt +++ b/runtime/doc/eval.txt @@ -1,4 +1,4 @@ -*eval.txt* For Vim version 8.0. Last change: 2017 May 02 +*eval.txt* For Vim version 8.0. Last change: 2017 Jun 04 VIM REFERENCE MANUAL by Bram Moolenaar @@ -3373,6 +3373,7 @@ did_filetype() Returns |TRUE| when autocommands are being executed and the FileType event has been triggered at least once. Can be used to avoid triggering the FileType event again in the scripts that detect the file type. |FileType| + Returns |FALSE| when `:setf FALLBACK` was used. When editing another file, the counter is reset, thus this really checks if the FileType event has been triggered for the current buffer. This allows an autocommand that starts diff --git a/runtime/doc/ft_ada.txt b/runtime/doc/ft_ada.txt index 81d7ceab59..5f1b78e2e4 100644 --- a/runtime/doc/ft_ada.txt +++ b/runtime/doc/ft_ada.txt @@ -116,7 +116,7 @@ NOTE: "gnat xref -v" is very tricky to use as it has almost no diagnostic then "gnat xref -v *.ad?" 4) Project manager support is completely broken - don't even try "gnat xref -Padacl.gpr". -5) VIM is faster when the tags file is sorted - use "sort --unique +5) Vim is faster when the tags file is sorted - use "sort --unique --ignore-case --output=tags tags" . 6) Remember to insert "!_TAG_FILE_SORTED 2 %sort ui" as first line to mark the file assorted. diff --git a/runtime/doc/hangulin.txt b/runtime/doc/hangulin.txt index 009250116f..08fb6126bd 100644 --- a/runtime/doc/hangulin.txt +++ b/runtime/doc/hangulin.txt @@ -6,7 +6,7 @@ Introduction *hangul* ------------ -It is to input hangul, the Korean language, with VIM GUI version. +It is to input hangul, the Korean language, with Vim GUI version. If you have a XIM program, you can use another |+xim| feature. Basically, it is for anybody who has no XIM program. @@ -31,7 +31,7 @@ You should set LANG variable to Korean locale such as ko, ko_KR.eucKR or ko_KR.UTF-8. If you set LC_ALL variable, it should be set to Korean locale also. -VIM resource +Vim resource ------------ You may want to set 'encoding' and 'fileencodings'. Next are examples: > @@ -53,12 +53,12 @@ If both are set, VIM_KEYBOARD has higher priority. Hangul Fonts ------------ -If you use GTK version of GVIM, you should set 'guifont' and 'guifontwide'. +If you use GTK version of gvim, you should set 'guifont' and 'guifontwide'. For example: > set guifont=Courier\ 12 set guifontwide=NanumGothicCoding\ 12 -If you use Motif or Athena version of GVIM, you should set 'guifontset' in +If you use Motif or Athena version of gvim, you should set 'guifontset' in your vimrc. You can set fontset in the .Xdefaults file. $HOME/.gvimrc: > @@ -77,11 +77,11 @@ $HOME/.Xdefaults: > attention! the , (comma) or ; (semicolon) -And there should be no ':set guifont'. If it exists, then Gvim ignores -':set guifontset'. It means VIM runs without fontset supporting. +And there should be no ':set guifont'. If it exists, then gvim ignores +':set guifontset'. It means Vim runs without fontset supporting. So, you can see only English. Hangul does not be correctly displayed. -After "fontset" feature is enabled, VIM does not allow using english +After "fontset" feature is enabled, Vim does not allow using english font only in "font" setting for syntax. For example, if you use > :set guifontset=eng_font,your_font @@ -99,7 +99,7 @@ We don't support Johab font. We don't support Hanja input. And We don't have any plan to support them. -If you really need such features, you can use console version of VIM with a +If you really need such features, you can use console version of Vim with a capable terminal emulator. Bug or Comment diff --git a/runtime/doc/help.txt b/runtime/doc/help.txt index 58049f656f..2be3ced374 100644 --- a/runtime/doc/help.txt +++ b/runtime/doc/help.txt @@ -31,7 +31,7 @@ Get specific help: It is possible to go directly to whatever you want help help entries for "word". Or use ":helpgrep word". |:helpgrep| -VIM stands for Vi IMproved. Most of VIM was made by Bram Moolenaar, but only +Vim stands for Vi IMproved. Most of Vim was made by Bram Moolenaar, but only through the help of many others. See |credits|. ------------------------------------------------------------------------------ *doc-file-list* *Q_ct* diff --git a/runtime/doc/if_ole.txt b/runtime/doc/if_ole.txt index 6a30a5807e..be84f43b17 100644 --- a/runtime/doc/if_ole.txt +++ b/runtime/doc/if_ole.txt @@ -41,9 +41,9 @@ instance), code similar to the following should be used: $vim = new Win32::OLE 'Vim.Application'; [C#] > - // Add a reference to VIM in your project. + // Add a reference to Vim in your project. // Choose the COM tab. - // Select "VIM Ole Interface 1.1 Type Library" + // Select "Vim Ole Interface 1.1 Type Library" Vim.Vim vimobj = new Vim.Vim(); Vim does not support acting as a "hidden" OLE server, like some other OLE diff --git a/runtime/doc/if_perl.txt b/runtime/doc/if_perl.txt index 84bfc78283..d69c22fb35 100644 --- a/runtime/doc/if_perl.txt +++ b/runtime/doc/if_perl.txt @@ -7,7 +7,7 @@ Perl and Vim *perl* *Perl* 1. Editing Perl files |perl-editing| -2. Compiling VIM with Perl interface |perl-compiling| +2. Compiling Vim with Perl interface |perl-compiling| 3. Using the Perl interface |perl-using| 4. Dynamic loading |perl-dynamic| @@ -33,7 +33,7 @@ Vim in the $VIMRUNTIME/tools directory. This script has currently more features than Exuberant ctags' Perl support. ============================================================================== -2. Compiling VIM with Perl interface *perl-compiling* +2. Compiling Vim with Perl interface *perl-compiling* To compile Vim with Perl interface, you need Perl 5.004 (or later). Perl must be installed before you compile Vim. Vim's Perl interface does NOT work with diff --git a/runtime/doc/insert.txt b/runtime/doc/insert.txt index 2c6900e896..2c4e2d0901 100644 --- a/runtime/doc/insert.txt +++ b/runtime/doc/insert.txt @@ -1,4 +1,4 @@ -*insert.txt* For Vim version 8.0. Last change: 2017 Apr 07 +*insert.txt* For Vim version 8.0. Last change: 2017 May 30 VIM REFERENCE MANUAL by Bram Moolenaar @@ -634,13 +634,13 @@ Completion can be done for: 10. User defined completion |i_CTRL-X_CTRL-U| 11. omni completion |i_CTRL-X_CTRL-O| 12. Spelling suggestions |i_CTRL-X_s| -13. keywords in 'complete' |i_CTRL-N| +13. keywords in 'complete' |i_CTRL-N| |i_CTRL-P| -All these (except 2) are done in CTRL-X mode. This is a sub-mode of Insert -and Replace modes. You enter CTRL-X mode by typing CTRL-X and one of the -CTRL-X commands. You exit CTRL-X mode by typing a key that is not a valid -CTRL-X mode command. Valid keys are the CTRL-X command itself, CTRL-N (next), -and CTRL-P (previous). +All these, except CTRL-N and CTRL-P, are done in CTRL-X mode. This is a +sub-mode of Insert and Replace modes. You enter CTRL-X mode by typing CTRL-X +and one of the CTRL-X commands. You exit CTRL-X mode by typing a key that is +not a valid CTRL-X mode command. Valid keys are the CTRL-X command itself, +CTRL-N (next), and CTRL-P (previous). Also see the 'infercase' option if you want to adjust the case of the match. diff --git a/runtime/doc/intro.txt b/runtime/doc/intro.txt index d6664ff45d..3dfea22930 100644 --- a/runtime/doc/intro.txt +++ b/runtime/doc/intro.txt @@ -84,8 +84,8 @@ The Vim pages contain the most recent information about Vim. They also contain links to the most recent version of Vim. The FAQ is a list of Frequently Asked Questions. Read this if you have problems. - VIM home page: http://www.vim.org/ - VIM FAQ: http://vimdoc.sf.net/ + Vim home page: http://www.vim.org/ + Vim FAQ: http://vimdoc.sf.net/ Downloading: ftp://ftp.vim.org/pub/vim/MIRRORS diff --git a/runtime/doc/map.txt b/runtime/doc/map.txt index 7d723cea93..239c7915c9 100644 --- a/runtime/doc/map.txt +++ b/runtime/doc/map.txt @@ -1,4 +1,4 @@ -*map.txt* For Vim version 8.0. Last change: 2017 Mar 10 +*map.txt* For Vim version 8.0. Last change: 2017 May 30 VIM REFERENCE MANUAL by Bram Moolenaar @@ -185,7 +185,7 @@ that starts with ",". Then you need to type another character for Vim to know whether to use the "," mapping or the longer one. To avoid this add the <nowait> argument. Then the mapping will be used when it matches, Vim does not wait for more characters to be typed. However, if the characters were -already type they are used. +already typed they are used. *:map-<silent>* *:map-silent* To define a mapping which will not be echoed on the command line, add @@ -798,7 +798,7 @@ Bear in mind that convert-meta has been reported to have troubles when used in UTF-8 locales. On terminals like xterm, the "metaSendsEscape" resource can be toggled on the fly through the "Main Options" menu, by pressing Ctrl-LeftClick on the terminal; that's a good last resource in case you want to send ESC when -using other applications but not when inside VIM. +using other applications but not when inside Vim. 1.11 MAPPING AN OPERATOR *:map-operator* diff --git a/runtime/doc/netbeans.txt b/runtime/doc/netbeans.txt index fb54b809d6..722cec6554 100644 --- a/runtime/doc/netbeans.txt +++ b/runtime/doc/netbeans.txt @@ -120,7 +120,7 @@ In case you do not want the NetBeans interface you can disable it by uncommenting a line with "--disable-netbeans" in the Makefile. Currently the NetBeans interface is supported by Vim running in a terminal and -by GVim when it is run with one of the following GUIs: GTK, GNOME, Windows, +by gvim when it is run with one of the following GUIs: GTK, GNOME, Windows, Athena and Motif. If Motif support is required the user must supply XPM libraries. See @@ -996,7 +996,7 @@ to "Vim". In the Expert tab make sure the "Vim Command" is correct. You should be careful if you change the "Vim Command". There are command line options there which must be there for the connection to be properly set up. You can change the command name but that's about it. If your gvim -can be found by your $PATH then the VIM Command can start with "gvim". If +can be found by your $PATH then the Vim Command can start with "gvim". If you don't want gvim searched from your $PATH then hard code in the full Unix path name. At this point you should get a gvim for any source file you open in NetBeans. diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt index c6fc424284..25b3f1835b 100644 --- a/runtime/doc/options.txt +++ b/runtime/doc/options.txt @@ -1,4 +1,4 @@ -*options.txt* For Vim version 8.0. Last change: 2017 May 08 +*options.txt* For Vim version 8.0. Last change: 2017 Jun 04 VIM REFERENCE MANUAL by Bram Moolenaar @@ -370,7 +370,7 @@ Note: In the future more global options can be made global-local. Using Setting the filetype -:setf[iletype] {filetype} *:setf* *:setfiletype* +:setf[iletype] [FALLBACK] {filetype} *:setf* *:setfiletype* Set the 'filetype' option to {filetype}, but only if not done yet in a sequence of (nested) autocommands. This is short for: > @@ -380,6 +380,13 @@ Setting the filetype < This command is used in a filetype.vim file to avoid setting the 'filetype' option twice, causing different settings and syntax files to be loaded. + + When the optional FALLBACK argument is present, a + later :setfiletype command will override the + 'filetype'. This is to used for filetype detections + that are just a guess. |did_filetype()| will return + false after this command. + {not in Vi} *option-window* *optwin* @@ -7735,6 +7742,7 @@ A jump table for the options with a short description can be found at |Q_op|. compatible terminal. If setting this option does not work (produces a colorless UI) reading |xterm-true-color| might help. + Note that the "cterm" attributes are still used, not the "gui" ones. NOTE: This option is reset when 'compatible' is set. *'terse'* *'noterse'* diff --git a/runtime/doc/os_beos.txt b/runtime/doc/os_beos.txt index f63eeaac00..06749bed8b 100644 --- a/runtime/doc/os_beos.txt +++ b/runtime/doc/os_beos.txt @@ -144,7 +144,7 @@ The default value for $VIM is set at compile time and can be determined with > :version The normal value is /boot/home/config/share/vim. If you don't like it you can -set the VIM environment variable to override this, or set 'helpfile' in your +set the Vim environment variable to override this, or set 'helpfile' in your .vimrc: > :if version >= 500 diff --git a/runtime/doc/os_vms.txt b/runtime/doc/os_vms.txt index 53f6fe5e57..5cf2378c37 100644 --- a/runtime/doc/os_vms.txt +++ b/runtime/doc/os_vms.txt @@ -539,7 +539,7 @@ More info under :help hardcopy 8.10 Setting up the symbols -When I use GVIM this way and press CTRL-Y in the parent terminal, gvim exits. +When I use gvim this way and press CTRL-Y in the parent terminal, gvim exits. I now use a different symbol that seems to work OK and fixes the problem. I suggest this instead: > @@ -547,7 +547,7 @@ I suggest this instead: > The /INPUT=NLA0: separates the standard input of the gvim process from the parent terminal, to block signals from the parent window. -Without the -GEOMETRY, the GVIM window size will be minimal and the menu +Without the -GEOMETRY, the gvim window size will be minimal and the menu will be confused after a window-resize. (Carlo Mekenkamp, Coen Engelbarts, Vim 6.0ac) @@ -764,14 +764,14 @@ GNU_TOOLS.ZIP package downloadable from http://www.polarhome.com/vim/ 9. VMS related changes *vms-changes* -Version 7.4 -- Undo: VMS can not handle more than one dot in the filenames use "dir/name" -> "dir/_un_name" +Version 7.4 +- Undo: VMS can not handle more than one dot in the filenames use "dir/name" -> "dir/_un_name" add _un_ at the beginning to keep the extension - correct swap file name wildcard handling - handle iconv usage correctly - do not optimize on vax - otherwise it hangs compiling crypto files - fileio.c fix the comment -- correct RealWaitForChar +- correct RealWaitForChar - after 7.4-119 use different functions lib$cvtf_to_internal_time because Alpha and VAX have G_FLOAT but IA64 uses IEEE float otherwise Vim crashes - guard against crashes that are caused by mixed filenames diff --git a/runtime/doc/os_win32.txt b/runtime/doc/os_win32.txt index 98b37d0ab8..9112dacde2 100644 --- a/runtime/doc/os_win32.txt +++ b/runtime/doc/os_win32.txt @@ -135,7 +135,7 @@ you will need to get a version older than that. 6. Running under Windows 3.1 *win32-win3.1* *win32s* *windows-3.1* *gui-w32s* -There was a special version of Gvim that runs under Windows 3.1 and 3.11. +There was a special version of gvim that runs under Windows 3.1 and 3.11. Support was removed in patch 7.4.1363. ============================================================================== diff --git a/runtime/doc/pi_getscript.txt b/runtime/doc/pi_getscript.txt index 628d9b74e5..66d11ab206 100644 --- a/runtime/doc/pi_getscript.txt +++ b/runtime/doc/pi_getscript.txt @@ -9,7 +9,7 @@ Copyright: (c) 2004-2012 by Charles E. Campbell *glvs-copyright* The VIM LICENSE (see |copyright|) applies to the files in this package, including getscriptPlugin.vim, getscript.vim, GetLatestVimScripts.dist, and pi_getscript.txt, except use "getscript" - instead of "VIM". Like anything else that's free, getscript and its + instead of "Vim". Like anything else that's free, getscript and its associated files are provided *as is* and comes with no warranty of any kind, either expressed or implied. No guarantees of merchantability. No guarantees of suitability for any purpose. By @@ -68,7 +68,7 @@ Your computer needs to have wget or curl for GetLatestVimScripts to do its work. mv GetLatestVimScripts.dist GetLatestVimScripts.dat (edit GetLatestVimScripts.dat to install your own personal list of desired plugins -- see |GetLatestVimScripts_dat|) - + 3. Windows: vim getscript.vba :so % diff --git a/runtime/doc/print.txt b/runtime/doc/print.txt index daa03549cc..62c37cfe63 100644 --- a/runtime/doc/print.txt +++ b/runtime/doc/print.txt @@ -99,25 +99,25 @@ If the option is empty, then vim will use the system default printer for HPUX: hp-roman8, EBCDIC: ebcdic-uk) global -Sets the character encoding used when printing. This option tells VIM which +Sets the character encoding used when printing. This option tells Vim which print character encoding file from the "print" directory in 'runtimepath' to use. This option will accept any value from |encoding-names|. Any recognized names -are converted to VIM standard names - see 'encoding' for more details. Names -not recognized by VIM will just be converted to lower case and underscores +are converted to Vim standard names - see 'encoding' for more details. Names +not recognized by Vim will just be converted to lower case and underscores replaced with '-' signs. -If 'printencoding' is empty or VIM cannot find the file then it will use -'encoding' (if VIM is compiled with |+multi_byte| and it is set an 8-bit -encoding) to find the print character encoding file. If VIM is unable to find +If 'printencoding' is empty or Vim cannot find the file then it will use +'encoding' (if Vim is compiled with |+multi_byte| and it is set an 8-bit +encoding) to find the print character encoding file. If Vim is unable to find a character encoding file then it will use the "latin1" print character encoding file. -When 'encoding' is set to a multi-byte encoding, VIM will try to convert +When 'encoding' is set to a multi-byte encoding, Vim will try to convert characters to the printing encoding for printing (if 'printencoding' is empty then the conversion will be to latin1). Conversion to a printing encoding -other than latin1 will require VIM to be compiled with the |+iconv| feature. +other than latin1 will require Vim to be compiled with the |+iconv| feature. If no conversion is possible then printing will fail. Any characters that cannot be converted will be replaced with upside down question marks. @@ -203,7 +203,7 @@ header is used when this option is empty. 'printmbcharset' 'pmbcs' string (default "") global Sets the CJK character set to be used when generating CJK output from -|:hardcopy|. The following predefined values are currently recognised by VIM: +|:hardcopy|. The following predefined values are currently recognised by Vim: Value Description ~ Chinese GB_2312-80 @@ -270,7 +270,7 @@ Japanese text you would do the following; > If 'printmbcharset' is not one of the above values then it is assumed to specify a custom multi-byte character set and no check will be made that it is -compatible with the value for 'printencoding'. VIM will look for a file +compatible with the value for 'printencoding'. Vim will look for a file defining the character set in the "print" directory in 'runtimepath'. *pmbfn-option* @@ -420,10 +420,10 @@ There are currently a number of limitations with PostScript printing: possible to get all the characters in an encoding to print by installing a new version of the Courier font family. -- Multi-byte support - Currently VIM will try to convert multi-byte characters +- Multi-byte support - Currently Vim will try to convert multi-byte characters to the 8-bit encoding specified by 'printencoding' (or latin1 if it is empty). Any characters that are not successfully converted are shown as - unknown characters. Printing will fail if VIM cannot convert the multi-byte + unknown characters. Printing will fail if Vim cannot convert the multi-byte to the 8-bit encoding. ============================================================================== @@ -434,11 +434,11 @@ you need to define your own PostScript font encoding vector. Details on how to define a font encoding vector is beyond the scope of this help file, but you can find details in the PostScript Language Reference Manual, 3rd Edition, published by Addison-Wesley and available in PDF form at -http://www.adobe.com/. The following describes what you need to do for VIM to +http://www.adobe.com/. The following describes what you need to do for Vim to locate and use your print character encoding. i. Decide on a unique name for your encoding vector, one that does not clash - with any of the recognized or standard encoding names that VIM uses (see + with any of the recognized or standard encoding names that Vim uses (see |encoding-names| for a list), and that no one else is likely to use. ii. Copy $VIMRUNTIME/print/latin1.ps to the print subdirectory in your 'runtimepath' and rename it with your unique name. @@ -446,23 +446,23 @@ iii. Edit your renamed copy of latin1.ps, replacing all occurrences of latin1 with your unique name (don't forget the line starting %%Title:), and modify the array of glyph names to define your new encoding vector. The array must have exactly 256 entries or you will not be able to print! -iv. Within VIM, set 'printencoding' to your unique encoding name and then - print your file. VIM will now use your custom print character encoding. +iv. Within Vim, set 'printencoding' to your unique encoding name and then + print your file. Vim will now use your custom print character encoding. -VIM will report an error with the resource file if you change the order or +Vim will report an error with the resource file if you change the order or content of the first 3 lines, other than the name of the encoding on the line starting %%Title: or the version number on the line starting %%Version:. -[Technical explanation for those that know PostScript - VIM looks for a file +[Technical explanation for those that know PostScript - Vim looks for a file with the same name as the encoding it will use when printing. The file defines a new PostScript Encoding resource called /VIM-name, where name is the -print character encoding VIM will use.] +print character encoding Vim will use.] ============================================================================== 5. PostScript CJK Printing *postscript-cjk-printing* *E673* *E674* *E675* -VIM supports printing of Chinese, Japanese, and Korean files. Setting up VIM +Vim supports printing of Chinese, Japanese, and Korean files. Setting up Vim to correctly print CJK files requires setting up a few more options. Each of these countries has many standard character sets and encodings which @@ -483,7 +483,7 @@ option allows you to specify different fonts to use when printing characters which are syntax highlighted with the font styles normal, italic, bold and bold-italic. -No CJK fonts are supplied with VIM. There are some free Korean, Japanese, and +No CJK fonts are supplied with Vim. There are some free Korean, Japanese, and Traditional Chinese fonts available at: http://examples.oreilly.com/cjkvinfo/adobe/samples/ @@ -498,7 +498,7 @@ CJK fonts can be large containing several thousand glyphs, and it is not uncommon to find that they only contain a subset of a national standard. It is not unusual to find the fonts to not include characters for codes in the ASCII code range. If you find half-width Roman characters are not appearing -in your printout then you should configure VIM to use the Courier font the +in your printout then you should configure Vim to use the Courier font the half-width ASCII characters with 'printmbfont'. If your font does not include other characters then you will need to find another font that does. @@ -506,7 +506,7 @@ Another issue with ASCII characters, is that the various national character sets specify a couple of different glyphs in the ASCII code range. If you |