Hi Please find attached doc fixes for vim-8.2.2041.
Regards Dominique -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAON-T_i3JKAX7QOHH3oCey7hfma2BB%2ByBH0vJHQJHgadP4ZfZQ%40mail.gmail.com.
diff --git a/runtime/doc/version8.txt b/runtime/doc/version8.txt index 951a3070f..f7dc1fc07 100644 --- a/runtime/doc/version8.txt +++ b/runtime/doc/version8.txt @@ -76,7 +76,7 @@ Timers ~ Also asynchronous are timers. They can fire once or repeatedly and invoke a function to do any work. For example: > let tempTimer = timer_start(4000, 'CheckTemp') -This will call the CheckTemp() function four seconds (4000 milli seconds) +This will call the CheckTemp() function four seconds (4000 milliseconds) later. See |timer_start()|. diff --git a/runtime/doc/vim9.txt b/runtime/doc/vim9.txt index 9d42b68d0..883e9e644 100644 --- a/runtime/doc/vim9.txt +++ b/runtime/doc/vim9.txt @@ -1122,7 +1122,7 @@ are used. That is different, thus it's good to use a different command: `:var`. This is used in many languages. The semantics might be slightly different, but it's easily recognized as a declaration. -Using `:const` for constants is common, but the semantics vary. Some +Using `:const` for constants is common, but the semantics varies. Some languages only make the variable immutable, others also make the value immutable. Since "final" is well known from Java for only making the variable immutable we decided to use that. And then `:const` can be used for making @@ -1182,7 +1182,7 @@ text not starting with a number would be converted to zero, which is considered false. Thus using a string for a condition would often not give an error and be considered false. That is confusing. -In Vim9 type checking is more strict to avoid mistakes. Where a condition is +In Vim9 type checking is stricter to avoid mistakes. Where a condition is used, e.g. with the `:if` command and the `||` operator, only boolean-like values are accepted: true: `true`, `v:true`, `1`, `0 < 9` diff --git a/src/INSTALLpc.txt b/src/INSTALLpc.txt index ee22b6549..2b610f037 100644 --- a/src/INSTALLpc.txt +++ b/src/INSTALLpc.txt @@ -380,7 +380,7 @@ The original 'mingw32' compiler is outdated, and may no longer work: Once you have downloaded the compiler binaries, unpack them on your hard disk somewhere, and put them on your PATH. Go to the Control Panel, (Performance and Maintenance), System, Advanced, and edit the environment from there. If -you use the standalone MinGW-w64 compiler, the path may depends on your +you use the standalone MinGW-w64 compiler, the path may depend on your installation. If you use msys2 compilers, set your installed paths (normally one of the following): diff --git a/src/INSTALLvms.txt b/src/INSTALLvms.txt index 3e05b5327..e336da4cb 100644 --- a/src/INSTALLvms.txt +++ b/src/INSTALLvms.txt @@ -9,12 +9,12 @@ If you already have an executable version of Vim, you don't need this. If you skip settings described here, then you will get the default Vim behavior as it is documented, which should be fine for most users. -The file "feature.h" can be edited to match your preferences, but this files +The file "feature.h" can be edited to match your preferences, but this file does not describe possibilities hidden in feature.h acrobatics, however -parameters from MAKE_VMS.MMS actively uses and sets up parameters in relation +parameters from MAKE_VMS.MMS actively use and set up parameters in relation with feature.h -More information and case analysis you can found in os_vms.txt +More information and case analysis you can find in os_vms.txt ([runtime.doc]os_vms.txt or :help vms from vim prompt) Contents: @@ -145,7 +145,7 @@ from CVS mirror ftp://ftp.polarhome.com/pub/cvs/SOURCE/ Parameter name : VIM_XIM Description : X Input Method. For entering special languages - like chinese and Japanese. Please define just + like Chinese and Japanese. Please define just one: VIM_XIM or VIM_HANGULIN Options: : YES - Build with support Uncommented - build without support. @@ -210,7 +210,7 @@ from CVS mirror ftp://ftp.polarhome.com/pub/cvs/SOURCE/ XXD.EXE you should change to subdirectory <.CTAGS> or <.XXD> and build them separately. -5.2. In these directories you can found one make file for VMS as well. +5.2. In these directories you can find one make file for VMS as well. Please read the detailed build instructions in the related *.MMS file. 6. Deployment @@ -300,7 +300,7 @@ perl_env : So far it works just on Alpha and IA64. More information at: http://www.openvms.compaq.com/openvms/products/ips/gtk.html - You need also the OpenVMS Porting Library: + You also need the OpenVMS Porting Library: http://www.openvms.compaq.com/openvms/products/ips/porting.html Source code for GTK and porting library that is used to build @@ -346,7 +346,7 @@ perl_env : Edit PERL_INC = to point to perl includes directory where is extern.h - Build as usually. + Build as usual. 7.4 PYTHON @@ -358,7 +358,7 @@ perl_env : python.h is located. Enable Python feature at make_vms.mms with VIM_PYTHON = YES - Build as usually. + Build as usual. 7.5 TCL @@ -371,13 +371,13 @@ perl_env : Edit TCL_INC = to point to TCL includes directory where is tcl.h - Build as usually. + Build as usual. 8. Notes 8.1. New Compaq C compiler - If you are using Compaq C compiler V6.2 or newer, Informational messages + If you are using Compaq C compiler V6.2 or newer, informational messages of the type QUESTCOMPARE will be displayed. You should ignore those messages ; they are generated only because some test comparisons are done with variables which type vary depending on the OS. Under VMS, those are
