From 13fcaaf1954e9f0d5aa53a55084e01b2c2741202 Mon Sep 17 00:00:00 2001 From: Bram Moolenaar Date: Fri, 15 Apr 2005 21:13:42 +0000 Subject: updated for version 7.0066 --- runtime/doc/arabic.txt | 27 +-- runtime/doc/evim-fr.1 | 56 +++++ runtime/doc/farsi.txt | 68 +++--- runtime/doc/filetype.txt | 8 +- runtime/doc/intro.txt | 6 +- runtime/doc/os_amiga.txt | 36 +-- runtime/doc/os_unix.txt | 10 +- runtime/doc/os_win32.txt | 22 +- runtime/doc/pattern.txt | 10 +- runtime/doc/pi_spec.txt | 34 +-- runtime/doc/quickfix.txt | 76 +++--- runtime/doc/quotes.txt | 44 ++-- runtime/doc/remote.txt | 6 +- runtime/doc/repeat.txt | 4 +- runtime/doc/scroll.txt | 6 +- runtime/doc/spell.txt | 228 +++++++++++++----- runtime/doc/starting.txt | 14 +- runtime/doc/syntax.txt | 242 +++++++++---------- runtime/doc/tagsrch.txt | 18 +- runtime/doc/todo.txt | 190 ++++++++++----- runtime/doc/usr_01.txt | 4 +- runtime/doc/usr_04.txt | 6 +- runtime/doc/usr_07.txt | 4 +- runtime/doc/usr_11.txt | 18 +- runtime/doc/usr_20.txt | 4 +- runtime/doc/usr_23.txt | 4 +- runtime/doc/usr_28.txt | 4 +- runtime/doc/usr_30.txt | 6 +- runtime/doc/usr_40.txt | 10 +- runtime/doc/various.txt | 6 +- runtime/doc/version7.txt | 26 +- runtime/doc/vim-fr.1 | 574 +++++++++++++++++++++++++++++++++++++++++++++ runtime/doc/vim-fr.UTF-8.1 | 0 runtime/doc/windows.txt | 14 +- runtime/doc/workshop.txt | 40 ++-- runtime/doc/xxd-fr.UTF-8.1 | 395 +++++++++++++++++++++++++++++++ 36 files changed, 1720 insertions(+), 500 deletions(-) create mode 100644 runtime/doc/evim-fr.1 create mode 100644 runtime/doc/vim-fr.1 create mode 100644 runtime/doc/vim-fr.UTF-8.1 create mode 100644 runtime/doc/xxd-fr.UTF-8.1 (limited to 'runtime/doc') diff --git a/runtime/doc/arabic.txt b/runtime/doc/arabic.txt index 2d961485ae..27990e023a 100644 --- a/runtime/doc/arabic.txt +++ b/runtime/doc/arabic.txt @@ -1,4 +1,4 @@ -*arabic.txt* For Vim version 7.0aa. Last change: 2004 Jun 09 +*arabic.txt* For Vim version 7.0aa. Last change: 2005 Mar 29 VIM REFERENCE MANUAL by Nadim Shaikli @@ -24,7 +24,7 @@ Introduction ------------ Arabic is a rather demanding language in which a number of special features are required. Characters are right-to-left oriented and -ought to appear as such on the screen (ie. from right to left). +ought to appear as such on the screen (i.e. from right to left). Arabic also requires shaping of its characters, meaning the same character has a different visual form based on its relative location within a word (initial, medial, final or stand-alone). Arabic also @@ -60,7 +60,7 @@ o Changing keyboard mapping and reverse insert modes using a single o Toggling complete Arabic support via a single command. -o While in Arabic mode, numbers are entered from left to right. Upon +o While in Arabic mode, numbers are entered from left to right. Upon entering a none number character, that character will be inserted just into the left of the last number. @@ -101,14 +101,14 @@ 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 + + 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 < NOTE: the string 'your_ARABIC_FONT' is used to denote a complete - font name akin to that used in linux/unix system. - (eg. -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1) + font name akin to that used in Linux/Unix systems. + (e.g. -misc-fixed-medium-r-normal--20-200-75-75-c-100-iso10646-1) You can append the 'guifont' set command to your .vimrc file in order to get the same above noted results. In other words, @@ -179,11 +179,11 @@ o Enable Arabic settings [short-cut] If, on the other hand, you'd like to be verbose and explicit and are opting not to use the 'arabic' short-cut command, here's what - is needed (ie. if you use ':set arabic' you can skip this section) - + is needed (i.e. if you use ':set arabic' you can skip this section) - + Arabic Keymapping Activation - To activate the Arabic keymap (ie. to remap your English/Latin + To activate the Arabic keymap (i.e. to remap your English/Latin keyboard to look-n-feel like a standard Arabic one), set the 'keymap' command to "arabic". This is done by entering > @@ -197,14 +197,14 @@ o Enable Arabic settings [short-cut] default mapping (English), it is advised that users use the 'CTRL-^' key press while in insert (or add/replace) mode. The command-line will display your current mapping by displaying an "Arabic" string - next to your insertion mode (eg. -- INSERT Arabic --) indicating + next to your insertion mode (e.g. -- INSERT Arabic --) indicating your current keymap. + Arabic deletion of a combined pair character 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 (ie. it reverts to treating the combined + and still retain the LAM (i.e. it reverts to treating the combined character as its natural two characters form -- this also pertains to harakat and their combined forms). You can enable this option by entering @@ -227,7 +227,7 @@ o Enable Arabic settings [short-cut] - While in Left-to-right mode, enter ':set rl' in the command line ('rl' is the abbreviation for rightleft). - - Put the ':set rl' line in your '.vimrc' file to start the VIM in + - Put the ':set rl' line in your '.vimrc' file to start Vim in right-to-left mode permanently. + Arabic right-to-left command-line Mode @@ -295,7 +295,7 @@ Restrictions ------------ o VIM in its GUI form does not currently support Bi-directionality - (ie. the ability to see both Arabic and Latin intermixed within + (i.e. the ability to see both Arabic and Latin intermixed within the same line). @@ -304,7 +304,7 @@ Known Bugs There is one known minor bug, - 1. If you insert a haraka (eg. Fatha (U+064E)) after a LAM (U+0644) + 1. If you insert a haraka (e.g. Fatha (U+064E)) after a LAM (U+0644) and then insert an ALEF (U+0627), the appropriate combining will not happen due to the sandwiched haraka resulting in something that will NOT be displayed correctly. @@ -320,4 +320,3 @@ There is one known minor bug, No other bugs are known to exist. vim:tw=78:ts=8:ft=help:norl: - diff --git a/runtime/doc/evim-fr.1 b/runtime/doc/evim-fr.1 new file mode 100644 index 0000000000..792c1bc30a --- /dev/null +++ b/runtime/doc/evim-fr.1 @@ -0,0 +1,56 @@ +.TH EVIM 1 "16 février 2002 February 16" +.SH NAME +evim \- « Easy Vim », édite un fichier avec Vim sans utiliser les modes +.SH SYNOPSIS +.br +.B evim +[options] [fichier ...] +.br +.B eview +.SH DESCRIPTION +.B eVim +lance +.B Vim +et configure ses options afin qu'il se comporte comme un éditeur sans mode. +Cela reste Vim, mais vous pouvez l'utiliser comme un éditeur « cliquer-taper ». +Cela ressemble beaucoup à l'édition avec Notepad sur MS-Windows. +.B eVim +ne fonctionne qu'avec l'interface graphique, qui est nécessaire pour permettre +l'utilisation des menus et de la barre d'outils. +.PP +Il n'est utile qu'aux personnes qui ne parviennent vraiment pas à utiliser Vim +de façon traditionnelle. L'édition est alors bien moins efficace. +.PP +.B eview +fait la même chose, mais démarre Vim en mode Lecture-seule. +Cela revient à lancer evim \-R. +.PP +Voir vim(1) pour davantage d'informations sur Vim, les options, etc. +.PP +L'option 'insertmode' est activée pour permettre de taper directement du texte. +.br +Les mappages sont configurés pour que Copier et Coller fonctionnent avec les +raccourcis habituels de MS-Windows. CTRL-X coupe le texte, CTRL-C copie le +texte et CTRL-V colle le texte. +Vous pouvez utiliser CTRL-Q pour obtenir la fonction originale de CTRL-V. +.SH OPTIONS +Voir vim(1). +.SH FICHIERS +.TP 15 +/usr/local/lib/vim/evim.vim +Le script chargé pour initialiser eVim. +.SH AUSSI CONNU SOUS +Également connu sous le nom « Vim pour gumbies » [N.D.T. : Flying Circus...]. +Quand vous utilisez eVim, vous êtes censé prendre un mouchoir de poche, +faire un noeud à chaque coin et le porter sur votre tête. +.SH VOIR AUSSI +vim(1) +.SH AUTEUR +La majeure partie de +.B Vim +a été écrite par Bram Moolenaar, avec l'aide de nombreux autres contributeurs. +Voir le menu Aide/Remerciements ou ":help credits" dans +.B Vim. +.SH TRADUCTION +Cette page de manuel a été traduite David Blanchet. + 2005-03-26. diff --git a/runtime/doc/farsi.txt b/runtime/doc/farsi.txt index 6f32f6e83f..0e7d9bbf76 100644 --- a/runtime/doc/farsi.txt +++ b/runtime/doc/farsi.txt @@ -1,4 +1,4 @@ -*farsi.txt* For Vim version 7.0aa. Last change: 2004 Jun 16 +*farsi.txt* For Vim version 7.0aa. Last change: 2005 Mar 29 VIM REFERENCE MANUAL by Mortaza Ghassab Shiran @@ -42,7 +42,7 @@ o Changing keyboard mapping and reverse insert modes using a single o Backing from reverse insert mode to the correct place in the file (if possible). -o While in Farsi mode, numbers are entered from left to right. Upon entering +o While in Farsi mode, numbers are entered from left to right. Upon entering a none number character, that character will be inserted just into the left of the last number. @@ -54,8 +54,8 @@ o Farsi keymapping on the command line in reverse insert mode. o Toggling between left-to-right and right-to-left via F8 function key. -o Toggling between Farsi ISIR-3342 standard encoding and VIM Farsi via F9 - function key. Since this makes sense only for the text written in +o Toggling between Farsi ISIR-3342 standard encoding and Vim Farsi via F9 + function key. Since this makes sense only for the text written in right-to-left mode, this function is also supported only in right-to-left mode. @@ -77,8 +77,8 @@ Font Installation o Installation of fonts for MS Window systems (NT/95/98) - From 'Control Panel' folder, start the 'Fonts' program. Then from 'file' - menu item select 'Install New Fonts ...'. Browse and select the + From 'Control Panel' folder, start the 'Fonts' program. Then from 'file' + menu item select 'Install New Fonts ...'. Browse and select the 'far-a01.fon', then follow the installation guide. NOTE: several people have reported that this does not work. The solution is unknown. @@ -104,19 +104,19 @@ o Installation of fonts for X Window systems (SunOS) o Installation of ASCII screen fonts (Unix/Linux) For Linux system, copy the far-a01.f16 fonts into /usr/lib/kbd/consolefonts - directory and execute the setfont program as "setfont far-a01.f16". For + directory and execute the setfont program as "setfont far-a01.f16". For other systems (e.g. SCO Unix), please refer to the fonts installation section of your system administration manuals. o Installation of ASCII screen fonts (DOS) - After system power on, prior to the first use of VIM, upload the Farsi + After system power on, prior to the first use of Vim, upload the Farsi fonts by executing the far-a01.com font uploading program. Usage ----- -Prior to starting VIM, the environment in which VIM can run in Farsi mode, +Prior to starting Vim, the environment in which Vim can run in Farsi mode, must be set. In addition to installation of Farsi fonts, following points refer to some of the system environments, which you may need to set: Key code mapping, loading graphic card in ASCII screen mode, setting the IO @@ -124,26 +124,26 @@ driver in 8 bit clean mode ... . o Setting the Farsi fonts - + For VIM GUI set the 'guifont' to far-a01. This is done by entering - ':set guifont=far-a01' in the VIM window. + + For Vim GUI set the 'guifont' to far-a01. This is done by entering + ':set guifont=far-a01' in the Vim window. - You can have 'guifont' set to far-a01 by VIM during the VIM startup + You can have 'guifont' set to far-a01 by Vim during the Vim startup by appending the ':set guifont=far-a01' into your .vimrc file (in case of NT/95/98 platforms _vimrc). - Under the X Window environment, you can also start the VIM with + Under the X Window environment, you can also start Vim with the '-fn far-a01' option. - + For the VIM within a xterm, start a xterm with the Farsi fonts (e.g. - kterm -fn far-a01). Then start the VIM inside the kterm. + + For Vim within a xterm, start a xterm with the Farsi fonts (e.g. + kterm -fn far-a01). Then start Vim inside the kterm. - + For VIM under DOS, prior to the first usage of VIM, upload the Farsi + + For Vim under DOS, prior to the first usage of Vim, upload the Farsi fonts by executing the far-a01.com fonts uploading program. o Farsi Keymapping Activation To activate the Farsi keymapping, set either 'altkeymap' or 'fkmap'. - This is done by entering ':set akm' or ':set fk' in the VIM window. + This is done by entering ':set akm' or ':set fk' in the Vim window. You can have 'altkeymap' or 'fkmap' set as default by appending ':set akm' or ':set fk' in your .vimrc file or _vimrc in case of NT/95/98 platforms. @@ -152,24 +152,24 @@ o Farsi Keymapping Activation o right-to-left Farsi Mode - By default VIM starts in Left-to-right mode. Following are ways to change + By default Vim starts in Left-to-right mode. Following are ways to change the window orientation: - + Start the VIM with -F option (e.g. vim -F ... ). + + Start Vim with the -F option (e.g. vim -F ...). - + Use F8 function key to toggle between left-to-right and right-to-left. + + Use the F8 function key to toggle between left-to-right and right-to-left. + While in Left-to-right mode, enter 'set rl' in the command line ('rl' is the abbreviation for rightleft). - + Put the 'set rl' line in your '.vimrc' file to start the VIM in + + Put the 'set rl' line in your '.vimrc' file to start Vim in right-to-left mode permanently. Encoding -------- -The letter encoding used is the VIM extended ISIR-3342 standard with a built -in function to convert between VIM extended ISIR-3342 and ISIR-3342 standard. +The letter encoding used is the Vim extended ISIR-3342 standard with a built +in function to convert between Vim extended ISIR-3342 and ISIR-3342 standard. For document portability reasons, the letter encoding is kept the same across different platforms (i.e. UNIX's, NT/95/98, MS DOS, ...). @@ -183,11 +183,11 @@ o Keyboard + CTRL-_ moves the cursor to the end of the typed text in edit mode. + CTRL-_ in command mode only toggles keyboard mapping between Farsi(akm)/ - Latin. The Farsi text is then entered in reverse insert mode. + Latin. The Farsi text is then entered in reverse insert mode. + F8 - Toggles between left-to-right and right-to-left. - + F9 - Toggles the encoding between ISIR-3342 standard and VIM extended + + F9 - Toggles the encoding between ISIR-3342 standard and Vim extended ISIR-3342 (supported only in right-to-left mode). + Keyboard mapping is based on the Iranian ISIRI-2901 standard. @@ -231,28 +231,28 @@ o In insert/replace mode and fkmap (Farsi mode) set, CTRL-B is not supported. o If you change the character mapping between Latin/Farsi, the redo buffer - will be reset (emptied). That is, redo is valid and will function (using + will be reset (emptied). That is, redo is valid and will function (using '.') only within the mode you are in. o While numbers are entered in Farsi mode, the redo buffer will be reset - (emptied). That is, you can not redo the last changes (using '.') after + (emptied). That is, you cannot redo the last changes (using '.') after entering numbers. -o While in left-to-right and Farsi mode set, CTRL-R is not supported. +o While in left-to-right mode and Farsi mode set, CTRL-R is not supported. o While in right-to-left mode, the search on 'Latin' pattern does not work, except if you enter the Latin search pattern in reverse. -o In the command mode, there is no support for entering the numbers from left - to right and also for the sake of the flexibility the keymapping logic is +o In command mode there is no support for entering numbers from left + to right and also for the sake of flexibility the keymapping logic is restricted. -o Under X Window environment, if you want to run the VIM within a xterm +o Under the X Window environment, if you want to run Vim within a xterm terminal emulator and Farsi mode set, you need to have an ANSI compatible - xterm terminal emulator. This is because the letter codes above 128 decimal + xterm terminal emulator. This is because the letter codes above 128 decimal have certain meanings in the standard xterm terminal emulator. - Note: Under X Window environment, VIM GUI works fine in Farsi mode. + Note: Under X Window environment, Vim GUI works fine in Farsi mode. This eliminates the need of any xterm terminal emulator. @@ -261,7 +261,7 @@ Bugs While in insert/replace and Farsi mode set, if you repeatedly change the cursor position (via cursor movement) and enter new text and then try to undo the last change, the undo will lag one change behind. But as you continue to -undo, you will reach the original line of text. You can also use U to undo all +undo, you will reach the original line of text. You can also use U to undo all changes made in the current line. For more information about the bugs refer to rileft.txt. diff --git a/runtime/doc/filetype.txt b/runtime/doc/filetype.txt index a4cc593a2a..8b7d6ac4a1 100644 --- a/runtime/doc/filetype.txt +++ b/runtime/doc/filetype.txt @@ -1,4 +1,4 @@ -*filetype.txt* For Vim version 7.0aa. Last change: 2004 Aug 31 +*filetype.txt* For Vim version 7.0aa. Last change: 2005 Mar 29 VIM REFERENCE MANUAL by Bram Moolenaar @@ -382,7 +382,7 @@ ways to change this: CHANGELOG *changelog-plugin* -Allows for easy entrance of Changelog entries in Changelog files. There are +Allows for easy entrance of Changelog entries in Changelog files. There are some commands, mappings, and variables worth exploring: Options: @@ -462,7 +462,7 @@ g:changelog_date_entry_search The Changelog entries are inserted where they add the least amount of text. After figuring out the current date and user, the file is searched for an entry beginning with the current date and user and if found adds another item -under it. If not found, a new entry and item is prepended to the beginning of +under it. If not found, a new entry and item is prepended to the beginning of the Changelog. @@ -474,7 +474,7 @@ Options: 'textwidth' is set to 72 for fixed source format as required by the Fortran standards and to 80 for free source format. 'formatoptions' is set to break code and comment lines and to preserve long - lines. You can format comments with |gq|. + lines. You can format comments with |gq|. For further discussion of fortran_have_tabs and the method used for the detection of source format see |fortran-syntax|. diff --git a/runtime/doc/intro.txt b/runtime/doc/intro.txt index 935577724c..ee187c974c 100644 --- a/runtime/doc/intro.txt +++ b/runtime/doc/intro.txt @@ -1,4 +1,4 @@ -*intro.txt* For Vim version 7.0aa. Last change: 2005 Feb 07 +*intro.txt* For Vim version 7.0aa. Last change: 2005 Mar 29 VIM REFERENCE MANUAL by Bram Moolenaar @@ -330,11 +330,11 @@ and <> are part of what you type, the context should make this clear. ["x] An optional register designation where text can be stored. See |registers|. The x is a single character between 'a' and 'z' or 'A' and 'Z' or '"', and in some cases (with the put - command) between '0' and '9', '%', '#', or others. The + command) between '0' and '9', '%', '#', or others. The uppercase and lowercase letter designate the same register, but the lowercase letter is used to overwrite the previous register contents, while the uppercase letter is used to - append to the previous register contents. Without the ""x" or + append to the previous register contents. Without the ""x" or with """" the stored text is put into the unnamed register. *{}* diff --git a/runtime/doc/os_amiga.txt b/runtime/doc/os_amiga.txt index 069e76964e..0e42c5d82d 100644 --- a/runtime/doc/os_amiga.txt +++ b/runtime/doc/os_amiga.txt @@ -1,4 +1,4 @@ -*os_amiga.txt* For Vim version 7.0aa. Last change: 2004 Jun 28 +*os_amiga.txt* For Vim version 7.0aa. Last change: 2005 Mar 29 VIM REFERENCE MANUAL by Bram Moolenaar @@ -13,7 +13,7 @@ Installation on the Amiga: look for the file "VIM:doc/help.txt" (for the help command). Setting the environment variable $VIM also works. And the other way around: when $VIM used and it is not defined, "VIM:" is used. -- With DOS 1.3 or earlier: Put "arp.library" in "libs:". Vim must have been +- With DOS 1.3 or earlier: Put "arp.library" in "libs:". Vim must have been compiled with the |+ARP| feature enabled. Make sure that newcli and run are in "C:" (for executing external commands). - Put a shell that accepts a command with "-c" (e.g. "Csh" from Fish disk @@ -21,13 +21,13 @@ Installation on the Amiga: executing external commands). If you have sufficient memory you can avoid startup delays by making Vim and -csh resident with the command "rez csh vim". You will have to put -"rezlib.library" in your "libs:" directory. Under 2.0 you will need rez +csh resident with the command "rez csh vim". You will have to put +"rezlib.library" in your "libs:" directory. Under 2.0 you will need rez version 0.5. If you do not use digraphs, you can save some memory by recompiling without -the |+digraphs| feature. If you want to use Vim with other terminals you can -recompile with the TERMCAP option. Vim compiles with Manx 5.x and SAS 6.x. +the |+digraphs| feature. If you want to use Vim with other terminals you can +recompile with the TERMCAP option. Vim compiles with Manx 5.x and SAS 6.x. See the makefiles and feature.h. If you notice Vim crashes on some files when syntax highlighting is on, or @@ -47,7 +47,7 @@ If you want to use different colors set the termcap codes: t_ZH (for italic text) t_ZR (for normal text after t_ZH) -Standard ANSI escape sequences are used. The codes are: +Standard ANSI escape sequences are used. The codes are: 30 grey char 40 grey cell >0 grey background 0 all attributes off 31 black char 41 black cell >1 black background 1 boldface 32 white char 42 white cell >2 white background 2 faint @@ -57,8 +57,8 @@ Standard ANSI escape sequences are used. The codes are: 36 white char 46 white cell >6 white background 8 invisible 37 blue char 47 blue cell >7 blue background -The codes with '>' must be the last. The cell and background color should be -the same. The codes can be combined by separating them with a semicolon. For +The codes with '>' must be the last. The cell and background color should be +the same. The codes can be combined by separating them with a semicolon. For example to get white text on a blue background: > :set t_me=^V[0;32;43;>3m :set t_se=^V[0;32;43;>3m @@ -72,14 +72,14 @@ example to get white text on a blue background: > When using multiple commands with a filter command, e.g. > :r! echo this; echo that -Only the output of the last command is used. To fix this you have to group the -commands. This depends on the shell you use (that is why it is not done -automatically in Vim). Examples: > +Only the output of the last command is used. To fix this you have to group the +commands. This depends on the shell you use (that is why it is not done +automatically in Vim). Examples: > :r! (echo this; echo that) :r! {echo this; echo that} Commands that accept a single file name allow for embedded spaces in the file -name. However, when using commands that accept several file names, embedded +name. However, when using commands that accept several file names, embedded spaces need to be escaped with a backslash. ------------------------------------------------------------------------------ @@ -94,8 +94,8 @@ For the latest info about the MorphOS version: Problems ~ There are a couple of problems which are not MorphOS related but more Vim and -UN*X related. When starting up Vim in ram: it complains with a nag requester -from MorphOS please simply ignore it. Another problem is when running Vim as +UN*X related. When starting up Vim in ram: it complains with a nag requester +from MorphOS please simply ignore it. Another problem is when running Vim as is some plugins will cause a few problems which you can ignore as well. Hopefully someone will be fixing it over the time. @@ -116,7 +116,7 @@ Installation ~ ftp://ftp.vim.org/pub/vim/amiga/vim62rt.tgz - and unpack it in your 'Apps' directory of the MorphOS installation. For me + and unpack it in your 'Apps' directory of the MorphOS installation. For me this would create following directory hierarchy: MorphOS:Apps/Vim/Vim62/... @@ -130,8 +130,8 @@ Installation ~ 4) Copy the '.vimrc' file to s: -5) There is also a file named 'color-sequence' included in this archive. This - will set the MorphOS Shell to show ANSI colors. Please copy the file to s: +5) There is also a file named 'color-sequence' included in this archive. This + will set the MorphOS Shell to show ANSI colors. Please copy the file to s: and change the s:shell-startup to: ;Begin VIM diff --git a/runtime/doc/os_unix.txt b/runtime/doc/os_unix.txt index 965b18d996..0a69e70c63 100644 --- a/runtime/doc/os_unix.txt +++ b/runtime/doc/os_unix.txt @@ -1,4 +1,4 @@ -*os_unix.txt* For Vim version 7.0aa. Last change: 2005 Mar 25 +*os_unix.txt* For Vim version 7.0aa. Last change: 2005 Mar 29 VIM REFERENCE MANUAL by Bram Moolenaar @@ -11,7 +11,7 @@ For compiling Vim on Unix see "INSTALL" and "Makefile" in the src directory. The default help file name is "/usr/local/lib/vim/help.txt" The files "$HOME/.vimrc" and "$HOME/.exrc" are used instead of "s:.vimrc" and -"s:.exrc". Additionally "/usr/local/etc/vimrc" is used first. +"s:.exrc". Additionally "/usr/local/etc/vimrc" is used first. If "/usr/local/share" exists it is used instead of "/usr/local/lib". Temporary files (for filtering) are put in "/tmp". If you want to place them @@ -26,15 +26,15 @@ For executing external commands fork()/exec() is used when possible, otherwise system() is used, which is a bit slower. The output of ":version" includes |+fork| when fork()/exec() is used, |+system()| when system() is used. This can be changed at compile time. -(For forking of the GUI version see |gui-fork|). +(For forking of the GUI version see |gui-fork|.) Because terminal updating under Unix is often slow (e.g. serial line terminal, shell window in suntools), the 'showcmd' and 'ruler' options -are default off. If you have a fast terminal, try setting them on. You might +are default off. If you have a fast terminal, try setting them on. You might also want to set 'ttyfast'. When using Vim in an xterm the mouse clicks can be used by Vim by setting -'mouse' to "a". If there is access to an X-server gui style copy/paste will +'mouse' to "a". If there is access to an X-server gui style copy/paste will be used and visual feedback will be provided while dragging with the mouse. If you then still want the xterm copy/paste with the mouse, press the shift key when using the mouse. See |mouse-using|. Visual feedback while dragging diff --git a/runtime/doc/os_win32.txt b/runtime/doc/os_win32.txt index 6f9a541c2e..880981d74e 100644 --- a/runtime/doc/os_win32.txt +++ b/runtime/doc/os_win32.txt @@ -1,4 +1,4 @@ -*os_win32.txt* For Vim version 7.0aa. Last change: 2004 Aug 31 +*os_win32.txt* For Vim version 7.0aa. Last change: 2005 Mar 29 VIM REFERENCE MANUAL by George Reilly @@ -192,7 +192,7 @@ A. In the GUI version, you can use the 'guifont' option. Example: > Q. When I change the size of the console window with ':set lines=xx' or similar, the font changes! (Win95) A. You have the console font set to 'Auto' in Vim's (or your MS-DOS prompt's) - properties. This makes W95 guess (badly!) what font is best. Set an explicit + properties. This makes W95 guess (badly!) what font is best. Set an explicit font instead. Q. Why can't I paste into Vim when running Windows 95? @@ -282,7 +282,7 @@ A. VisionFS can't handle certain dot (.) three letter extension file names. dir > file.bat < The result is that the "dir" command updates the "file.bat~" file, instead - of creating a new "file.bat" file. This same behavior is exhibited in Vim + of creating a new "file.bat" file. This same behavior is exhibited in Vim when editing an existing file named "foo.bat" because the default behavior of Vim is to create a temporary file with a '~' character appended to the name. When the file is written, it winds up being deleted. @@ -306,13 +306,13 @@ A. When using :! to run an external command, you can run it with "start": > To avoid this special treatment, use ":! start". Q. I'm using Win32s, and when I try to run an external command like "make", - Vim doesn't wait for it to finish! Help! + Vim doesn't wait for it to finish! Help! A. The problem is that a 32-bit application (Vim) can't get notification from - Windows that a 16-bit application (your DOS session) has finished. Vim + Windows that a 16-bit application (your DOS session) has finished. Vim includes a work-around for this, but you must set up your DOS commands to - run in a window, not full-screen. Unfortunately the default when you - install Windows is full-screen. To change this: - 1) Start PIF editor (in the Main program group) + run in a window, not full-screen. Unfortunately the default when you + install Windows is full-screen. To change this: + 1) Start PIF editor (in the Main program group). 2) Open the file "_DEFAULT.PIF" in your Windows directory. 3) Changes the display option from "Full Screen" to "Windowed". 4) Save and exit. @@ -321,10 +321,10 @@ A. The problem is that a 32-bit application (Vim) can't get notification from :!dir C:\". < You should see a DOS box window appear briefly with the directory listing. -Q. I use Vim under Win32s and NT. In NT, I can define the console to default to - 50 lines, so that I get a 80x50 shell when I ':sh'. Can I do the same in +Q. I use Vim under Win32s and NT. In NT, I can define the console to default to + 50 lines, so that I get a 80x50 shell when I ':sh'. Can I do the same in W3.1x, or am I stuck with 80x25? -A. Edit SYSTEM.INI and add 'ScreenLines=50' to the [NonWindowsApp] section. DOS +A. Edit SYSTEM.INI and add 'ScreenLines=50' to the [NonWindowsApp] section. DOS prompts and external DOS commands will now run in a 50-line window. vim:tw=78:fo=tcq2:ts=8:ft=help:norl: diff --git a/runtime/doc/pattern.txt b/runtime/doc/pattern.txt index d5a6e2983b..ba35a04706 100644 --- a/runtime/doc/pattern.txt +++ b/runtime/doc/pattern.txt @@ -1,4 +1,4 @@ -*pattern.txt* For Vim version 7.0aa. Last change: 2005 Mar 07 +*pattern.txt* For Vim version 7.0aa. Last change: 2005 Mar 29 VIM REFERENCE MANUAL by Bram Moolenaar @@ -631,7 +631,7 @@ overview. position: "\(foo\)\@!bar" will match "bar" in "foobar", because at the position where "bar" matches, "foo" does not match. To avoid matching "foobar" you could use "\(foo\)\@!...bar", but that doesn't match a - bar at the start of a line. Use "\(foo\)\@* \> Matches the end of a word: The previous char is the last char of a - word. The 'iskeyword' option specifies what is a word character. + word. The 'iskeyword' option specifies what is a word character. |/zero-width| */\zs* @@ -745,7 +745,7 @@ $ At end of pattern or in front of "\|" or "\)" ("|" or ")" after "\v"): /^\s*\zsif < matches an "if" at the start of a line, ignoring white space. Can be used multiple times, the last one encountered in a matching - branch is used. Example: > + branch is used. Example: > /\(.\{-}\zsFab\)\{3} < Finds the third occurrence of "Fab". {not in Vi} {not available when compiled without the +syntax feature} @@ -930,7 +930,7 @@ x A single character, with no special meaning, matches itself [] (with 'nomagic': \[]) */[]* */\[]* */\_[]* */collection* \_[] - A collection. This is a sequence of characters enclosed in brackets. + A collection. This is a sequence of characters enclosed in brackets. It matches any single character in the collection. Example matches ~ [xyz] any 'x', 'y' or 'z' diff --git a/runtime/doc/pi_spec.txt b/runtime/doc/pi_spec.txt index a52984a582..d3b03d80fe 100644 --- a/runtime/doc/pi_spec.txt +++ b/runtime/doc/pi_spec.txt @@ -1,13 +1,13 @@ -*pi_spec.txt* For Vim version 7.0aa. Last change: 2002 Oct 29 +*pi_spec.txt* For Vim version 7.0aa. Last change: 2005 Apr 01 by Gustavo Niemeyer ~ This is a filetype plugin to work with rpm spec files. Currently, this Vim plugin allows you to easily update the %changelog -section in RPM spec files. It will even create a section for you if it -doesn't exist yet. If you've already inserted an entry today, it will -give you the opportunity to just add a new item in today's entry. If you +section in RPM spec files. It will even create a section for you if it +doesn't exist yet. If you've already inserted an entry today, it will +give you the opportunity to just add a new item in today's entry. If you don't provide a format string (|spec_chglog_format|), it'll ask you an email address and build a format string by itself. @@ -22,24 +22,24 @@ The spec_chglog plugin provides a map like the following: :map c SpecChangelog It means that you may run the plugin inside a spec file by pressing -your maplocalleader key (default is '\') plus 'c'. If you do not have +your maplocalleader key (default is '\') plus 'c'. If you do not have |spec_chglog_format| set, the plugin will ask you for an email address to use in this edit session. Everytime you run the plugin, it will check to see if the last entry -in the changelog has been written today and by you. If it's the entry +in the changelog has been written today and by you. If it's the entry mathes, it will just insert a new changelog item, otherwise it will -create a new changelog entry. If you are running with +create a new changelog entry. If you are running with |spec_chglog_release_info| enabled, it will also check if the name, version -and release matches. The plugin is smart enough to ask you if it should +and release matches. The plugin is smart enough to ask you if it should update the package release, if you have not done so. Setting a map *spec-setting-a-map* ------------- As you should know, you can easily set a map to access any Vim command (or -anything, for that matter). If you don't like the default map of -c, you may just set up your own key. The following line +anything, for that matter). If you don't like the default map of +c, you may just set up your own key. The following line shows you how you could do this in your .vimrc file, mapping the plugin to the key: @@ -57,16 +57,16 @@ This command will add a map only in the spec file buffers. The format string *spec_chglog_format* ----------------- -You can easily customize how your spec file entry will look like. To do +You can easily customize how your spec file entry will look like. To do this just set the variable "spec_chglog_format" in your .vimrc file like this: > let spec_chglog_format = "%a %b %d %Y My Name " -Note that "%a %b %d %Y" is the most used time format. If you don't provide +Note that "%a %b %d %Y" is the most used time format. If you don't provide a format string, when you run the SpecChangelog command for the first time, it will ask you an email address and build the |spec_chglog_format| -variable for you. This way, you will only need to provide your email +variable for you. This way, you will only need to provide your email address once. To discover which format options you can use, take a look at the strftime() @@ -76,7 +76,7 @@ Where to insert new items *spec_chglog_prepend* ------------------------- The plugin will usually insert new %changelog entry items (note that it's -not the entry itself) after the existing ones. If you set the +not the entry itself) after the existing ones. If you set the spec_chglog_prepend variable > let spec_chglog_prepend = 1 @@ -87,11 +87,11 @@ Inserting release info *spec_chglog_release_info* ---------------------- If you want, the plugin may automatically insert release information -on each changelog entry. One advantage of turning this feature on is +on each changelog entry. One advantage of turning this feature on is that it may control if the release has been updated after the last -change in the package or not. If you have not updated the package +change in the package or not. If you have not updated the package version or release, it will ask you if it should update the package -release for you. To turn this feature on, just insert the following +release for you. To turn this feature on, just insert the following code in your .vimrc: > let spec_chglog_release_info = 1 diff --git a/runtime/doc/quickfix.txt b/runtime/doc/quickfix.txt index d40d7e7728..d558440a05 100644 --- a/runtime/doc/quickfix.txt +++ b/runtime/doc/quickfix.txt @@ -1,4 +1,4 @@ -*quickfix.txt* For Vim version 7.0aa. Last change: 2005 Mar 25 +*quickfix.txt* For Vim version 7.0aa. Last change: 2005 Apr 01 VIM REFERENCE MANUAL by Bram Moolenaar @@ -122,7 +122,7 @@ The following quickfix commands can be used: :cl[ist] [from] [, [to]] List all errors that are valid |quickfix-valid|. If numbers [from] and/or [to] are given, the respective - range of errors is listed. A negative number counts + range of errors is listed. A negative number counts from the last error backwards, -1 being the last error. The 'switchbuf' settings are respected when jumping to a buffer. @@ -380,16 +380,16 @@ id-utils) in a similar way to its compiler integration (see |:make| above). 5.3 Setting up external grep If you have a standard "grep" program installed, the :grep command may work -well with the defaults. The syntax is very similar to the standard command: > +well with the defaults. The syntax is very similar to the standard command: > :grep foo *.c -Will search all files with the .c extension for the substring "foo". The +Will search all files with the .c extension for the substring "foo". The arguments to :grep are passed straight to the "grep" program, so you can use whatever options your "grep" supports. By default, :grep invokes grep with the -n option (show file and line -numbers). You can change this with the 'grepprg' option. You will need to set +numbers). You can change this with the 'grepprg' option. You will need to set 'grepprg' if: a) You are using a program that isn't called "grep" @@ -515,8 +515,8 @@ stdin (standard input) will not be interactive. PYUNIT COMPILER *compiler-pyunit* This is not actually a compiler, but a unit testing framework for the -Python language. It is included into standard Python distribution -starting from version 2.0. For older versions, you can get it from +Python language. It is included into standard Python distribution +starting from version 2.0. For older versions, you can get it from http://pyunit.sourceforge.net. When you run your tests with the help of the framework, possible errors @@ -534,20 +534,20 @@ Also see http://vim.sourceforge.net/tip_view.php?tip_id=280. TEX COMPILER *compiler-tex* Included in the distribution compiler for TeX ($VIMRUNTIME/compiler/tex.vim) -uses make command if possible. If the compiler finds a file named "Makefile" +uses make command if possible. If the compiler finds a file named "Makefile" or "makefile" in the current directory, it supposes that you want to process -your *TeX files with make, and the makefile does the right work. In this case -compiler sets 'errorformat' for *TeX output and leaves 'makeprg' untouched. If +your *TeX files with make, and the makefile does the right work. In this case +compiler sets 'errorformat' for *TeX output and leaves 'makeprg' untouched. If neither "Makefile" nor "makefile" is found, the compiler will not use make. You can force the compiler to ignore makefiles by defining b:tex_ignore_makefile or g:tex_ignore_makefile variable (they are checked for existence only). If the compiler chose not to use make, it need to choose a right program for -processing your input. If b:tex_flavor or g:tex_flavor (in this precedence) +processing your input. If b:tex_flavor or g:tex_flavor (in this precedence) variable exists, it defines TeX flavor for :make (actually, this is the name of executed command), and if both variables do not exist, it defaults to -"latex". For example, while editing chapter2.tex \input-ed from mypaper.tex +"latex". For example, while editing chapter2.tex \input-ed from mypaper.tex written in AMS-TeX: > :let b:tex_flavor = 'amstex' @@ -557,16 +557,16 @@ written in AMS-TeX: > Note that you must specify a name of the file to process as an argument (to process the right file when editing \input-ed or \include-ed file; portable -solution for substituting % for no arguments is welcome). This is not in the +solution for substituting % for no arguments is welcome). This is not in the semantics of make, where you specify a target, not source, but you may specify filename without extension ".tex" and mean this as "make filename.dvi or filename.pdf or filename.some_result_extension according to compiler". Note: tex command line syntax is set to usable both for MikTeX (suggestion -by Srinath Avadhanula) and teTeX (checked by Artem Chuprina). Suggestion +by Srinath Avadhanula) and teTeX (checked by Artem Chuprina). Suggestion from |errorformat-LaTeX| is too complex to keep it working for different shells and OSes and also does not allow to use other available TeX options, -if any. If your TeX doesn't support "-interaction=nonstopmode", please +if any. If your TeX doesn't support "-interaction=nonstopmode", please report it with different means to express \nonstopmode from the command line. ============================================================================= @@ -600,7 +600,7 @@ Basic items column of the error, (1 == 1 character column)) %v virtual column number (finds a number representing screen column of the error (1 == 8 screen - columns) + columns)) %t error type (finds a single character) %n error number (finds a number) %m error message (finds a string) @@ -646,7 +646,7 @@ The following uppercase conversion characters specify the type of special format strings. At most one of them may be given as a prefix at the begin of a single comma-separated format pattern. Some compilers produce messages that consist of directory names that have to -be prepended to each file name read by %f (example: GNU make). The following +be prepended to each file name read by %f (example: GNU make). The following codes can be used to scan these directory names; they will be stored in an internal directory stack. *E379* %D "enter directory" format string; expects a following @@ -654,7 +654,7 @@ internal directory stack. *E379* %X "leave directory" format string; expects following %f When defining an "enter directory" or "leave directory" format, the "%D" or -"%X" has to be given at the start of that substring. Vim tracks the directory +"%X" has to be given at the start of that substring. Vim tracks the directory changes and prepends the current directory to each erroneous file found with a relative path. See |quickfix-directory-stack| for details, tips and limitations. @@ -663,7 +663,7 @@ limitations. Multi-line messages *errorformat-multi-line* It is possible to read the output of programs that produce multi-line -messages, ie. error strings that consume more than one line. Possible +messages, i.e. error strings that consume more than one line. Possible prefixes are: %E start of a multi-line error message %W start of a multi-line warning message @@ -756,7 +756,7 @@ A call of |:clist| writes them accordingly with their correct filenames: 9 a3.tt:67 col 3 warning: 's' already defined Unlike the other prefixes that all match against whole lines, %P, %Q and %O -can be used to match several patterns in the same line. Thus it is possible +can be used to match several patterns in the same line. Thus it is possible to parse even nested files like in the following line: {"file1" {"file2" error1} error2 {"file3" error3 {"file4" error4 error5}}} The %O then parses over strings that do not contain any push/pop file name @@ -766,11 +766,11 @@ information. See |errorformat-LaTeX| for an extended example. Ignoring and using whole messages *efm-ignore* The codes '+' or '-' can be combined with the uppercase codes above; in that -case they have to precede the letter, eg. '%+A' or '%-G': +case they have to precede the letter, e.g. '%+A' or '%-G': %- do not include the matching multi-line in any output %+ include the whole matching line in the %m error string -One prefix is only useful in combination with '+' or '-', namely %G. It parses +One prefix is only useful in combination with '+' or '-', namely %G. It parses over lines containing general information like compiler version strings or other headers that can be skipped. %-G ignore this message @@ -785,7 +785,7 @@ with previous versions of Vim. However, it is also possible to specify Since meta characters of the regular expression language can be part of ordinary matching strings or file names (and therefore internally have to be escaped), meta symbols have to be written with leading '%': - %\ the single '\' character. Note that this has to be + %\ the single '\' character. Note that this has to be escaped ("%\\") in ":set errorformat=" definitions. %. the single '.' character. %# the single '*'(!) character. @@ -795,7 +795,7 @@ be escaped), meta symbols have to be written with leading '%': %~ the single '~' character. When using character classes in expressions (see |/\i| for an overview), terms containing the "\+" quantifier can be written in the scanf() "%*" -notation. Example: "%\\d%\\+" ("\d\+", "any number") is equivalent to "%*\\d". +notation. Example: "%\\d%\\+" ("\d\+", "any number") is equivalent to "%*\\d". Important note: The \(...\) grouping of sub-matches can not be used in format specifications because it is reserved for internal conversions. @@ -881,19 +881,19 @@ required for the set command. 8. The directory stack *quickfix-directory-stack* Quickfix maintains a stack for saving all used directories parsed from the -make output. For GNU-make this is rather simple, as it always prints the -absolute path of all directories it enters and leaves. Regardless if this is +make output. For GNU-make this is rather simple, as it always prints the +absolute path of all directories it enters and leaves. Regardless if this is done via a 'cd' command in the makefile or with the parameter "-C dir" (change -to directory before reading the makefile). It may be useful to use the switch +to directory before reading the makefile). It may be useful to use the switch "-w" to force GNU-make to print out the working directory before and after processing. Maintaining the correct directory is more complicated if you don't use -GNU-make. AIX-make for example doesn't print any information about its working -directory. Then you need to enhance the makefile. In the makefile of LessTif -there is a command which echoes "Making {target} in {dir}". The special -problem here is that it doesn't print informations on leaving the directory -and that it doesn't print the absolute path. +GNU-make. AIX-make for example doesn't print any information about its +working directory. Then you need to enhance the makefile. In the makefile of +LessTif there is a command which echoes "Making {target} in {dir}". The +special problem here is that it doesn't print informations on leaving the +directory and that it doesn't print the absolute path. To solve the problem with relative paths and missing "leave directory" messages Vim uses following algorithm: @@ -907,10 +907,10 @@ messages Vim uses following algorithm: Additionally it is checked for every file, if it really exists in the identified directory. If not, it is searched in all other directories of the -directory stack (NOT the directory subtree!). If it is still not found, it is +directory stack (NOT the directory subtree!). If it is still not found, it is assumed that it is in Vim's current directory. -There are limitation in this algorithm. This examples assume that make just +There are limitation in this algorithm. This examples assume that make just prints information about entering a directory in the form "Making all in dir". 1) Assume you have following directories and files: @@ -957,7 +957,7 @@ Add to your 'errorformat' to handle the above output. Note that Vim doesn't check if the directory name in a "leave directory" -messages is the current directory. This is why you could just use the message +messages is the current directory. This is why you could just use the message "Leaving dir". ============================================================================= @@ -1019,7 +1019,7 @@ It should be easy to adopt the above LaTeX errorformat to any compiler output consisting of multi-line errors. The commands can be placed in a |vimrc| file or some other Vim script file, -eg. a script containing LaTeX related stuff which is loaded only when editing +e.g. a script containing LaTeX related stuff which is loaded only when editing LaTeX sources. Make sure to copy all lines of the example (in the given order), afterwards remove the comment lines. For the '\' notation at the start of some lines see @@ -1033,7 +1033,7 @@ remove the comment lines. For the '\' notation at the start of some lines see :set efm=%E!\ LaTeX\ %trror:\ %m, \%E!\ %m, < Start of multi-line warning messages; the first two also - include the line number. Meaning of some regular expressions: + include the line number. Meaning of some regular expressions: - "%.%#" (".*") matches a (possibly empty) string - "%*\\d" ("\d\+") matches a number > \%+WLaTeX\ %.%#Warning:\ %.%#line\ %l%.%#, @@ -1072,7 +1072,7 @@ remove the comment lines. For the '\' notation at the start of some lines see on a stack since the file apparently does not contain any error: > \%+O(%f)%r, -< Push a file name onto the stack. The name is given after '(': > +< Push a file name onto the stack. The name is given after '(': > \%+P(%f%r, \%+P\ %\\=(%f%r, \%+P%*[^()](%f%r, diff --git a/runtime/doc/quotes.txt b/runtime/doc/quotes.txt index 3c5c3a3e69..9cc94ff768 100644 --- a/runtime/doc/quotes.txt +++ b/runtime/doc/quotes.txt @@ -1,4 +1,4 @@ -*quotes.txt* For Vim version 7.0aa. Last change: 2004 May 06 +*quotes.txt* For Vim version 7.0aa. Last change: 2005 Apr 04 VIM REFERENCE MANUAL by Bram Moolenaar @@ -18,7 +18,7 @@ Coming with a very GUI mindset from Windows, I always thought of people using Vi as some kind of outer space alien in human clothes. Once I tried I really got addicted by its power and now I found myself typing Vim keypresses in the oddest places! That's why I would like to see Vim embedded in every -application which deals with text editing. (José Fonseca) +application which deals with text editing. (José Fonseca) I was a 12-year emacs user who switched to Vim about a year ago after finally giving up on the multiple incompatible versions, flaky contributed packages, @@ -32,17 +32,17 @@ the Vi editor") Out of all the open software i've ever seen and used, and i've seen a lot, Vim is the best, most useful and highest quality to work with, second only to the -linux kernel itself. (Peter Jay Salzman) +linux kernel itself. (Peter Jay Salzman) It's well worth noting that the _entirety_ of SourceForge was written using -Vim and its nifty PHP syntax highlighting. I think the entire SF.net tech +Vim and its nifty PHP syntax highlighting. I think the entire SF.net tech staff uses Vim and we're all excited to have you aboard! (Tim Perdue) Vim is one of a select bunch of tools for which I have no substitute. It is a brilliant piece of work! (Biju Chacko) A previous girlfriend of mine switched to emacs. Needless to say, the -relationship went nowhere. (Geoffrey Mann) +relationship went nowhere. (Geoffrey Mann) I rarely think about Vim, in the same way that I guess a fish rarely thinks about water. It's the environment in which everything else happens. I'm a @@ -51,7 +51,7 @@ is the only thing that's consistent across all my systems, and it's just about the only thing that doesn't break from time to time. When a new system comes in the door without Vim, I install it right away. Great to have a tool that's the same everywhere, that's completely reliable, so I can ignore it and think -about other things. (Pete Schaeffer) +about other things. (Pete Schaeffer) Having recently succeeded in running Vim via telnet through a Nokia Communicator, I can now report that it works nicely on a Palm Pilot too. @@ -63,10 +63,10 @@ versions of 'emacs' in the late 1970's and was relieved by finding 'vi' in the first UNIX I came across in 1983). In my opinion, it's about time 'VIM' replace 'emacs' as the standard for top editors. (Bo Thide', Sweden) -I love and use VIM heavily too. (Larry Wall) +I love and use VIM heavily too. (Larry Wall) Vi is like a Ferrari, if you're a beginner, it handles like a bitch, but once -you get the hang of it, its small, powerful and FAST! (Unknown) +you get the hang of it, it's small, powerful and FAST! (Unknown) VIM is like a new model Ferrari, and sounds like one too - "VIIIIIIMMM!" (Stephen Riehm, Germany) @@ -77,12 +77,12 @@ quickly get used to and appreciate the advantages of this editor. (Garry Glendown, conclusion of an article on VIM in iX magazine 9/1998) I've recently acquired the O'Reilly book on VI (it also discusses VIM -in-depth), and I'm amazed at just how powerful this application is. (Jeffrey +in-depth), and I'm amazed at just how powerful this application is. (Jeffrey Rankin) This guide was written using the Windows 9.x distribution of GVIM, which is quite possibly the greatest thing to come along since God created the naked -girl. (Michael DiBernardo) +girl. (Michael DiBernardo) Boy, I thought I knew almost everything about VIM, but every time I browse the online documentation, I hit upon a minor but cool aspect of a VIM feature that @@ -103,7 +103,7 @@ of those "Perfect Programmer's Editor" threads and was delighted to discover that VIM already supports it. (Brendan Macmillan, Australia) I just discovered VIM (5.0) and I'm telling everyone I know about it! -I tell them VIM stands for VI for the new (M)illenium. Thanks so much! +I tell them VIM stands for VI for the new (M)illenium. Thanks so much! (Matt F. Valentine) I think from now on "vi" should be called "Vim Imitation", not the other way @@ -121,12 +121,12 @@ Whenever I move to a new computing platform, the first thing I do is to port VIM. Lately, I am simply stunned by its ease of compilation using the configure facility. (A.M. Sabuncu, Turkey) -The options are really excellent and very powerful. (Anish Maharaj) +The options are really excellent and very powerful. (Anish Maharaj) The Spring user-interface designs are in, and word from the boutiques is that 80x24 text-only mode is back with a *vengeance! Vi editor clone VIM burst onto March desk-tops with a dazzling show of pastel syntax highlights for its 5.0 -look. Strident and customizable, VIM raises eyebrows with its interpretation +look. Strident and customizable, VIM raises eyebrows with its interpretation of the classic Vi single-key macro collection. http://www.ntk.net/index.cgi?back=archive98/now0327.txt&line=179#l @@ -134,7 +134,7 @@ I just wanted to take this opportunity to let you know that VIM 5 ROCKS! Syntax highlighting: how did I survive without it?! Thank you for creating mankind's best editor! (Mun Johl, USA) -Thanks again for VIM. I use it every day on Linux. (Eric Foster-Johnson, +Thanks again for VIM. I use it every day on Linux. (Eric Foster-Johnson, author of the book "UNIX Programming Tools") The BEST EDITOR EVER (Stuart Woolford) @@ -172,17 +172,17 @@ I am really happy with such a wonderful software package. Much better than almost any expensive, off the shelf program. (Jeff Walker) Whenever I reread the VIM documentation I'm overcome with excitement at the -power of the editor. (William Edward Webber, Australia) +power of the editor. (William Edward Webber, Australia) Hurrah for VIM!! It is "at your fingertips" like vi, and has the extensions that vi sorely needs: highlighting for executing commands on blocks, an easily -navigable and digestible help screen, and more. (Paul Pax) +navigable and digestible help screen, and more. (Paul Pax) The reason WHY I don't have this amazingly useful macro any more, is that I now use VIM - and this is built in!! (Stephen Riehm, Germany) -I am a user of VIM and I love it. I use it to do all my programming, C, -C++, HTML what ever. (Tim Allwine) +I am a user of VIM and I love it. I use it to do all my programming, C, +C++, HTML what ever. (Tim Allwine) I discovered VIM after years of struggling with the original vi, and I just can't live without it any more. (Emmanuel Mogenet, USA) @@ -194,11 +194,11 @@ better than most commercial software! (Leiming Qian) This version of VIM will just blow people apart when they discover just how fantastic it is! (Tony Nugent, Australia) -I took your advice & finally got VIM & I'm really impressed. Instant convert. +I took your advice & finally got VIM & I'm really impressed. Instant convert. (Patrick Killelea, USA) VIM is by far my favorite piece of shareware and I have been particularly -pleased with version 3.0. This is really a solid piece of work. (Robert +pleased with version 3.0. This is really a solid piece of work. (Robert Colon, USA) VIM is a joy to use, it is so well thought and practical that I wonder why @@ -244,7 +244,7 @@ VIM is the greatest editor since the stone chisel. (Jose Unpingco, USA) I would like to say that with VIM I am finally making the 'emacs to vi' transition - as an Editor it is so much better in many ways: keyboard layout, -memory usage, text alteration to name 3. (Mark Adam) +memory usage, text alteration to name 3. (Mark Adam) In fact, now if I want to know what a particular setting does in vi, I fire up VIM and check out it's help! (Nikhil Patel, USA) @@ -255,7 +255,7 @@ before I encountered this program. (Steinar Knutsen, Norway) I use VIM since version 3.0. Since that time, it is the ONLY editor I use, with Solaris, Linux and OS/2 Warp. I suggest all my friends to use VIM, they try, and they continue using it. VIM is really the best software I have ever -downloaded from the Internet, and the best editor I know of. (Marco +downloaded from the Internet, and the best editor I know of. (Marco Eccettuato, Italy) diff --git a/runtime/doc/remote.txt b/runtime/doc/remote.txt index e3d3224e76..a5253d908f 100644 --- a/runtime/doc/remote.txt +++ b/runtime/doc/remote.txt @@ -1,4 +1,4 @@ -*remote.txt* For Vim version 7.0aa. Last change: 2003 Nov 10 +*remote.txt* For Vim version 7.0aa. Last change: 2005 Apr 01 VIM REFERENCE MANUAL by Bram Moolenaar @@ -87,7 +87,7 @@ SERVER NAME By default Vim will try to register the name under which it was invoked (gvim, egvim ...). This can be overridden with the --servername argument. If the specified name is not available, a postfix is applied until a free name is -encountered, ie. "gvim1" for the second invocation of gvim on a particular +encountered, i.e. "gvim1" for the second invocation of gvim on a particular X-server. The resulting name is available in the servername builtin variable |v:servername|. The case of the server name is ignored, thus "gvim" and "GVIM" are considered equal. @@ -121,7 +121,7 @@ wait for each of the files to have been edited. This uses the BufUnload event, thus as soon as a file has been unloaded, Vim assumes you are done editing it. Note that the --remote and --remote-wait arguments will consume the rest of -the command line. Ie. all remaining arguments will be regarded as filenames. +the command line. I.e. all remaining arguments will be regarded as filenames. You can not put options there! diff --git a/runtime/doc/repeat.txt b/runtime/doc/repeat.txt index 57221023f8..66e6d30840 100644 --- a/runtime/doc/repeat.txt +++ b/runtime/doc/repeat.txt @@ -1,4 +1,4 @@ -*repeat.txt* For Vim version 7.0aa. Last change: 2005 Feb 28 +*repeat.txt* For Vim version 7.0aa. Last change: 2005 Apr 01 VIM REFERENCE MANUAL by Bram Moolenaar @@ -176,7 +176,7 @@ For writing a Vim script, see chapter 41 of the user manual |usr_41.txt|. matching files. Example: > :runtime! plugin/*.vim < This is what Vim uses to load the plugin files when - starting up. This similar command: > + starting up. This similar command: > :runtime plugin/*.vim < would source the first file only. diff --git a/runtime/doc/scroll.txt b/runtime/doc/scroll.txt index 2627533662..1aa1b9304c 100644 --- a/runtime/doc/scroll.txt +++ b/runtime/doc/scroll.txt @@ -1,4 +1,4 @@ -*scroll.txt* For Vim version 7.0aa. Last change: 2005 Feb 10 +*scroll.txt* For Vim version 7.0aa. Last change: 2005 Apr 01 VIM REFERENCE MANUAL by Bram Moolenaar @@ -265,12 +265,12 @@ You can also use Alt and Ctrl modifiers. This only works when Vim gets the scroll wheel events, of course. You can check if this works with the "xev" program. -When using Xfree86, the /etc/XF86Config file should have the correct entry for +When using XFree86, the /etc/XF86Config file should have the correct entry for your mouse. For FreeBSD, this entry works for a Logitech scrollmouse: > Protocol "MouseMan" Device "/dev/psm0" ZAxisMapping 4 5 -See the Xfree86 documentation for information. +See the XFree86 documentation for information. *xterm-mouse-wheel* To use the mouse wheel in a new xterm you only have to make the scroll wheel diff --git a/runtime/doc/spell.txt b/runtime/doc/spell.txt index 84c9e753b5..04e1cfd0be 100644 --- a/runtime/doc/spell.txt +++ b/runtime/doc/spell.txt @@ -1,4 +1,4 @@ -*spell.txt* For Vim version 7.0aa. Last change: 2005 Mar 22 +*spell.txt* For Vim version 7.0aa. Last change: 2005 Apr 15 VIM REFERENCE MANUAL by Bram Moolenaar @@ -7,7 +7,8 @@ Spell checking *spell* 1. Quick start |spell-quickstart| -X. Spell file format |spell-file-format| +2. Generating a spell file |spell-mkspell| +9. Spell file format |spell-file-format| {Vi does not have any of these commands} @@ -21,18 +22,29 @@ This command switches on spell checking: > :setlocal spell spelllang=en_us -This switches the 'spell' option on and specifies to check for US English. +This switches on the 'spell' option and specifies to check for US English. The words that are not recognized are highlighted with one of these: SpellBad word not recognized SpellRare rare word SpellLocal wrong spelling for selected region +Vim only checks words for spelling, there is no grammar check. + +To search for the next misspelled word: + + *]s* *E756* +]s Move to next misspelled word after the cursor. + + *[s* +[s Move to next misspelled word before the cursor. + DOESN'T WORK YET! + PERFORMANCE Note that Vim does on-the-fly spellc