iTerm2 PSMTabBarControl

https://github.com/gnachman/iTerm2/tree/master/ThirdParty/PSMTabBarControl
2026-06-02 11:19:22 +02:00 · 2016-10-01 23:48:20 -07:00
1349 changed files with 55939 additions and 135638 deletions
@@ -5,7 +5,6 @@ src/xxd/xxd
 src/auto/if_perl.c
 src/auto/gui_gtk_gresources.c
 src/auto/gui_gtk_gresources.h
-src/objects/.dirstamp
 src/tags

 # We do need src/auto/configure.
@@ -38,7 +37,6 @@ src/pathdef.c
 src/Obj*/pathdef.c
 gvimext.dll
 gvimext.lib
-gvim.lib
 runtime/doc/uganda.nsis.txt

 # Borland C++
@@ -79,11 +77,9 @@ src/testdir/test.log
 src/testdir/dostmp/*
 src/testdir/messages
 src/testdir/viminfo
-src/testdir/opt_test.vim
 src/memfile_test
 src/json_test
 src/message_test
-src/kword_test

 # From MacVim
 .*.swp
@@ -1,10 +1,9 @@
 language: c
-dist: trusty

 os:
  - osx

-osx_image: xcode9.2
+osx_image: xcode8

 compiler:
  - clang
@@ -18,17 +17,16 @@ env:
    vi_cv_path_plain_lua=/usr/local/bin/lua
    vi_cv_dll_name_perl=/System/Library/Perl/5.16/darwin-thread-multi-2level/CORE/libperl.dylib
    vi_cv_dll_name_python=/System/Library/Frameworks/Python.framework/Versions/2.7/Python
-    vi_cv_dll_name_python3=/usr/local/Frameworks/Python.framework/Versions/3.6/Python
+    vi_cv_dll_name_python3=/usr/local/Frameworks/Python.framework/Versions/3.5/Python
    VIMCMD=src/MacVim/build/Release/MacVim.app/Contents/MacOS/Vim
-    "CONFOPT='--with-features=huge --enable-multibyte --enable-terminal --enable-netbeans --with-tlib=ncurses --enable-cscope --enable-perlinterp=dynamic --enable-pythoninterp=dynamic --enable-python3interp=dynamic --enable-rubyinterp=dynamic --with-ruby-command=/usr/local/bin/ruby --enable-luainterp=dynamic --with-lua-prefix=/usr/local --enable-gui=macvim'"
+    "CONFOPT='--with-features=huge --enable-multibyte --enable-netbeans --with-tlib=ncurses --enable-cscope --enable-perlinterp=dynamic --enable-pythoninterp=dynamic --enable-python3interp=dynamic --enable-rubyinterp=dynamic --enable-luainterp=dynamic --with-lua-prefix=/usr/local --enable-gui=macvim'"

 sudo: false

 before_install:
  - brew update || brew update
-  - brew upgrade python
+  - brew install python3
  - brew install lua
-  - brew install ruby

 script:
  - NPROC=$(getconf _NPROCESSORS_ONLN)
@@ -12,8 +12,6 @@ SRC_ALL =	\
 		src/arabic.c \
 		src/arabic.h \
 		src/ascii.h \
-		src/beval.c \
-		src/beval.h \
 		src/blowfish.c \
 		src/buffer.c \
 		src/channel.c \
@@ -26,7 +24,6 @@ SRC_ALL =	\
 		src/edit.c \
 		src/eval.c \
 		src/evalfunc.c \
-		src/ex_cmdidxs.h \
 		src/ex_cmds.c \
 		src/ex_cmds.h \
 		src/ex_cmds2.c \
@@ -43,11 +40,11 @@ SRC_ALL =	\
 		src/gui.c \
 		src/gui.h \
 		src/gui_beval.c \
+		src/gui_beval.h \
 		src/hardcopy.c \
 		src/hashtab.c \
 		src/json.c \
 		src/json_test.c \
-		src/kword_test.c \
 		src/list.c \
 		src/keymap.h \
 		src/macros.h \
@@ -86,7 +83,6 @@ SRC_ALL =	\
 		src/syntax.c \
 		src/tag.c \
 		src/term.c \
-		src/terminal.c \
 		src/term.h \
 		src/termlib.c \
 		src/ui.c \
@@ -100,26 +96,20 @@ SRC_ALL =	\
 		src/tee/tee.c \
 		src/xxd/xxd.c \
 		src/main.aap \
-		src/testdir/gen_opt_test.vim \
 		src/testdir/main.aap \
 		src/testdir/README.txt \
 		src/testdir/Make_all.mak \
 		src/testdir/*.in \
 		src/testdir/*.py \
-		src/testdir/lsan-suppress.txt \
 		src/testdir/sautest/autoload/*.vim \
 		src/testdir/runtest.vim \
 		src/testdir/shared.vim \
-		src/testdir/screendump.vim \
-		src/testdir/view_util.vim \
 		src/testdir/setup.vim \
-		src/testdir/gui_init.vim \
-		src/testdir/setup_gui.vim \
-		src/testdir/gui_preinit.vim \
 		src/testdir/test[0-9]*.ok \
 		src/testdir/test[0-9]*a.ok \
 		src/testdir/test_[a-z]*.ok \
 		src/testdir/test49.vim \
+		src/testdir/test60.vim \
 		src/testdir/test83-tags? \
 		src/testdir/test77a.com \
 		src/testdir/test_*.vim \
@@ -132,17 +122,11 @@ SRC_ALL =	\
 		src/testdir/pythonx/topmodule/submodule/subsubmodule/subsubsubmodule.py \
 		src/testdir/python_after/*.py \
 		src/testdir/python_before/*.py \
-		src/testdir/pyxfile/*.py \
 		src/testdir/bench*.in \
 		src/testdir/bench*.vim \
-		src/testdir/dumps/*.dump \
 		src/testdir/samples/*.txt \
-		src/testdir/samples/test000 \
-		src/testdir/if_ver*.vim \
-		src/testdir/color_ramp.vim \
 		src/proto.h \
 		src/proto/arabic.pro \
-		src/proto/beval.pro \
 		src/proto/blowfish.pro \
 		src/proto/buffer.pro \
 		src/proto/channel.pro \
@@ -195,7 +179,6 @@ SRC_ALL =	\
 		src/proto/syntax.pro \
 		src/proto/tag.pro \
 		src/proto/term.pro \
-		src/proto/terminal.pro \
 		src/proto/termlib.pro \
 		src/proto/ui.pro \
 		src/proto/undo.pro \
@@ -203,76 +186,6 @@ SRC_ALL =	\
 		src/proto/version.pro \
 		src/proto/winclip.pro \
 		src/proto/window.pro \
-		src/libvterm/.bzrignore \
-		src/libvterm/.gitignore \
-		src/libvterm/LICENSE \
-		src/libvterm/Makefile \
-		src/libvterm/README \
-		src/libvterm/tbl2inc_c.pl \
-		src/libvterm/vterm.pc.in \
-		src/libvterm/bin/unterm.c \
-		src/libvterm/bin/vterm-ctrl.c \
-		src/libvterm/bin/vterm-dump.c \
-		src/libvterm/doc/URLs \
-		src/libvterm/doc/seqs.txt \
-		src/libvterm/include/vterm.h \
-		src/libvterm/include/vterm_keycodes.h \
-		src/libvterm/src/encoding.c \
-		src/libvterm/src/encoding/DECdrawing.inc \
-		src/libvterm/src/encoding/DECdrawing.tbl \
-		src/libvterm/src/encoding/uk.inc \
-		src/libvterm/src/encoding/uk.tbl \
-		src/libvterm/src/keyboard.c \
-		src/libvterm/src/mouse.c \
-		src/libvterm/src/parser.c \
-		src/libvterm/src/pen.c \
-		src/libvterm/src/rect.h \
-		src/libvterm/src/screen.c \
-		src/libvterm/src/state.c \
-		src/libvterm/src/unicode.c \
-		src/libvterm/src/utf8.h \
-		src/libvterm/src/vterm.c \
-		src/libvterm/src/vterm_internal.h \
-		src/libvterm/t/02parser.test \
-		src/libvterm/t/03encoding_utf8.test \
-		src/libvterm/t/10state_putglyph.test \
-		src/libvterm/t/11state_movecursor.test \
-		src/libvterm/t/12state_scroll.test \
-		src/libvterm/t/13state_edit.test \
-		src/libvterm/t/14state_encoding.test \
-		src/libvterm/t/15state_mode.test \
-		src/libvterm/t/16state_resize.test \
-		src/libvterm/t/17state_mouse.test \
-		src/libvterm/t/18state_termprops.test \
-		src/libvterm/t/20state_wrapping.test \
-		src/libvterm/t/21state_tabstops.test \
-		src/libvterm/t/22state_save.test \
-		src/libvterm/t/25state_input.test \
-		src/libvterm/t/26state_query.test \
-		src/libvterm/t/27state_reset.test \
-		src/libvterm/t/28state_dbl_wh.test \
-		src/libvterm/t/29state_fallback.test \
-		src/libvterm/t/30pen.test \
-		src/libvterm/t/40screen_ascii.test \
-		src/libvterm/t/41screen_unicode.test \
-		src/libvterm/t/42screen_damage.test \
-		src/libvterm/t/43screen_resize.test \
-		src/libvterm/t/44screen_pen.test \
-		src/libvterm/t/45screen_protect.test \
-		src/libvterm/t/46screen_extent.test \
-		src/libvterm/t/47screen_dbl_wh.test \
-		src/libvterm/t/48screen_termprops.test \
-		src/libvterm/t/90vttest_01-movement-1.test \
-		src/libvterm/t/90vttest_01-movement-2.test \
-		src/libvterm/t/90vttest_01-movement-3.test \
-		src/libvterm/t/90vttest_01-movement-4.test \
-		src/libvterm/t/90vttest_02-screen-1.test \
-		src/libvterm/t/90vttest_02-screen-2.test \
-		src/libvterm/t/90vttest_02-screen-3.test \
-		src/libvterm/t/90vttest_02-screen-4.test \
-		src/libvterm/t/92lp1640917.test \
-		src/libvterm/t/harness.c \
-		src/libvterm/t/run-test.pl \


 # source files for Unix only
@@ -294,8 +207,7 @@ SRC_UNIX =	\
 		src/config.mk.dist \
 		src/config.mk.in \
 		src/configure \
-		src/configure.ac \
-		src/create_cmdidxs.vim \
+		src/configure.in \
 		src/gui_at_fs.c \
 		src/gui_at_sb.c \
 		src/gui_at_sb.h \
@@ -319,7 +231,7 @@ SRC_UNIX =	\
 		src/link.sh \
 		src/installman.sh \
 		src/installml.sh \
-		src/install-sh \
+		src/mkinstalldirs \
 		src/os_unix.c \
 		src/os_unix.h \
 		src/os_unixx.h \
@@ -410,7 +322,6 @@ SRC_DOS =	\
 		src/msvcsetup.bat \
 		src/msvc2008.bat \
 		src/msvc2010.bat \
-		src/msvc2015.bat \
 		src/dimm.idl \
 		src/dlldata.c \
 		src/dosinst.c \
@@ -455,7 +366,6 @@ SRC_DOS =	\
 		src/xxd/Make_mvc.mak \
 		nsis/gvim.nsi \
 		nsis/gvim_version.nsh \
-		nsis/vimrc.ini \
 		nsis/README.txt \
 		uninstal.txt \
 		src/VisVim/Commands.cpp \
@@ -586,7 +496,6 @@ RT_ALL =	\
 		runtime/doc/*.txt \
 		runtime/doc/Makefile \
 		runtime/doc/doctags.c \
-		runtime/doc/test_urls.vim \
 		runtime/doc/vim.1 \
 		runtime/doc/evim.1 \
 		runtime/doc/vimdiff.1 \
@@ -646,7 +555,6 @@ RT_ALL =	\
 		runtime/pack/dist/opt/matchit/doc/tags \
 		runtime/pack/dist/opt/shellmenu/plugin/shellmenu.vim \
 		runtime/pack/dist/opt/swapmouse/plugin/swapmouse.vim \
-		runtime/pack/dist/opt/termdebug/plugin/termdebug.vim \

 # runtime files for all distributions without CR-NL translation
 RT_ALL_BIN =	\
@@ -664,11 +572,9 @@ RT_SCRIPTS =	\
 		runtime/makemenu.vim \
 		runtime/autoload/*.vim \
 		runtime/autoload/README.txt \
-		runtime/autoload/dist/*.vim \
 		runtime/autoload/xml/*.vim \
 		runtime/colors/*.vim \
 		runtime/colors/README.txt \
-		runtime/colors/tools/*.vim \
 		runtime/compiler/*.vim \
 		runtime/compiler/README.txt \
 		runtime/indent/*.vim \
@@ -811,6 +717,7 @@ EXTRA =		\
 		farsi/README.txt \
 		farsi/fonts/*/far-* \
 		runtime/vimlogo.xpm \
+		src/swis.s \
 		src/tee/Makefile \
 		src/tee/Make_mvc.mak \
 		src/tee/tee.c \
@@ -120,28 +120,27 @@ MINOR = 0
 #
 # MS-Windows:
 # - Run make on Unix to update the ".mo" files.
-# - Get 32 bit libintl-8.dll, libiconv-2.dll and libgcc_s_sjlj-1.dll. E.g. from
+# - Get libintl-8.dll and libiconv-2.dll. E.g. from
 #   https://mlocati.github.io/gettext-iconv-windows/ .
-#   Use the "shared-32.zip file and extract the archive to get the files.
-#   Put them in the gettext32 directory, "make dosrt" uses them.
-# - Get 64 bit libintl-8.dll and libiconv-2.dll. E.g. from
-#   https://mlocati.github.io/gettext-iconv-windows/ .
-#   Use the "shared-64.zip file and extract the archive to get the files.
-#   Put them in the gettext64 directory, "make dosrt" uses them.
+#   Put them in the top directory, "make dosrt" uses them.
 # - > make dossrc
 #   > make dosrt
 #   Unpack dist/vim##rt.zip and dist/vim##src.zip on an MS-Windows PC.
-#   This creates the directory vim/vim80 and puts all files in there.
 # Win32 console version build:
-# - See src/INSTALLpc.txt for installing the compiler and SDK.
-# - Set environment for Visual C++ 2015:
-#   > cd src
-#   > msvc2015.bat
-# - Build the console binary:
+# - Set environment for Visual C++ 2008, e.g.:
+#   > src/msvc2008.bat
+#   Or: 
+#   > C:\Program Files (x86)\Microsoft Visual Studio 9.0\VC\bin\vcvars32.bat
+#   Or, when using the Visual C++ Toolkit 2003: "msvcsetup.bat" (adjust the
+#   paths when necessary).
+#   For Windows 98/ME the 2003 version is required, but then the executable
+#   won't work on Windows 7 and 64 bit systems.
+# - > cd src
 #   > nmake -f Make_mvc.mak
-# - Run the tests and check the ouput:
+# - Run the tests:
 #   > nmake -f Make_mvc.mak testclean
 #   > nmake -f Make_mvc.mak test
+#   - check the output.
 # - Rename (using ../tools/rename.bat):
 #           vim.exe to vimw32.exe
 #           tee/tee.exe to teew32.exe
@@ -152,18 +151,19 @@ MINOR = 0
 # Win32 GUI version build:
 # - > cd src
 #   > nmake -f Make_mvc.mak GUI=yes
-# - Run the tests and check the output:
+# - Run the tests:
 #   > nmake -f Make_mvc.mak testclean
 #   > nmake -f Make_mvc.mak testgvim
+#   - check the output.
 # - move "gvim.exe" to here (otherwise the OLE version will overwrite it).
 # - Move gvim.pdb to here.
 # - Copy "GvimExt/gvimext.dll" to here.
 # - Delete vimrun.exe, install.exe and uninstal.exe.
 # Win32 GUI version with OLE, PERL, Ruby, TCL, PYTHON and dynamic IME:
 # - Install the interfaces you want, see src/INSTALLpc.txt
-#   Adjust bigvim.bat to match the version of each interface you want.
 # - Build:
 #   > cd src
+#   Adjust bigvim.bat to match the version of each interface you want.
 #   > bigvim.bat
 # - Run the tests:
 #   > nmake -f Make_mvc.mak testclean
@@ -187,11 +187,10 @@ MINOR = 0
 #	gvimext64.dll in src/GvimExt
 #	VisVim.dll in src/VisVim
 #   Note: VisVim needs to be build with MSVC 5, newer versions don't work.
-#   gvimext64.dll can be obtained from:
-#   https://github.com/vim/vim-win32-installer/releases
-#	It is part of gvim_8.0.*_x64.zip as vim/vim80/GvimExt/gvimext64.dll.
+#   gvimext64.dll can be obtained from http://code.google.com/p/vim-win3264/
+#	It is part of vim72.zip as vim72/gvimext.dll.
 # - Make sure there is a diff.exe two levels up (get it from a previous Vim
-#   version).  Also put winpty32.dll and winpty-agent.exe there.
+#   version).
 # - go to ../nsis and do:
 #   > makensis gvim.nsi  (takes a few minutes).
 #      ignore warning for libwinpthread-1.dll
@@ -467,13 +466,8 @@ dosrt_files: dist prepare no_title.vim
 		cp $$i dist/vim/$(VIMRTDIR)/lang/$$n/LC_MESSAGES/vim.mo; \
 	      fi \
 	    done
-	mkdir dist/vim/$(VIMRTDIR)/gettext32
-	cp gettext32/libintl-8.dll dist/vim/$(VIMRTDIR)/gettext32/
-	cp gettext32/libiconv-2.dll dist/vim/$(VIMRTDIR)/gettext32/
-	cp gettext32/libgcc_s_sjlj-1.dll dist/vim/$(VIMRTDIR)/gettext32/
-	mkdir dist/vim/$(VIMRTDIR)/gettext64
-	cp gettext64/libintl-8.dll dist/vim/$(VIMRTDIR)/gettext64/
-	cp gettext64/libiconv-2.dll dist/vim/$(VIMRTDIR)/gettext64/
+	cp libintl-8.dll dist/vim/$(VIMRTDIR)/
+	cp libiconv-2.dll dist/vim/$(VIMRTDIR)/


 # Used before uploading.  Don't delete the AAPDIR/sign files!
@@ -500,10 +494,7 @@ dosbin_gvim: dist no_title.vim dist/$(COMMENT_GVIM)
 	cp vimrun.exe dist/vim/$(VIMRTDIR)/vimrun.exe
 	cp installw32.exe dist/vim/$(VIMRTDIR)/install.exe
 	cp uninstalw32.exe dist/vim/$(VIMRTDIR)/uninstal.exe
-	mkdir dist/vim/$(VIMRTDIR)/GvimExt32
-	cp gvimext.dll dist/vim/$(VIMRTDIR)/GvimExt32/gvimext.dll
-	mkdir dist/vim/$(VIMRTDIR)/GvimExt64
-	cp gvimext64.dll dist/vim/$(VIMRTDIR)/GvimExt64/gvimext.dll
+	cp gvimext.dll dist/vim/$(VIMRTDIR)/gvimext.dll
 	cd dist && zip -9 -rD -z gvim$(VERSION).zip vim <$(COMMENT_GVIM)
 	cp gvim.pdb dist/gvim$(VERSION).pdb

@@ -1,13 +1,38 @@
 README_mac.txt for version 8.0 of Vim: Vi IMproved.

-How to install MacVim?
+This file explains the installation of MacVim.
+See "README.txt" for general information about Vim.
+See "src/MacVim/README" for an overview of the MacVim specific source code.
+
+MacVim uses the usual configure/make steps to build the binary but instead of
+"make install" you just drag the app bundle into the directory you wish to
+install in (usually `/Applications').
+
+
+How to build and install
 ========================

-Download MacVim.dmg from latest binary release page https://github.com/macvim-dev/macvim/releases/latest , open the dmg file, and copy MacVim.app to /Applications.
+Run `./configure` in the `src/` directory with the flags you want (call
+`./configure --help` to see a list of flags) e.g.:

+    $ cd src
+    $ ./configure --with-features=huge \
+                  --enable-rubyinterp \
+                  --enable-pythoninterp \
+                  --enable-perlinterp \
+                  --enable-cscope

-Questions?
-========================
+Now build the project using `make`:

-Please take a look at the home page http://macvim-dev.github.io/macvim/
+    $ make

+The resulting app bundle will reside under `MacVim/build/Release`.  To try it
+out quickly, type:
+
+    $ open MacVim/build/Release/MacVim.app
+
+To install MacVim, type
+
+    $ open MacVim/build/Release
+
+and drag the MacVim icon into your `Applications` folder.
@@ -16,7 +16,6 @@ matrix:

 before_build:
  - '"C:\Program Files\Microsoft SDKs\Windows\v7.1\Bin\SetEnv.cmd" /x64 /release'
-  - 'set INCLUDE=%INCLUDE%C:\Program Files (x86)\Windows Kits\8.1\Include\um'

 build_script:
  - src/appveyor.bat
@@ -1,5 +1,5 @@
 This builds a one-click install for Vim for Win32 using the Nullsoft
-Installation System (NSIS), available at http://nsis.sourceforge.net/
+Installation System (NSIS), available at http://www.nullsoft.com/free/nsis/

 To build the installable .exe:

@@ -17,14 +17,8 @@ To build the installable .exe:
 	uninstal.exe,
 	xxd/xxd.exe,

-    Then execute tools/rename.bat to rename the executables. (mv command is
-    required.)
-
 3.  Go to the GvimExt directory and build gvimext.dll (or get it from a binary
-    archive).  Both 64- and 32-bit versions are needed and should be placed
-    as follows:
-	64-bit: src/GvimExt/gvimext64.dll
-	32-bit: src/GvimExt/gvimext.dll
+    archive).

 4.  Go to the VisVim directory and build VisVim.dll (or get it from a binary
    archive).
@@ -33,35 +27,13 @@ To build the installable .exe:
    get them from a binary archive).

 6.  Get a "diff.exe" program and put it in the "../.." directory (above the
-    "vim80" directory, it's the same for all Vim versions).
+    "vim61" directory, it's the same for all Vim versions).
    You can find one in previous Vim versions or in this archive:
 		http://www.mossbayeng.com/~ron/vim/diffutils.tar.gz
-    Also put winpty32.dll and winpty-agent.exe there.

 7.  Do "make uganda.nsis.txt" in runtime/doc.  This requires sed, you may have
    to do this on Unix.  Make sure the file is in DOS file format!

-8.  Get gettext and iconv DLLs from the following site:
-	https://github.com/mlocati/gettext-iconv-windows/releases
-    Both 64- and 32-bit versions are needed.
-    Download the files gettextX.X.X.X-iconvX.XX-shared-{32,64}.zip, extract
-    DLLs and place them as follows:
-
-	<GETTEXT directory>
-	    |
-	    + gettext32/
-	    |	libintl-8.dll
-	    |	libiconv-2.dll
-	    |	libgcc_s_sjlj-1.dll
-	    |
-	    ` gettext64/
-		libintl-8.dll
-		libiconv-2.dll
-
-    The default <GETTEXT directory> is "..", however, you can change it by
-    passing /DGETTEXT=... option to the makensis command.
-
-
 Install NSIS if you didn't do that already.
 Also install UPX, if you want a compressed file.

@@ -20,15 +20,8 @@
  !define VIMTOOLS ..\..
 !endif

-# Location of gettext.
-# It must contain two directories: gettext32 and gettext64.
-# See README.txt for detail.
-!ifndef GETTEXT
-  !define GETTEXT ${VIMRT}
-!endif
-
 # Comment the next line if you don't have UPX.
-# Get it at https://upx.github.io/
+# Get it at http://upx.sourceforge.net
 !define HAVE_UPX

 # comment the next line if you do not want to add Native Language Support
@@ -83,24 +76,17 @@ SilentInstall normal
 # These are the pages we use
 Page license
 Page components
-Page custom SetCustom ValidateCustom ": _vimrc setting"
 Page directory "" "" CheckInstallDir
 Page instfiles
 UninstPage uninstConfirm
 UninstPage instfiles

-# Reserve files
-# Needed for showing the _vimrc setting page faster.
-ReserveFile /plugin InstallOptions.dll
-ReserveFile vimrc.ini
-
 ##########################################################
 # Functions

 Function .onInit
  MessageBox MB_YESNO|MB_ICONQUESTION \
 	"This will install Vim ${VER_MAJOR}.${VER_MINOR} on your computer.$\n Continue?" \
-	/SD IDYES \
 	IDYES NoAbort
 	    Abort ; causes installer to quit.
 	NoAbort:
@@ -141,10 +127,6 @@ Function .onInit
  StrCpy $1 "-register-OLE"
  StrCpy $2 "gvim evim gview gvimdiff vimtutor"

-  # Extract InstallOptions files
-  # $PLUGINSDIR will automatically be removed when the installer closes
-  InitPluginsDir
-  File /oname=$PLUGINSDIR\vimrc.ini "vimrc.ini"
 FunctionEnd

 Function .onUserAbort
@@ -196,7 +178,7 @@ FunctionEnd

 ##########################################################
 Section "Vim executables and runtime files"
-	SectionIn 1 2 3 RO
+	SectionIn 1 2 3

 	# we need also this here if the user changes the instdir
 	StrCpy $0 "$INSTDIR\vim${VER_MAJOR}${VER_MINOR}"
@@ -208,16 +190,13 @@ Section "Vim executables and runtime files"
 	File ${VIMSRC}\vimrun.exe
 	File /oname=tee.exe ${VIMSRC}\teew32.exe
 	File /oname=xxd.exe ${VIMSRC}\xxdw32.exe
+	File ${VIMTOOLS}\diff.exe
 	File ${VIMRT}\vimtutor.bat
 	File ${VIMRT}\README.txt
 	File ..\uninstal.txt
 	File ${VIMRT}\*.vim
 	File ${VIMRT}\rgb.txt

-	File ${VIMTOOLS}\diff.exe
-	File ${VIMTOOLS}\winpty32.dll
-	File ${VIMTOOLS}\winpty-agent.exe
-
 	SetOutPath $0\colors
 	File ${VIMRT}\colors\*.*

@@ -236,14 +215,6 @@ Section "Vim executables and runtime files"

 	SetOutPath $0\macros
 	File ${VIMRT}\macros\*.*
-	SetOutPath $0\macros\hanoi
-	File ${VIMRT}\macros\hanoi\*.*
-	SetOutPath $0\macros\life
-	File ${VIMRT}\macros\life\*.*
-	SetOutPath $0\macros\maze
-	File ${VIMRT}\macros\maze\*.*
-	SetOutPath $0\macros\urm
-	File ${VIMRT}\macros\urm\*.*

 	SetOutPath $0\pack\dist\opt\dvorak\dvorak
 	File ${VIMRT}\pack\dist\opt\dvorak\dvorak\*.*
@@ -273,9 +244,6 @@ Section "Vim executables and runtime files"
 	SetOutPath $0\autoload
 	File ${VIMRT}\autoload\*.*

-	SetOutPath $0\autoload\dist
-	File ${VIMRT}\autoload\dist\*.*
-
 	SetOutPath $0\autoload\xml
 	File ${VIMRT}\autoload\xml\*.*

@@ -348,67 +316,24 @@ Section "Add an Edit-with-Vim context menu entry"
 	SetOutPath $0
 	ClearErrors
 	SetOverwrite try
-
 	${If} ${RunningX64}
-	  # Install 64-bit gvimext.dll into the GvimExt64 directory.
-	  SetOutPath $0\GvimExt64
-	  ClearErrors
 	  File /oname=gvimext.dll ${VIMSRC}\GvimExt\gvimext64.dll
-!ifdef HAVE_NLS
-	  File ${GETTEXT}\gettext64\libintl-8.dll
-	  File ${GETTEXT}\gettext64\libiconv-2.dll
-!endif
-
-	  IfErrors 0 GvimExt64Done
-
-	  # Can't copy gvimext.dll, create it under another name and rename it
-	  # on next reboot.
-	  GetTempFileName $3 $0\GvimExt64
-	  File /oname=$3 ${VIMSRC}\GvimExt\gvimext64.dll
-	  Rename /REBOOTOK $3 $0\GvimExt64\gvimext.dll
-!ifdef HAVE_NLS
-	  GetTempFileName $3 $0\GvimExt64
-	  File /oname=$3 ${GETTEXT}\gettext64\libintl-8.dll
-	  Rename /REBOOTOK $3 $0\GvimExt64\libintl-8.dll
-	  GetTempFileName $3 $0\GvimExt64
-	  File /oname=$3 ${GETTEXT}\gettext64\libiconv-2.dll
-	  Rename /REBOOTOK $3 $0\GvimExt64\libiconv-2.dll
-!endif
+	${Else}
+	  File /oname=gvimext.dll ${VIMSRC}\GvimExt\gvimext.dll
 	${EndIf}
-
-	GvimExt64Done:
-
-	# Install 32-bit gvimext.dll into the GvimExt32 directory.
-	SetOutPath $0\GvimExt32
-	ClearErrors
-
-	File /oname=gvimext.dll ${VIMSRC}\GvimExt\gvimext.dll
-!ifdef HAVE_NLS
-	File ${GETTEXT}\gettext32\libintl-8.dll
-	File ${GETTEXT}\gettext32\libiconv-2.dll
-	File ${GETTEXT}\gettext32\libgcc_s_sjlj-1.dll
-!endif
-
-	IfErrors 0 GvimExt32Done
+	IfErrors 0 GvimExtDone

 	# Can't copy gvimext.dll, create it under another name and rename it on
 	# next reboot.
-	GetTempFileName $3 $0\GvimExt32
-	File /oname=$3 ${VIMSRC}\GvimExt\gvimext.dll
-	Rename /REBOOTOK $3 $0\GvimExt32\gvimext.dll
-!ifdef HAVE_NLS
-	GetTempFileName $3 $0\GvimExt32
-	File /oname=$3 ${GETTEXT}\gettext32\libintl-8.dll
-	Rename /REBOOTOK $3 $0\GvimExt32\libintl-8.dll
-	GetTempFileName $3 $0\GvimExt32
-	File /oname=$3 ${GETTEXT}\gettext32\libiconv-2.dll
-	Rename /REBOOTOK $3 $0\GvimExt32\libiconv-2.dll
-	GetTempFileName $3 $0\GvimExt32
-	File /oname=$3 ${GETTEXT}\gettext32\libgcc_s_sjlj-1.dll
-	Rename /REBOOTOK $3 $0\GvimExt32\libgcc_s_sjlj-1.dll
-!endif
+	GetTempFileName $3 $0
+	${If} ${RunningX64}
+	  File /oname=$3 ${VIMSRC}\GvimExt\gvimext64.dll
+	${Else}
+	  File /oname=$3 ${VIMSRC}\GvimExt\gvimext.dll
+	${EndIf}
+	Rename /REBOOTOK $3 $0\gvimext.dll

-	GvimExt32Done:
+	GvimExtDone:
 	SetOverwrite lastused

 	# We don't have a separate entry for the "Open With..." menu, assume
@@ -417,7 +342,7 @@ Section "Add an Edit-with-Vim context menu entry"
 SectionEnd

 ##########################################################
-Section "Create a _vimrc if it doesn't exist" sec_vimrc_id
+Section "Create a _vimrc if it doesn't exist"
 	SectionIn 1 3

 	StrCpy $1 "$1 -create-vimrc"
@@ -457,10 +382,9 @@ SectionEnd
 		File ${VIMRT}\keymap\README.txt
 		File ${VIMRT}\keymap\*.vim
 		SetOutPath $0
-		File ${GETTEXT}\gettext32\libintl-8.dll
-		File ${GETTEXT}\gettext32\libiconv-2.dll
-		#File /nonfatal ${VIMRT}\libwinpthread-1.dll
-		File /nonfatal ${GETTEXT}\gettext32\libgcc_s_sjlj-1.dll
+		File ${VIMRT}\libintl-8.dll
+		File ${VIMRT}\libiconv-2.dll
+		File /nonfatal ${VIMRT}\libwinpthread-1.dll
 	SectionEnd
 !endif

@@ -475,43 +399,6 @@ Section -post
 	BringToFront
 SectionEnd

-##########################################################
-Function SetCustom
-	# Display the InstallOptions dialog
-
-	# Check if a _vimrc should be created
-	SectionGetFlags ${sec_vimrc_id} $3
-	IntOp $3 $3 & 1
-	StrCmp $3 "1" +2 0
-	  Abort
-
-	InstallOptions::dialog "$PLUGINSDIR\vimrc.ini"
-	Pop $3
-FunctionEnd
-
-Function ValidateCustom
-	ReadINIStr $3 "$PLUGINSDIR\vimrc.ini" "Field 2" "State"
-	StrCmp $3 "1" 0 +3
-	  StrCpy $1 "$1 -vimrc-remap no"
-	  Goto behave
-
-	  StrCpy $1 "$1 -vimrc-remap win"
-
-	behave:
-	ReadINIStr $3 "$PLUGINSDIR\vimrc.ini" "Field 5" "State"
-	StrCmp $3 "1" 0 +3
-	  StrCpy $1 "$1 -vimrc-behave unix"
-	  Goto done
-
-	ReadINIStr $3 "$PLUGINSDIR\vimrc.ini" "Field 6" "State"
-	StrCmp $3 "1" 0 +3
-	  StrCpy $1 "$1 -vimrc-behave mswin"
-	  Goto done
-
-	  StrCpy $1 "$1 -vimrc-behave default"
-	done:
-FunctionEnd
-
 ##########################################################
 Section Uninstall
 	# Apparently $INSTDIR is set to the directory where the uninstaller is
@@ -537,11 +424,6 @@ Section Uninstall
 	   $\nIt contains the Vim executables and runtime files." IDNO NoRemoveExes

 	Delete /REBOOTOK $0\*.dll
-	Delete /REBOOTOK $0\GvimExt32\*.dll
-	${If} ${RunningX64}
-	  Delete /REBOOTOK $0\GvimExt64\*.dll
-	${EndIf}
-
 	ClearErrors
 	# Remove everything but *.dll files.  Avoids that
 	# a lot remains when gvimext.dll cannot be deleted.
@@ -1,68 +0,0 @@
-[Settings]
-NumFields=7
-
-[Field 1]
-Type=GroupBox
-Left=0
-Right=-1
-Top=0
-Bottom=53
-Text=" Key remapping "
-
-[Field 2]
-Type=radiobutton
-Text=Do not remap keys for Windows behavior (Default)
-Left=10
-Right=-10
-Top=17
-Bottom=25
-State=1
-Flags=GROUP
-
-[Field 3]
-Type=radiobutton
-Text=Remap a few keys for Windows behavior (<C-V>, <C-C>, <C-A>, <C-S>, <C-F>, etc)
-Left=10
-Right=-10
-Top=30
-Bottom=47
-State=0
-Flags=NOTABSTOP
-
-[Field 4]
-Type=GroupBox
-Left=0
-Right=-1
-Top=55
-Bottom=-5
-Text=" Mouse behavior "
-
-[Field 5]
-Type=radiobutton
-Text=Right button extends selection, left button starts visual mode (Unix)
-Left=10
-Right=-5
-Top=72
-Bottom=80
-State=0
-Flags=GROUP
-
-[Field 6]
-Type=radiobutton
-Text=Right button has a popup menu, left button starts select mode (Windows)
-Left=10
-Right=-5
-Top=85
-Bottom=93
-State=0
-Flags=NOTABSTOP
-
-[Field 7]
-Type=radiobutton
-Text=Right button has a popup menu, left button starts visual mode (Default)
-Left=10
-Right=-5
-Top=98
-Bottom=106
-State=1
-Flags=NOTABSTOP
@@ -2,13 +2,12 @@
 "  Description: Perform Ada specific completion & tagging.
 "     Language: Ada (2005)
 "	   $Id: ada.vim 887 2008-07-08 14:29:01Z krischik $
-"   Maintainer: Mathias Brousset <mathiasb17@gmail.com>
-"		Martin Krischik <krischik@users.sourceforge.net>
+"   Maintainer: Martin Krischik <krischik@users.sourceforge.net>
 "		Taylor Venable <taylor@metasyntax.net>
 "		Neil Bird <neil@fnxweb.com>
 "		Ned Okie <nokie@radford.edu>
 "      $Author: krischik $
-"	 $Date: 2017-01-31 20:20:05 +0200 (Mon, 01 Jan 2017) $
+"	 $Date: 2008-07-08 16:29:01 +0200 (Di, 08 Jul 2008) $
 "      Version: 4.6
 "    $Revision: 887 $
 "     $HeadURL: https://gnuada.svn.sourceforge.net/svnroot/gnuada/trunk/tools/vim/autoload/ada.vim $
@@ -24,7 +23,6 @@
 "	        09.05.2007 MK Session just won't work no matter how much
 "			      tweaking is done
 "		19.09.2007 NO still some mapleader problems
-"		31.01.2017 MB fix more mapleader problems
 "    Help Page: ft-ada-functions
 "------------------------------------------------------------------------------

@@ -449,7 +447,7 @@ function ada#Switch_Session (New_Session)

      if a:New_Session != v:this_session
 	 "
-	 "  We actually got a new session - otherwise there
+	 "  We actualy got a new session - otherwise there
 	 "  is nothing to do.
 	 "
 	 if strlen (v:this_session) > 0
@@ -587,11 +585,11 @@ function ada#Map_Menu (Text, Keys, Command)
 	\ " :"	  . a:Command . "<CR>"
      execute
 	\ "nnoremap <buffer>" .
-	\ " <Leader>a" . a:Keys .
+	\ escape(l:leader . "a" . a:Keys , '\') .
 	\" :" . a:Command
      execute
 	\ "inoremap <buffer>" .
-	\ " <Leader>a" . a:Keys .
+	\ escape(l:leader . "a" . a:Keys , '\') .
 	\" <C-O>:" . a:Command
   endif
   return
@@ -1,184 +0,0 @@
-" Language:           ConTeXt typesetting engine
-" Maintainer:         Nicola Vitacolonna <nvitacolonna@gmail.com>
-" Latest Revision:    2016 Oct 21
-
-let s:keepcpo= &cpo
-set cpo&vim
-
-" Helper functions {{{
-function! s:context_echo(message, mode)
-  redraw
-  echo "\r"
-  execute 'echohl' a:mode
-  echomsg '[ConTeXt]' a:message
-  echohl None
-endf
-
-function! s:sh()
-  return has('win32') || has('win64') || has('win16') || has('win95')
-        \ ? ['cmd.exe', '/C']
-        \ : ['/bin/sh', '-c']
-endfunction
-
-" For backward compatibility
-if exists('*win_getid')
-
-  function! s:win_getid()
-    return win_getid()
-  endf
-
-  function! s:win_id2win(winid)
-    return win_id2win(a:winid)
-  endf
-
-else
-
-  function! s:win_getid()
-    return winnr()
-  endf
-
-  function! s:win_id2win(winnr)
-    return a:winnr
-  endf
-
-endif
-" }}}
-
-" ConTeXt jobs {{{
-if has('job')
-
-  let g:context_jobs = []
-
-  " Print the status of ConTeXt jobs
-  function! context#job_status()
-    let l:jobs = filter(g:context_jobs, 'job_status(v:val) == "run"')
-    let l:n = len(l:jobs)
-    call s:context_echo(
-          \ 'There '.(l:n == 1 ? 'is' : 'are').' '.(l:n == 0 ? 'no' : l:n)
-          \ .' job'.(l:n == 1 ? '' : 's').' running'
-          \ .(l:n == 0 ? '.' : ' (' . join(l:jobs, ', ').').'),
-          \ 'ModeMsg')
-  endfunction
-
-  " Stop all ConTeXt jobs
-  function! context#stop_jobs()
-    let l:jobs = filter(g:context_jobs, 'job_status(v:val) == "run"')
-    for job in l:jobs
-      call job_stop(job)
-    endfor
-    sleep 1
-    let l:tmp = []
-    for job in l:jobs
-      if job_status(job) == "run"
-        call add(l:tmp, job)
-      endif
-    endfor
-    let g:context_jobs = l:tmp
-    if empty(g:context_jobs)
-      call s:context_echo('Done. No jobs running.', 'ModeMsg')
-    else
-      call s:context_echo('There are still some jobs running. Please try again.', 'WarningMsg')
-    endif
-  endfunction
-
-  function! context#callback(path, job, status)
-    if index(g:context_jobs, a:job) != -1 && job_status(a:job) != 'run' " just in case
-      call remove(g:context_jobs, index(g:context_jobs, a:job))
-    endif
-    call s:callback(a:path, a:job, a:status)
-  endfunction
-
-  function! context#close_cb(channel)
-    call job_status(ch_getjob(a:channel)) " Trigger exit_cb's callback for faster feedback
-  endfunction
-
-  function! s:typeset(path)
-    call add(g:context_jobs,
-          \ job_start(add(s:sh(), context#command() . ' ' . shellescape(fnamemodify(a:path, ":t"))), {
-          \   'close_cb' : 'context#close_cb',
-          \   'exit_cb'  : function(get(b:, 'context_callback', get(g:, 'context_callback', 'context#callback')),
-          \                         [a:path]),
-          \   'in_io'    : 'null'
-          \ }))
-  endfunction
-
-else " No jobs
-
-  function! context#job_status()
-    call s:context_echo('Not implemented', 'WarningMsg')
-  endfunction!
-
-  function! context#stop_jobs()
-    call s:context_echo('Not implemented', 'WarningMsg')
-  endfunction
-
-  function! context#callback(path, job, status)
-    call s:callback(a:path, a:job, a:status)
-  endfunction
-
-  function! s:typeset(path)
-    execute '!' . context#command() . ' ' . shellescape(fnamemodify(a:path, ":t"))
-    call call(get(b:, 'context_callback', get(g:, 'context_callback', 'context#callback')),
-          \ [a:path, 0, v:shell_error])
-  endfunction
-
-endif " has('job')
-
-function! s:callback(path, job, status) abort
-  if a:status < 0 " Assume the job was terminated
-    return
-  endif
-  " Get info about the current window
-  let l:winid = s:win_getid()             " Save window id
-  let l:efm = &l:errorformat              " Save local errorformat
-  let l:cwd = fnamemodify(getcwd(), ":p") " Save local working directory
-  " Set errorformat to parse ConTeXt errors
-  execute 'setl efm=' . escape(b:context_errorformat, ' ')
-  try " Set cwd to expand error file correctly
-    execute 'lcd' fnameescape(fnamemodify(a:path, ':h'))
-  catch /.*/
-    execute 'setl efm=' . escape(l:efm, ' ')
-    throw v:exception
-  endtry
-  try
-    execute 'cgetfile' fnameescape(fnamemodify(a:path, ':r') . '.log')
-    botright cwindow
-  finally " Restore cwd and errorformat
-    execute s:win_id2win(l:winid) . 'wincmd w'
-    execute 'lcd ' . fnameescape(l:cwd)
-    execute 'setl efm=' . escape(l:efm, ' ')
-  endtry
-  if a:status == 0
-    call s:context_echo('Success!', 'ModeMsg')
-  else
-    call s:context_echo('There are errors. ', 'ErrorMsg')
-  endif
-endfunction
-
-function! context#command()
-  return get(b:, 'context_mtxrun', get(g:, 'context_mtxrun', 'mtxrun'))
-        \ . ' --script context --autogenerate --nonstopmode'
-        \ . ' --synctex=' . (get(b:, 'context_synctex', get(g:, 'context_synctex', 0)) ? '1' : '0')
-        \ . ' ' . get(b:, 'context_extra_options', get(g:, 'context_extra_options', ''))
-endfunction
-
-" Accepts an optional path (useful for big projects, when the file you are
-" editing is not the project's root document). If no argument is given, uses
-" the path of the current buffer.
-function! context#typeset(...) abort
-  let l:path = fnamemodify(strlen(a:000[0]) > 0 ? a:1 : expand("%"), ":p")
-  let l:cwd = fnamemodify(getcwd(), ":p") " Save local working directory
-  call s:context_echo('Typesetting...',  'ModeMsg')
-  execute 'lcd' fnameescape(fnamemodify(l:path, ":h"))
-  try
-    call s:typeset(l:path)
-  finally " Restore local working directory
-    execute 'lcd ' . fnameescape(l:cwd)
-  endtry
-endfunction!
-"}}}
-
-let &cpo = s:keepcpo
-unlet s:keepcpo
-
-" vim: sw=2 fdm=marker
@@ -1,25 +0,0 @@
-" Language:           ConTeXt typesetting engine
-" Maintainer:         Nicola Vitacolonna <nvitacolonna@gmail.com>
-" Latest Revision:    2016 Oct 15
-
-let s:keepcpo= &cpo
-set cpo&vim
-
-" Complete keywords in MetaPost blocks
-function! contextcomplete#Complete(findstart, base)
-  if a:findstart == 1
-    if len(synstack(line('.'), 1)) > 0 &&
-          \ synIDattr(synstack(line('.'), 1)[0], "name") ==# 'contextMPGraphic'
-      return syntaxcomplete#Complete(a:findstart, a:base)
-    else
-      return -3
-    endif
-  else
-    return syntaxcomplete#Complete(a:findstart, a:base)
-  endif
-endfunction
-
-let &cpo = s:keepcpo
-unlet s:keepcpo
-
-" vim: sw=2 fdm=marker
@@ -1,745 +0,0 @@
-" Vim functions for file type detection
-"
-" Maintainer:	Bram Moolenaar <Bram@vim.org>
-" Last Change:	2017 Dec 05
-
-" These functions are moved here from runtime/filetype.vim to make startup
-" faster.
-
-" Line continuation is used here, remove 'C' from 'cpoptions'
-let s:cpo_save = &cpo
-set cpo&vim
-
-func dist#ft#Check_inp()
-  if getline(1) =~ '^\*'
-    setf abaqus
-  else
-    let n = 1
-    if line("$") > 500
-      let nmax = 500
-    else
-      let nmax = line("$")
-    endif
-    while n <= nmax
-      if getline(n) =~? "^header surface data"
-	setf trasys
-	break
-      endif
-      let n = n + 1
-    endwhile
-  endif
-endfunc
-
-" This function checks for the kind of assembly that is wanted by the user, or
-" can be detected from the first five lines of the file.
-func dist#ft#FTasm()
-  " make sure b:asmsyntax exists
-  if !exists("b:asmsyntax")
-    let b:asmsyntax = ""
-  endif
-
-  if b:asmsyntax == ""
-    call dist#ft#FTasmsyntax()
-  endif
-
-  " if b:asmsyntax still isn't set, default to asmsyntax or GNU
-  if b:asmsyntax == ""
-    if exists("g:asmsyntax")
-      let b:asmsyntax = g:asmsyntax
-    else
-      let b:asmsyntax = "asm"
-    endif
-  endif
-
-  exe "setf " . fnameescape(b:asmsyntax)
-endfunc
-
-func dist#ft#FTasmsyntax()
-  " see if file contains any asmsyntax=foo overrides. If so, change
-  " b:asmsyntax appropriately
-  let head = " ".getline(1)." ".getline(2)." ".getline(3)." ".getline(4).
-	\" ".getline(5)." "
-  let match = matchstr(head, '\sasmsyntax=\zs[a-zA-Z0-9]\+\ze\s')
-  if match != ''
-    let b:asmsyntax = match
-  elseif ((head =~? '\.title') || (head =~? '\.ident') || (head =~? '\.macro') || (head =~? '\.subtitle') || (head =~? '\.library'))
-    let b:asmsyntax = "vmasm"
-  endif
-endfunc
-
-" Check if one of the first five lines contains "VB_Name".  In that case it is
-" probably a Visual Basic file.  Otherwise it's assumed to be "alt" filetype.
-func dist#ft#FTVB(alt)
-  if getline(1).getline(2).getline(3).getline(4).getline(5) =~? 'VB_Name\|Begin VB\.\(Form\|MDIForm\|UserControl\)'
-    setf vb
-  else
-    exe "setf " . a:alt
-  endif
-endfunc
-
-func dist#ft#FTbtm()
-  if exists("g:dosbatch_syntax_for_btm") && g:dosbatch_syntax_for_btm
-    setf dosbatch
-  else
-    setf btm
-  endif
-endfunc
-
-func dist#ft#BindzoneCheck(default)
-  if getline(1).getline(2).getline(3).getline(4) =~ '^; <<>> DiG [0-9.]\+.* <<>>\|$ORIGIN\|$TTL\|IN\s\+SOA'
-    setf bindzone
-  elseif a:default != ''
-    exe 'setf ' . a:default
-  endif
-endfunc
-
-func dist#ft#FTlpc()
-  if exists("g:lpc_syntax_for_c")
-    let lnum = 1
-    while lnum <= 12
-      if getline(lnum) =~# '^\(//\|inherit\|private\|protected\|nosave\|string\|object\|mapping\|mixed\)'
-	setf lpc
-	return
-      endif
-      let lnum = lnum + 1
-    endwhile
-  endif
-  setf c
-endfunc
-
-func dist#ft#FTheader()
-  if match(getline(1, min([line("$"), 200])), '^@\(interface\|end\|class\)') > -1
-    if exists("g:c_syntax_for_h")
-      setf objc
-    else
-      setf objcpp
-    endif
-  elseif exists("g:c_syntax_for_h")
-    setf c
-  elseif exists("g:ch_syntax_for_h")
-    setf ch
-  else
-    setf cpp
-  endif
-endfunc
-
-" This function checks if one of the first ten lines start with a '@'.  In
-" that case it is probably a change file.
-" If the first line starts with # or ! it's probably a ch file.
-" If a line has "main", "include", "//" ir "/*" it's probably ch.
-" Otherwise CHILL is assumed.
-func dist#ft#FTchange()
-  let lnum = 1
-  while lnum <= 10
-    if getline(lnum)[0] == '@'
-      setf change
-      return
-    endif
-    if lnum == 1 && (getline(1)[0] == '#' || getline(1)[0] == '!')
-      setf ch
-      return
-    endif
-    if getline(lnum) =~ "MODULE"
-      setf chill
-      return
-    endif
-    if getline(lnum) =~ 'main\s*(\|#\s*include\|//'
-      setf ch
-      return
-    endif
-    let lnum = lnum + 1
-  endwhile
-  setf chill
-endfunc
-
-func dist#ft#FTent()
-  " This function checks for valid cl syntax in the first five lines.
-  " Look for either an opening comment, '#', or a block start, '{".
-  " If not found, assume SGML.
-  let lnum = 1
-  while lnum < 6
-    let line = getline(lnum)
-    if line =~ '^\s*[#{]'
-      setf cl
-      return
-    elseif line !~ '^\s*$'
-      " Not a blank line, not a comment, and not a block start,
-      " so doesn't look like valid cl code.
-      break
-    endif
-    let lnum = lnum + 1
-  endw
-  setf dtd
-endfunc
-
-func dist#ft#EuphoriaCheck()
-  if exists('g:filetype_euphoria')
-    exe 'setf ' . g:filetype_euphoria
-  else
-    setf euphoria3
-  endif
-endfunc
-
-func dist#ft#DtraceCheck()
-  let lines = getline(1, min([line("$"), 100]))
-  if match(lines, '^module\>\|^import\>') > -1
-    " D files often start with a module and/or import statement.
-    setf d
-  elseif match(lines, '^#!\S\+dtrace\|#pragma\s\+D\s\+option\|:\S\{-}:\S\{-}:') > -1
-    setf dtrace
-  else
-    setf d
-  endif
-endfunc
-
-func dist#ft#FTe()
-  if exists('g:filetype_euphoria')
-    exe 'setf ' . g:filetype_euphoria
-  else
-    let n = 1
-    while n < 100 && n < line("$")
-      if getline(n) =~ "^\\s*\\(<'\\|'>\\)\\s*$"
-	setf specman
-	return
-      endif
-      let n = n + 1
-    endwhile
-    setf eiffel
-  endif
-endfunc
-
-" Distinguish between HTML, XHTML and Django
-func dist#ft#FThtml()
-  let n = 1
-  while n < 10 && n < line("$")
-    if getline(n) =~ '\<DTD\s\+XHTML\s'
-      setf xhtml
-      return
-    endif
-    if getline(n) =~ '{%\s*\(extends\|block\|load\)\>\|{#\s\+'
-      setf htmldjango
-      return
-    endif
-    let n = n + 1
-  endwhile
-  setf html
-endfunc
-
-" Distinguish between standard IDL and MS-IDL
-func dist#ft#FTidl()
-  let n = 1
-  while n < 50 && n < line("$")
-    if getline(n) =~ '^\s*import\s\+"\(unknwn\|objidl\)\.idl"'
-      setf msidl
-      return
-    endif
-    let n = n + 1
-  endwhile
-  setf idl
-endfunc
-
-" Distinguish between "default" and Cproto prototype file. */
-func dist#ft#ProtoCheck(default)
-  " Cproto files have a comment in the first line and a function prototype in
-  " the second line, it always ends in ";".  Indent files may also have
-  " comments, thus we can't match comments to see the difference.
-  " IDL files can have a single ';' in the second line, require at least one
-  " chacter before the ';'.
-  if getline(2) =~ '.;$'
-    setf cpp
-  else
-    exe 'setf ' . a:default
-  endif
-endfunc
-
-func dist#ft#FTm()
-  let n = 1
-  let saw_comment = 0 " Whether we've seen a multiline comment leader.
-  while n < 100
-    let line = getline(n)
-    if line =~ '^\s*/\*'
-      " /* ... */ is a comment in Objective C and Murphi, so we can't conclude
-      " it's either of them yet, but track this as a hint in case we don't see
-      " anything more definitive.
-      let saw_comment = 1
-    endif
-    if line =~ '^\s*\(#\s*\(include\|import\)\>\|@import\>\|//\)'
-      setf objc
-      return
-    endif
-    if line =~ '^\s*%'
-      setf matlab
-      return
-    endif
-    if line =~ '^\s*(\*'
-      setf mma
-      return
-    endif
-    if line =~ '^\c\s*\(\(type\|var\)\>\|--\)'
-      setf murphi
-      return
-    endif
-    let n = n + 1
-  endwhile
-
-  if saw_comment
-    " We didn't see anything definitive, but this looks like either Objective C
-    " or Murphi based on the comment leader. Assume the former as it is more
-    " common.
-    setf objc
-  elseif exists("g:filetype_m")
-    " Use user specified default filetype for .m
-    exe "setf " . g:filetype_m
-  else
-    " Default is matlab
-    setf matlab
-  endif
-endfunc
-
-func dist#ft#FTmms()
-  let n = 1
-  while n < 10
-    let line = getline(n)
-    if line =~ '^\s*\(%\|//\)' || line =~ '^\*'
-      setf mmix
-      return
-    endif
-    if line =~ '^\s*#'
-      setf make
-      return
-    endif
-    let n = n + 1
-  endwhile
-  setf mmix
-endfunc
-
-" This function checks if one of the first five lines start with a dot.  In
-" that case it is probably an nroff file: 'filetype' is set and 1 is returned.
-func dist#ft#FTnroff()
-  if getline(1)[0] . getline(2)[0] . getline(3)[0] . getline(4)[0] . getline(5)[0] =~ '\.'
-    setf nroff
-    return 1
-  endif
-  return 0
-endfunc
-
-func dist#ft#FTmm()
-  let n = 1
-  while n < 10
-    let line = getline(n)
-    if line =~ '^\s*\(#\s*\(include\|import\)\>\|@import\>\|/\*\)'
-      setf objcpp
-      return
-    endif
-    let n = n + 1
-  endwhile
-  setf nroff
-endfunc
-
-func dist#ft#FTpl()
-  if exists("g:filetype_pl")
-    exe "setf " . g:filetype_pl
-  else
-    " recognize Prolog by specific text in the first non-empty line
-    " require a blank after the '%' because Perl uses "%list" and "%translate"
-    let l = getline(nextnonblank(1))
-    if l =~ '\<prolog\>' || l =~ '^\s*\(%\+\(\s\|$\)\|/\*\)' || l =~ ':-'
-      setf prolog
-    else
-      setf perl
-    endif
-  endif
-endfunc
-
-func dist#ft#FTinc()
-  if exists("g:filetype_inc")
-    exe "setf " . g:filetype_inc
-  else
-    let lines = getline(1).getline(2).getline(3)
-    if lines =~? "perlscript"
-      setf aspperl
-    elseif lines =~ "<%"
-      setf aspvbs
-    elseif lines =~ "<?"
-      setf php
-    else
-      call dist#ft#FTasmsyntax()
-      if exists("b:asmsyntax")
-	exe "setf " . fnameescape(b:asmsyntax)
-      else
-	setf pov
-      endif
-    endif
-  endif
-endfunc
-
-func dist#ft#FTprogress_cweb()
-  if exists("g:filetype_w")
-    exe "setf " . g:filetype_w
-    return
-  endif
-  if getline(1) =~ '&ANALYZE' || getline(3) =~ '&GLOBAL-DEFINE'
-    setf progress
-  else
-    setf cweb
-  endif
-endfunc
-
-func dist#ft#FTprogress_asm()
-  if exists("g:filetype_i")
-    exe "setf " . g:filetype_i
-    return
-  endif
-  " This function checks for an assembly comment the first ten lines.
-  " If not found, assume Progress.
-  let lnum = 1
-  while lnum <= 10 && lnum < line('$')
-    let line = getline(lnum)
-    if line =~ '^\s*;' || line =~ '^\*'
-      call dist#ft#FTasm()
-      return
-    elseif line !~ '^\s*$' || line =~ '^/\*'
-      " Not an empty line: Doesn't look like valid assembly code.
-      " Or it looks like a Progress /* comment
-      break
-    endif
-    let lnum = lnum + 1
-  endw
-  setf progress
-endfunc
-
-func dist#ft#FTprogress_pascal()
-  if exists("g:filetype_p")
-    exe "setf " . g:filetype_p
-    return
-  endif
-  " This function checks for valid Pascal syntax in the first ten lines.
-  " Look for either an opening comment or a program start.
-  " If not found, assume Progress.
-  let lnum = 1
-  while lnum <= 10 && lnum < line('$')
-    let line = getline(lnum)
-    if line =~ '^\s*\(program\|unit\|procedure\|function\|const\|type\|var\)\>'
-	\ || line =~ '^\s*{' || line =~ '^\s*(\*'
-      setf pascal
-      return
-    elseif line !~ '^\s*$' || line =~ '^/\*'
-      " Not an empty line: Doesn't look like valid Pascal code.
-      " Or it looks like a Progress /* comment
-      break
-    endif
-    let lnum = lnum + 1
-  endw
-  setf progress
-endfunc
-
-func dist#ft#FTr()
-  let max = line("$") > 50 ? 50 : line("$")
-
-  for n in range(1, max)
-    " Rebol is easy to recognize, check for that first
-    if getline(n) =~? '\<REBOL\>'
-      setf rebol
-      return
-    endif
-  endfor
-
-  for n in range(1, max)
-    " R has # comments
-    if getline(n) =~ '^\s*#'
-      setf r
-      return
-    endif
-    " Rexx has /* comments */
-    if getline(n) =~ '^\s*/\*'
-      setf rexx
-      return
-    endif
-  endfor
-
-  " Nothing recognized, use user default or assume Rexx
-  if exists("g:filetype_r")
-    exe "setf " . g:filetype_r
-  else
-    " Rexx used to be the default, but R appears to be much more popular.
-    setf r
-  endif
-endfunc
-
-func dist#ft#McSetf()
-  " Rely on the file to start with a comment.
-  " MS message text files use ';', Sendmail files use '#' or 'dnl'
-  for lnum in range(1, min([line("$"), 20]))
-    let line = getline(lnum)
-    if line =~ '^\s*\(#\|dnl\)'
-      setf m4  " Sendmail .mc file
-      return
-    elseif line =~ '^\s*;'
-      setf msmessages  " MS Message text file
-      return
-    endif
-  endfor
-  setf m4  " Default: Sendmail .mc file
-endfunc
-
-" Called from filetype.vim and scripts.vim.
-func dist#ft#SetFileTypeSH(name)
-  if expand("<amatch>") =~ g:ft_ignore_pat
-    return
-  endif
-  if a:name =~ '\<csh\>'
-    " Some .sh scripts contain #!/bin/csh.
-    call dist#ft#SetFileTypeShell("csh")
-    return
-  elseif a:name =~ '\<tcsh\>'
-    " Some .sh scripts contain #!/bin/tcsh.
-    call dist#ft#SetFileTypeShell("tcsh")
-    return
-  elseif a:name =~ '\<zsh\>'
-    " Some .sh scripts contain #!/bin/zsh.
-    call dist#ft#SetFileTypeShell("zsh")
-    return
-  elseif a:name =~ '\<ksh\>'
-    let b:is_kornshell = 1
-    if exists("b:is_bash")
-      unlet b:is_bash
-    endif
-    if exists("b:is_sh")
-      unlet b:is_sh
-    endif
-  elseif exists("g:bash_is_sh") || a:name =~ '\<bash\>' || a:name =~ '\<bash2\>'
-    let b:is_bash = 1
-    if exists("b:is_kornshell")
-      unlet b:is_kornshell
-    endif
-    if exists("b:is_sh")
-      unlet b:is_sh
-    endif
-  elseif a:name =~ '\<sh\>'
-    let b:is_sh = 1
-    if exists("b:is_kornshell")
-      unlet b:is_kornshell
-    endif
-    if exists("b:is_bash")
-      unlet b:is_bash
-    endif
-  endif
-  call dist#ft#SetFileTypeShell("sh")
-endfunc
-
-" For shell-like file types, check for an "exec" command hidden in a comment,
-" as used for Tcl.
-" Also called from scripts.vim, thus can't be local to this script.
-func dist#ft#SetFileTypeShell(name)
-  if expand("<amatch>") =~ g:ft_ignore_pat
-    return
-  endif
-  let l = 2
-  while l < 20 && l < line("$") && getline(l) =~ '^\s*\(#\|$\)'
-    " Skip empty and comment lines.
-    let l = l + 1
-  endwhile
-  if l < line("$") && getline(l) =~ '\s*exec\s' && getline(l - 1) =~ '^\s*#.*\\$'
-    " Found an "exec" line after a comment with continuation
-    let n = substitute(getline(l),'\s*exec\s\+\([^ ]*/\)\=', '', '')
-    if n =~ '\<tclsh\|\<wish'
-      setf tcl
-      return
-    endif
-  endif
-  exe "setf " . a:name
-endfunc
-
-func dist#ft#CSH()
-  if exists("g:filetype_csh")
-    call dist#ft#SetFileTypeShell(g:filetype_csh)
-  elseif &shell =~ "tcsh"
-    call dist#ft#SetFileTypeShell("tcsh")
-  else
-    call dist#ft#SetFileTypeShell("csh")
-  endif
-endfunc
-
-let s:ft_rules_udev_rules_pattern = '^\s*\cudev_rules\s*=\s*"\([^"]\{-1,}\)/*".*'
-func dist#ft#FTRules()
-  let path = expand('<amatch>:p')
-  if path =~ '^/\(etc/udev/\%(rules\.d/\)\=.*\.rules\|lib/udev/\%(rules\.d/\)\=.*\.rules\)$'
-    setf udevrules
-    return
-  endif
-  if path =~ '^/etc/ufw/'
-    setf conf  " Better than hog
-    return
-  endif
-  if path =~ '^/\(etc\|usr/share\)/polkit-1/rules\.d'
-    setf javascript
-    return
-  endif
-  try
-    let config_lines = readfile('/etc/udev/udev.conf')
-  catch /^Vim\%((\a\+)\)\=:E484/
-    setf hog
-    return
-  endtry
-  let dir = expand('<amatch>:p:h')
-  for line in config_lines
-    if line =~ s:ft_rules_udev_rules_pattern
-      let udev_rules = substitute(line, s:ft_rules_udev_rules_pattern, '\1', "")
-      if dir == udev_rules
-	setf udevrules
-      endif
-      break
-    endif
-  endfor
-  setf hog
-endfunc
-
-func dist#ft#SQL()
-  if exists("g:filetype_sql")
-    exe "setf " . g:filetype_sql
-  else
-    setf sql
-  endif
-endfunc
-
-" If the file has an extension of 't' and is in a directory 't' or 'xt' then
-" it is almost certainly a Perl test file.
-" If the first line starts with '#' and contains 'perl' it's probably a Perl
-" file.
-" (Slow test) If a file contains a 'use' statement then it is almost certainly
-" a Perl file.
-func dist#ft#FTperl()
-  let dirname = expand("%:p:h:t")
-  if expand("%:e") == 't' && (dirname == 't' || dirname == 'xt')
-    setf perl
-    return 1
-  endif
-  if getline(1)[0] == '#' && getline(1) =~ 'perl'
-    setf perl
-    return 1
-  endif
-  let save_cursor = getpos('.')
-  call cursor(1,1)
-  let has_use = search('^use\s\s*\k', 'c', 30)
-  call setpos('.', save_cursor)
-  if has_use
-    setf perl
-    return 1
-  endif
-  return 0
-endfunc
-
-" Choose context, plaintex, or tex (LaTeX) based on these rules:
-" 1. Check the first line of the file for "%&<format>".
-" 2. Check the first 1000 non-comment lines for LaTeX or ConTeXt keywords.
-" 3. Default to "latex" or to g:tex_flavor, can be set in user's vimrc.
-func dist#ft#FTtex()
-  let firstline = getline(1)
-  if firstline =~ '^%&\s*\a\+'
-    let format = tolower(matchstr(firstline, '\a\+'))
-    let format = substitute(format, 'pdf', '', '')
-    if format == 'tex'
-      let format = 'latex'
-    elseif format == 'plaintex'
-      let format = 'plain'
-    endif
-  elseif expand('%') =~ 'tex/context/.*/.*.tex'
-    let format = 'context'
-  else
-    " Default value, may be changed later:
-    let format = exists("g:tex_flavor") ? g:tex_flavor : 'plain'
-    " Save position, go to the top of the file, find first non-comment line.
-    let save_cursor = getpos('.')
-    call cursor(1,1)
-    let firstNC = search('^\s*[^[:space:]%]', 'c', 1000)
-    if firstNC " Check the next thousand lines for a LaTeX or ConTeXt keyword.
-      let lpat = 'documentclass\>\|usepackage\>\|begin{\|newcommand\>\|renewcommand\>'
-      let cpat = 'start\a\+\|setup\a\+\|usemodule\|enablemode\|enableregime\|setvariables\|useencoding\|usesymbols\|stelle\a\+\|verwende\a\+\|stel\a\+\|gebruik\a\+\|usa\a\+\|imposta\a\+\|regle\a\+\|utilisemodule\>'
-      let kwline = search('^\s*\\\%(' . lpat . '\)\|^\s*\\\(' . cpat . '\)',
-			      \ 'cnp', firstNC + 1000)
-      if kwline == 1	" lpat matched
-	let format = 'latex'
-      elseif kwline == 2	" cpat matched
-	let format = 'context'
-      endif		" If neither matched, keep default set above.
-      " let lline = search('^\s*\\\%(' . lpat . '\)', 'cn', firstNC + 1000)
-      " let cline = search('^\s*\\\%(' . cpat . '\)', 'cn', firstNC + 1000)
-      " if cline > 0
-      "   let format = 'context'
-      " endif
-      " if lline > 0 && (cline == 0 || cline > lline)
-      "   let format = 'tex'
-      " endif
-    endif " firstNC
-    call setpos('.', save_cursor)
-  endif " firstline =~ '^%&\s*\a\+'
-
-  " Translation from formats to file types.  TODO:  add AMSTeX, RevTex, others?
-  if format == 'plain'
-    setf plaintex
-  elseif format == 'context'
-    setf context
-  else " probably LaTeX
-    setf tex
-  endif
-  return
-endfunc
-
-func dist#ft#FTxml()
-  let n = 1
-  while n < 100 && n < line("$")
-    let line = getline(n)
-    " DocBook 4 or DocBook 5.
-    let is_docbook4 = line =~ '<!DOCTYPE.*DocBook'
-    let is_docbook5 = line =~ ' xmlns="http://docbook.org/ns/docbook"'
-    if is_docbook4 || is_docbook5
-      let b:docbk_type = "xml"
-      if is_docbook5
-	let b:docbk_ver = 5
-      else
-	let b:docbk_ver = 4
-      endif
-      setf docbk
-      return
-    endif
-    if line =~ 'xmlns:xbl="http://www.mozilla.org/xbl"'
-      setf xbl
-      return
-    endif
-    let n += 1
-  endwhile
-  setf xml
-endfunc
-
-func dist#ft#FTy()
-  let n = 1
-  while n < 100 && n < line("$")
-    let line = getline(n)
-    if line =~ '^\s*%'
-      setf yacc
-      return
-    endif
-    if getline(n) =~ '^\s*\(#\|class\>\)' && getline(n) !~ '^\s*#\s*include'
-      setf racc
-      return
-    endif
-    let n = n + 1
-  endwhile
-  setf yacc
-endfunc
-
-func dist#ft#Redif()
-  let lnum = 1
-  while lnum <= 5 && lnum < line('$')
-    if getline(lnum) =~ "^\ctemplate-type:"
-      setf redif
-      return
-    endif
-    let lnum = lnum + 1
-  endwhile
-endfunc
-
-
-" Restore 'cpoptions'
-let &cpo = s:cpo_save
-unlet s:cpo_save
@@ -1,6 +1,6 @@
 " Vim autoload file for editing compressed files.
 " Maintainer: Bram Moolenaar <Bram@vim.org>
-" Last Change: 2016 Sep 28
+" Last Change: 2014 Nov 05

 " These functions are used by the gzip plugin.

@@ -63,9 +63,6 @@ fun gzip#read(cmd)
  " set 'modifiable'
  let ma_save = &ma
  setlocal ma
-  " set 'write'
-  let write_save = &write
-  set write
  " Reset 'foldenable', otherwise line numbers get adjusted.
  if has("folding")
    let fen_save = &fen
@@ -130,7 +127,6 @@ fun gzip#read(cmd)
  let &pm = pm_save
  let &cpo = cpo_save
  let &l:ma = ma_save
-  let &write = write_save
  if has("folding")
    let &l:fen = fen_save
  endif
@@ -1,7 +1,7 @@
 " Vim completion script
 " Language:	Java Script
 " Maintainer:	Mikolaj Machowski ( mikmach AT wp DOT pl )
-" Last Change:	2017 Mar 04
+" Last Change:	2006 Apr 30

 function! javascriptcomplete#CompleteJS(findstart, base)
  if a:findstart
@@ -563,7 +563,7 @@ function! javascriptcomplete#CompleteJS(findstart, base)
 	for i in arguments
 		let g:ia = i
 		let f_elements = matchlist(i, 'function\s\+\(\k\+\)\s*(\(.\{-}\))')
-		if len(f_elements) >= 3
+		if len(f_elements) == 3
 			let b:js_menuinfo[f_elements[1].'('] = f_elements[2]
 		endif
 	endfor
@@ -22,8 +22,8 @@
 if &cp || exists("g:loaded_netrw")
  finish
 endif
-" netrw requires vim having patch 213; netrw will benefit from vim's having patch#656, too
-if v:version < 704 || !has("patch213")
+" netrw requires vim having patch 7.4.213; netrw will benefit from vim's having patch#656, too
+if v:version < 704 || (v:version == 704 && !has("patch213"))
 if !exists("s:needpatch213")
  unsilent echomsg "***sorry*** this version of netrw requires vim v7.4 with patch 213"
 endif
@@ -1,6 +1,6 @@
 " Vim support file to help with paste mappings and menus
 " Maintainer:	Bram Moolenaar <Bram@vim.org>
-" Last Change:	2017 Aug 30
+" Last Change:	2006 Jun 23

 " Define the string to use for items that are present both in Edit, Popup and
 " Toolbar menu.  Also used in mswin.vim and macmap.vim.
@@ -12,7 +12,7 @@
 if has("virtualedit")
  let paste#paste_cmd = {'n': ":call paste#Paste()<CR>"}
  let paste#paste_cmd['v'] = '"-c<Esc>' . paste#paste_cmd['n']
-  let paste#paste_cmd['i'] = "\<c-\>\<c-o>\"+gP"
+  let paste#paste_cmd['i'] = 'x<BS><Esc>' . paste#paste_cmd['n'] . 'gi'

  func! paste#Paste()
    let ove = &ve
@@ -3,7 +3,7 @@
 " Maintainer:	Dávid Szabó ( complex857 AT gmail DOT com )
 " Previous Maintainer:	Mikolaj Machowski ( mikmach AT wp DOT pl )
 " URL: https://github.com/shawncplus/phpcomplete.vim
-" Last Change:  2016 Oct 10
+" Last Change:  2015 Jul 13
 "
 "	OPTIONS:
 "
@@ -195,8 +195,6 @@ function! phpcomplete#CompletePHP(findstart, base) " {{{
 			" }}}
 		elseif context =~? 'implements'
 			return phpcomplete#CompleteClassName(a:base, ['i'], current_namespace, imports)
-		elseif context =~? 'instanceof'
-			return phpcomplete#CompleteClassName(a:base, ['c', 'n'], current_namespace, imports)
 		elseif context =~? 'extends\s\+.\+$' && a:base == ''
 			return ['implements']
 		elseif context =~? 'extends'
@@ -789,8 +787,6 @@ function! phpcomplete#CompleteClassName(base, kinds, current_namespace, imports)

 	if kinds == ['c', 'i']
 		let filterstr = 'v:val =~? "\\(class\\|interface\\)\\s\\+[a-zA-Z_\\x7f-\\xff][a-zA-Z_0-9\\x7f-\\xff]*\\s*"'
-	elseif kinds == ['c', 'n']
-		let filterstr = 'v:val =~? "\\(class\\|namespace\\)\\s\\+[a-zA-Z_\\x7f-\\xff][a-zA-Z_0-9\\x7f-\\xff]*\\s*"'
 	elseif kinds == ['c']
 		let filterstr = 'v:val =~? "class\\s\\+[a-zA-Z_\\x7f-\\xff][a-zA-Z_0-9\\x7f-\\xff]*\\s*"'
 	elseif kinds == ['i']
@@ -1000,7 +996,7 @@ function! phpcomplete#CompleteUserClass(context, base, sccontent, visibility) "
 		let required_modifiers += ['static']
 	endif
 	let all_variable = filter(deepcopy(a:sccontent),
-					\ 'v:val =~ "\\(^\\s*\\(var\\s\\+\\|public\\s\\+\\|protected\\s\\+\\|private\\s\\+\\|final\\s\\+\\|abstract\\s\\+\\|static\\s\\+\\)\\+\\$\\|^\\s*\\(\\/\\|\\*\\)*\\s*@property\\s\\+\\S\\+\\s\\S\\{-}\\s*$\\)"')
+					\ 'v:val =~ "^\\s*\\(var\\s\\+\\|public\\s\\+\\|protected\\s\\+\\|private\\s\\+\\|final\\s\\+\\|abstract\\s\\+\\|static\\s\\+\\)\\+\\$"')

 	let variables = []
 	for i in all_variable
@@ -1164,14 +1160,6 @@ function! phpcomplete#GetTaglist(pattern) " {{{
 	endif

 	let tags = taglist(a:pattern)
-	for tag in tags
-		for prop in keys(tag)
-			if prop == 'cmd' || prop == 'static' || prop == 'kind' || prop == 'builtin'
-				continue
-			endif
-			let tag[prop] = substitute(tag[prop], '\\\\', '\\', 'g')
-		endfor
-	endfor
 	let s:cache_tags[a:pattern] = tags
 	let has_key = has_key(s:cache_tags, a:pattern)
 	let s:cache_tags_checksum = cache_checksum
@@ -1391,7 +1379,7 @@ function! phpcomplete#GetCallChainReturnType(classname_candidate, class_candidat
 			" Get Structured information of all classes and subclasses including namespace and includes
 			" try to find the method's return type in docblock comment
 			for classstructure in classcontents
-				let docblock_target_pattern = 'function\s\+&\?'.method.'\>\|\(public\|private\|protected\|var\).\+\$'.method.'\>\|@property.\+\$'.method.'\>'
+				let docblock_target_pattern = 'function\s\+&\?'.method.'\|\(public\|private\|protected\|var\).\+\$'.method
 				let doc_str = phpcomplete#GetDocBlock(split(classstructure.content, '\n'), docblock_target_pattern)
 				if doc_str != ''
 					break
@@ -1399,17 +1387,8 @@ function! phpcomplete#GetCallChainReturnType(classname_candidate, class_candidat
 			endfor
 			if doc_str != ''
 				let docblock = phpcomplete#ParseDocBlock(doc_str)
-				if has_key(docblock.return, 'type') || has_key(docblock.var, 'type') || len(docblock.properties) > 0
-					let type = has_key(docblock.return, 'type') ? docblock.return.type : has_key(docblock.var, 'type') ? docblock.var.type : ''
-
-					if type == ''
-						for property in docblock.properties
-							if property.description =~? method
-								let type = property.type
-								break
-							endif
-						endfor
-					endif
+				if has_key(docblock.return, 'type') || has_key(docblock.var, 'type')
+					let type = has_key(docblock.return, 'type') ? docblock.return.type : docblock.var.type

 					" there's a namespace in the type, threat the type as FQCN
 					if type =~ '\\'
@@ -1575,9 +1554,6 @@ function! phpcomplete#GetClassName(start_line, context, current_namespace, impor
 	elseif get(methodstack, 0) =~# function_invocation_pattern
 		let function_name = matchstr(methodstack[0], '^\s*\zs'.function_name_pattern)
 		let function_file = phpcomplete#GetFunctionLocation(function_name, a:current_namespace)
-		if function_file == ''
-			let function_file = phpcomplete#GetFunctionLocation(function_name, '\')
-		endif

 		if function_file == 'VIMPHP_BUILTINFUNCTION'
 			" built in function, grab the return type from the info string
@@ -1593,7 +1569,7 @@ function! phpcomplete#GetClassName(start_line, context, current_namespace, impor
 				let [class_candidate_namespace, function_imports] = phpcomplete#GetCurrentNameSpace(file_lines)
 				" try to expand the classname of the returned type with the context got from the function's source file

-				let [classname_candidate, class_candidate_namespace] = phpcomplete#ExpandClassName(classname_candidate, class_candidate_namespace, function_imports)
+				let [classname_candidate, unused] = phpcomplete#ExpandClassName(classname_candidate, class_candidate_namespace, function_imports)
 			endif
 		endif
 		if classname_candidate != ''
@@ -1674,10 +1650,9 @@ function! phpcomplete#GetClassName(start_line, context, current_namespace, impor
 					let sub_methodstack = phpcomplete#GetMethodStack(matchstr(line, '^\s*'.object.'\s*=&\?\s*\s\+\zs.*'))
 					let [classname_candidate, class_candidate_namespace] = phpcomplete#GetCallChainReturnType(
 						\ classname,
-						\ namespace_for_class,
+						\ a:current_namespace,
 						\ a:imports,
 						\ sub_methodstack)
-
 					return (class_candidate_namespace == '\' || class_candidate_namespace == '') ? classname_candidate : class_candidate_namespace.'\'.classname_candidate
 				endif
 			endif
@@ -1808,9 +1783,6 @@ function! phpcomplete#GetClassName(start_line, context, current_namespace, impor
 				let [function_name, function_namespace] = phpcomplete#ExpandClassName(function_name, a:current_namespace, a:imports)

 				let function_file = phpcomplete#GetFunctionLocation(function_name, function_namespace)
-				if function_file == ''
-					let function_file = phpcomplete#GetFunctionLocation(function_name, '\')
-				endif

 				if function_file == 'VIMPHP_BUILTINFUNCTION'
 					" built in function, grab the return type from the info string
@@ -1826,7 +1798,7 @@ function! phpcomplete#GetClassName(start_line, context, current_namespace, impor
 						let classname_candidate = docblock.return.type
 						let [class_candidate_namespace, function_imports] = phpcomplete#GetCurrentNameSpace(file_lines)
 						" try to expand the classname of the returned type with the context got from the function's source file
-						let [classname_candidate, class_candidate_namespace] = phpcomplete#ExpandClassName(classname_candidate, class_candidate_namespace, function_imports)
+						let [classname_candidate, unused] = phpcomplete#ExpandClassName(classname_candidate, class_candidate_namespace, function_imports)
 						break
 					endif
 				endif
@@ -1889,8 +1861,6 @@ function! phpcomplete#GetClassName(start_line, context, current_namespace, impor
 				for tag in tags
 					if tag.kind ==? 'v' && tag.cmd =~? '=\s*new\s\+\zs'.class_name_pattern.'\ze'
 						let classname = matchstr(tag.cmd, '=\s*new\s\+\zs'.class_name_pattern.'\ze')
-						" unescape the classname, it would have "\" doubled since it is an ex command
-						let classname = substitute(classname, '\\\(\_.\)', '\1', 'g')
 						return classname
 					endif
 				endfor
@@ -2107,19 +2077,6 @@ function! phpcomplete#GetClassContentsStructure(file_path, file_lines, class_nam
 	endif
 	call searchpair('{', '', '}', 'W')
 	let class_closing_bracket_line = line('.')
-
-	" Include class docblock
-	let doc_line = cfline - 1
-	if getline(doc_line) =~? '^\s*\*/'
-		while doc_line != 0
-			if getline(doc_line) =~? '^\s*/\*\*'
-				let cfline = doc_line
-				break
-			endif
-			let doc_line -= 1
-		endwhile
-	endif
-
 	let classcontent = join(getline(cfline, class_closing_bracket_line), "\n")

 	let used_traits = []
@@ -2284,19 +2241,8 @@ function! phpcomplete#GetDocBlock(sccontent, search) " {{{
 		let line = a:sccontent[i]
 		" search for a function declaration
 		if line =~? a:search
-			if line =~? '@property'
-				let doc_line = i
-				while doc_line != sccontent_len - 1
-					if a:sccontent[doc_line] =~? '^\s*\*/'
-						let l = doc_line
-						break
-					endif
-					let doc_line += 1
-				endwhile
-			else
-				let l = i - 1
-			endif
-			" start backward search for the comment block
+			let l = i - 1
+			" start backward serch for the comment block
 			while l != 0
 				let line = a:sccontent[l]
 				" if it's a one line docblock like comment and we can just return it right away
@@ -2317,7 +2263,7 @@ function! phpcomplete#GetDocBlock(sccontent, search) " {{{
 				return ''
 			end

-			while l >= 0
+			while l != 0
 				let line = a:sccontent[l]
 				if line =~? '^\s*/\*\*'
 					let comment_start = l
@@ -2351,10 +2297,9 @@ function! phpcomplete#ParseDocBlock(docblock) " {{{
 		\ 'return': {},
 		\ 'throws': [],
 		\ 'var': {},
-		\ 'properties': [],
 		\ }

-	let res.description = substitute(matchstr(a:docblock, '\zs\_.\{-}\ze\(@type\|@var\|@param\|@return\|$\)'), '\(^\_s*\|\_s*$\)', '', 'g')
+	let res.description = substitute(matchstr(a:docblock, '\zs\_.\{-}\ze\(@var\|@param\|@return\|$\)'), '\(^\_s*\|\_s*$\)', '', 'g')
 	let docblock_lines = split(a:docblock, "\n")

 	let param_lines = filter(copy(docblock_lines), 'v:val =~? "^@param"')
@@ -2389,26 +2334,15 @@ function! phpcomplete#ParseDocBlock(docblock) " {{{
 		endif
 	endfor

-	let var_line = filter(copy(docblock_lines), 'v:val =~? "^\\(@var\\|@type\\)"')
+	let var_line = filter(copy(docblock_lines), 'v:val =~? "^@var"')
 	if len(var_line) > 0
-		let var_parts = matchlist(var_line[0], '\(@var\|@type\)\s\+\(\S\+\)\s*\(.*\)')
+		let var_parts = matchlist(var_line[0], '@var\s\+\(\S\+\)\s*\(.*\)')
 		let res['var'] = {
 					\ 'line': var_parts[0],
-					\ 'type': phpcomplete#GetTypeFromDocBlockParam(get(var_parts, 2, '')),
-					\ 'description': get(var_parts, 3, '')}
+					\ 'type': phpcomplete#GetTypeFromDocBlockParam(get(var_parts, 1, '')),
+					\ 'description': get(var_parts, 2, '')}
 	endif

-	let property_lines = filter(copy(docblock_lines), 'v:val =~? "^@property"')
-	for property_line in property_lines
-		let parts = matchlist(property_line, '\(@property\)\s\+\(\S\+\)\s*\(.*\)')
-		if len(parts) > 0
-			call add(res.properties, {
-						\ 'line': parts[0],
-						\ 'type': phpcomplete#GetTypeFromDocBlockParam(get(parts, 2, '')),
-						\ 'description': get(parts, 3, '')})
-		endif
-	endfor
-
 	return res
 endfunction
 " }}}
@@ -2564,7 +2498,6 @@ function! phpcomplete#GetCurrentNameSpace(file_lines) " {{{
 						let	name = matchstr(name, '\\\zs[^\\]\+\ze$')
 					endif
 				endif
-
 				" leading slash is not required use imports are always absolute
 				let imports[name] = {'name': object, 'kind': ''}
 			endfor
@@ -2600,7 +2533,6 @@ function! phpcomplete#GetCurrentNameSpace(file_lines) " {{{
 								elseif !exists('no_namespace_candidate')
 									" save the first namespacless match to be used if no better
 									" candidate found later on
-									let tag.namespace = namespace_for_classes
 									let no_namespace_candidate = tag
 								endif
 							endif
@@ -196,7 +196,7 @@ function! rubycomplete#Complete(findstart, base)
            if c =~ '\w'
                continue
            elseif ! c =~ '\.'
-                let idx = -1
+                idx = -1
                break
            else
                break
@@ -1,415 +0,0 @@
-" Author: Kevin Ballard
-" Description: Helper functions for Rust commands/mappings
-" Last Modified: May 27, 2014
-" For bugs, patches and license go to https://github.com/rust-lang/rust.vim
-
-" Jump {{{1
-
-function! rust#Jump(mode, function) range
-	let cnt = v:count1
-	normal! m'
-	if a:mode ==# 'v'
-		norm! gv
-	endif
-	let foldenable = &foldenable
-	set nofoldenable
-	while cnt > 0
-		execute "call <SID>Jump_" . a:function . "()"
-		let cnt = cnt - 1
-	endwhile
-	let &foldenable = foldenable
-endfunction
-
-function! s:Jump_Back()
-	call search('{', 'b')
-	keepjumps normal! w99[{
-endfunction
-
-function! s:Jump_Forward()
-	normal! j0
-	call search('{', 'b')
-	keepjumps normal! w99[{%
-	call search('{')
-endfunction
-
-" Run {{{1
-
-function! rust#Run(bang, args)
-	let args = s:ShellTokenize(a:args)
-	if a:bang
-		let idx = index(l:args, '--')
-		if idx != -1
-			let rustc_args = idx == 0 ? [] : l:args[:idx-1]
-			let args = l:args[idx+1:]
-		else
-			let rustc_args = l:args
-			let args = []
-		endif
-	else
-		let rustc_args = []
-	endif
-
-	let b:rust_last_rustc_args = l:rustc_args
-	let b:rust_last_args = l:args
-
-	call s:WithPath(function("s:Run"), rustc_args, args)
-endfunction
-
-function! s:Run(dict, rustc_args, args)
-	let exepath = a:dict.tmpdir.'/'.fnamemodify(a:dict.path, ':t:r')
-	if has('win32')
-		let exepath .= '.exe'
-	endif
-
-	let relpath = get(a:dict, 'tmpdir_relpath', a:dict.path)
-	let rustc_args = [relpath, '-o', exepath] + a:rustc_args
-
-	let rustc = exists("g:rustc_path") ? g:rustc_path : "rustc"
-
-	let pwd = a:dict.istemp ? a:dict.tmpdir : ''
-	let output = s:system(pwd, shellescape(rustc) . " " . join(map(rustc_args, 'shellescape(v:val)')))
-	if output != ''
-		echohl WarningMsg
-		echo output
-		echohl None
-	endif
-	if !v:shell_error
-		exe '!' . shellescape(exepath) . " " . join(map(a:args, 'shellescape(v:val)'))
-	endif
-endfunction
-
-" Expand {{{1
-
-function! rust#Expand(bang, args)
-	let args = s:ShellTokenize(a:args)
-	if a:bang && !empty(l:args)
-		let pretty = remove(l:args, 0)
-	else
-		let pretty = "expanded"
-	endif
-	call s:WithPath(function("s:Expand"), pretty, args)
-endfunction
-
-function! s:Expand(dict, pretty, args)
-	try
-		let rustc = exists("g:rustc_path") ? g:rustc_path : "rustc"
-
-		if a:pretty =~? '^\%(everybody_loops$\|flowgraph=\)'
-			let flag = '--xpretty'
-		else
-			let flag = '--pretty'
-		endif
-		let relpath = get(a:dict, 'tmpdir_relpath', a:dict.path)
-		let args = [relpath, '-Z', 'unstable-options', l:flag, a:pretty] + a:args
-		let pwd = a:dict.istemp ? a:dict.tmpdir : ''
-		let output = s:system(pwd, shellescape(rustc) . " " . join(map(args, 'shellescape(v:val)')))
-		if v:shell_error
-			echohl WarningMsg
-			echo output
-			echohl None
-		else
-			new
-			silent put =output
-			1
-			d
-			setl filetype=rust
-			setl buftype=nofile
-			setl bufhidden=hide
-			setl noswapfile
-			" give the buffer a nice name
-			let suffix = 1
-			let basename = fnamemodify(a:dict.path, ':t:r')
-			while 1
-				let bufname = basename
-				if suffix > 1 | let bufname .= ' ('.suffix.')' | endif
-				let bufname .= '.pretty.rs'
-				if bufexists(bufname)
-					let suffix += 1
-					continue
-				endif
-				exe 'silent noautocmd keepalt file' fnameescape(bufname)
-				break
-			endwhile
-		endif
-	endtry
-endfunction
-
-function! rust#CompleteExpand(lead, line, pos)
-	if a:line[: a:pos-1] =~ '^RustExpand!\s*\S*$'
-		" first argument and it has a !
-		let list = ["normal", "expanded", "typed", "expanded,identified", "flowgraph=", "everybody_loops"]
-		if !empty(a:lead)
-			call filter(list, "v:val[:len(a:lead)-1] == a:lead")
-		endif
-		return list
-	endif
-
-	return glob(escape(a:lead, "*?[") . '*', 0, 1)
-endfunction
-
-" Emit {{{1
-
-function! rust#Emit(type, args)
-	let args = s:ShellTokenize(a:args)
-	call s:WithPath(function("s:Emit"), a:type, args)
-endfunction
-
-function! s:Emit(dict, type, args)
-	try
-		let output_path = a:dict.tmpdir.'/output'
-
-		let rustc = exists("g:rustc_path") ? g:rustc_path : "rustc"
-
-		let relpath = get(a:dict, 'tmpdir_relpath', a:dict.path)
-		let args = [relpath, '--emit', a:type, '-o', output_path] + a:args
-		let pwd = a:dict.istemp ? a:dict.tmpdir : ''
-		let output = s:system(pwd, shellescape(rustc) . " " . join(map(args, 'shellescape(v:val)')))
-		if output != ''
-			echohl WarningMsg
-			echo output
-			echohl None
-		endif
-		if !v:shell_error
-			new
-			exe 'silent keepalt read' fnameescape(output_path)
-			1
-			d
-			if a:type == "llvm-ir"
-				setl filetype=llvm
-				let extension = 'll'
-			elseif a:type == "asm"
-				setl filetype=asm
-				let extension = 's'
-			endif
-			setl buftype=nofile
-			setl bufhidden=hide
-			setl noswapfile
-			if exists('l:extension')
-				" give the buffer a nice name
-				let suffix = 1
-				let basename = fnamemodify(a:dict.path, ':t:r')
-				while 1
-					let bufname = basename
-					if suffix > 1 | let bufname .= ' ('.suffix.')' | endif
-					let bufname .= '.'.extension
-					if bufexists(bufname)
-						let suffix += 1
-						continue
-					endif
-					exe 'silent noautocmd keepalt file' fnameescape(bufname)
-					break
-				endwhile
-			endif
-		endif
-	endtry
-endfunction
-
-" Utility functions {{{1
-
-" Invokes func(dict, ...)
-" Where {dict} is a dictionary with the following keys:
-"   'path' - The path to the file
-"   'tmpdir' - The path to a temporary directory that will be deleted when the
-"              function returns.
-"   'istemp' - 1 if the path is a file inside of {dict.tmpdir} or 0 otherwise.
-" If {istemp} is 1 then an additional key is provided:
-"   'tmpdir_relpath' - The {path} relative to the {tmpdir}.
-"
-" {dict.path} may be a path to a file inside of {dict.tmpdir} or it may be the
-" existing path of the current buffer. If the path is inside of {dict.tmpdir}
-" then it is guaranteed to have a '.rs' extension.
-function! s:WithPath(func, ...)
-	let buf = bufnr('')
-	let saved = {}
-	let dict = {}
-	try
-		let saved.write = &write
-		set write
-		let dict.path = expand('%')
-		let pathisempty = empty(dict.path)
-
-		" Always create a tmpdir in case the wrapped command wants it
-		let dict.tmpdir = tempname()
-		call mkdir(dict.tmpdir)
-
-		if pathisempty || !saved.write
-			let dict.istemp = 1
-			" if we're doing this because of nowrite, preserve the filename
-			if !pathisempty
-				let filename = expand('%:t:r').".rs"
-			else
-				let filename = 'unnamed.rs'
-			endif
-			let dict.tmpdir_relpath = filename
-			let dict.path = dict.tmpdir.'/'.filename
-
-			let saved.mod = &mod
-			set nomod
-
-			silent exe 'keepalt write! ' . fnameescape(dict.path)
-			if pathisempty
-				silent keepalt 0file
-			endif
-		else
-			let dict.istemp = 0
-			update
-		endif
-
-		call call(a:func, [dict] + a:000)
-	finally
-		if bufexists(buf)
-			for [opt, value] in items(saved)
-				silent call setbufvar(buf, '&'.opt, value)
-				unlet value " avoid variable type mismatches
-			endfor
-		endif
-		if has_key(dict, 'tmpdir') | silent call s:RmDir(dict.tmpdir) | endif
-	endtry
-endfunction
-
-function! rust#AppendCmdLine(text)
-	call setcmdpos(getcmdpos())
-	let cmd = getcmdline() . a:text
-	return cmd
-endfunction
-
-" Tokenize the string according to sh parsing rules
-function! s:ShellTokenize(text)
-	" states:
-	" 0: start of word
-	" 1: unquoted
-	" 2: unquoted backslash
-	" 3: double-quote
-	" 4: double-quoted backslash
-	" 5: single-quote
-	let l:state = 0
-	let l:current = ''
-	let l:args = []
-	for c in split(a:text, '\zs')
-		if l:state == 0 || l:state == 1 " unquoted
-			if l:c ==# ' '
-				if l:state == 0 | continue | endif
-				call add(l:args, l:current)
-				let l:current = ''
-				let l:state = 0
-			elseif l:c ==# '\'
-				let l:state = 2
-			elseif l:c ==# '"'
-				let l:state = 3
-			elseif l:c ==# "'"
-				let l:state = 5
-			else
-				let l:current .= l:c
-				let l:state = 1
-			endif
-		elseif l:state == 2 " unquoted backslash
-			if l:c !=# "\n" " can it even be \n?
-				let l:current .= l:c
-			endif
-			let l:state = 1
-		elseif l:state == 3 " double-quote
-			if l:c ==# '\'
-				let l:state = 4
-			elseif l:c ==# '"'
-				let l:state = 1
-			else
-				let l:current .= l:c
-			endif
-		elseif l:state == 4 " double-quoted backslash
-			if stridx('$`"\', l:c) >= 0
-				let l:current .= l:c
-			elseif l:c ==# "\n" " is this even possible?
-				" skip it
-			else
-				let l:current .= '\'.l:c
-			endif
-			let l:state = 3
-		elseif l:state == 5 " single-quoted
-			if l:c == "'"
-				let l:state = 1
-			else
-				let l:current .= l:c
-			endif
-		endif
-	endfor
-	if l:state != 0
-		call add(l:args, l:current)
-	endif
-	return l:args
-endfunction
-
-function! s:RmDir(path)
-	" sanity check; make sure it's not empty, /, or $HOME
-	if empty(a:path)
-		echoerr 'Attempted to delete empty path'
-		return 0
-	elseif a:path == '/' || a:path == $HOME
-		echoerr 'Attempted to delete protected path: ' . a:path
-		return 0
-	endif
-	return system("rm -rf " . shellescape(a:path))
-endfunction
-
-" Executes {cmd} with the cwd set to {pwd}, without changing Vim's cwd.
-" If {pwd} is the empty string then it doesn't change the cwd.
-function! s:system(pwd, cmd)
-	let cmd = a:cmd
-	if !empty(a:pwd)
-		let cmd = 'cd ' . shellescape(a:pwd) . ' && ' . cmd
-	endif
-	return system(cmd)
-endfunction
-
-" Playpen Support {{{1
-" Parts of gist.vim by Yasuhiro Matsumoto <mattn.jp@gmail.com> reused
-" gist.vim available under the BSD license, available at
-" http://github.com/mattn/gist-vim
-function! s:has_webapi()
-    if !exists("*webapi#http#post")
-	try
-	    call webapi#http#post()
-	catch
-	endtry
-    endif
-    return exists("*webapi#http#post")
-endfunction
-
-function! rust#Play(count, line1, line2, ...) abort
-    redraw
-
-    let l:rust_playpen_url = get(g:, 'rust_playpen_url', 'https://play.rust-lang.org/')
-    let l:rust_shortener_url = get(g:, 'rust_shortener_url', 'https://is.gd/')
-
-    if !s:has_webapi()
-	echohl ErrorMsg | echomsg ':RustPlay depends on webapi.vim (https://github.com/mattn/webapi-vim)' | echohl None
-	return
-    endif
-
-    let bufname = bufname('%')
-    if a:count < 1
-	let content = join(getline(a:line1, a:line2), "\n")
-    else
-	let save_regcont = @"
-	let save_regtype = getregtype('"')
-	silent! normal! gvy
-	let content = @"
-	call setreg('"', save_regcont, save_regtype)
-    endif
-
-    let body = l:rust_playpen_url."?code=".webapi#http#encodeURI(content)
-
-    if strlen(body) > 5000
-	echohl ErrorMsg | echomsg 'Buffer too large, max 5000 encoded characters ('.strlen(body).')' | echohl None
-	return
-    endif
-
-    let payload = "format=simple&url=".webapi#http#encodeURI(body)
-    let res = webapi#http#post(l:rust_shortener_url.'create.php', payload, {})
-    let url = res.content
-
-    redraw | echomsg 'Done: '.url
-endfunction
-
-" }}}1
-
-" vim: set noet sw=8 ts=8:
@@ -1,107 +0,0 @@
-" Author: Stephen Sugden <stephen@stephensugden.com>
-"
-" Adapted from https://github.com/fatih/vim-go
-" For bugs, patches and license go to https://github.com/rust-lang/rust.vim
-
-if !exists("g:rustfmt_autosave")
-	let g:rustfmt_autosave = 0
-endif
-
-if !exists("g:rustfmt_command")
-	let g:rustfmt_command = "rustfmt"
-endif
-
-if !exists("g:rustfmt_options")
-	let g:rustfmt_options = ""
-endif
-
-if !exists("g:rustfmt_fail_silently")
-	let g:rustfmt_fail_silently = 0
-endif
-
-let s:got_fmt_error = 0
-
-function! s:RustfmtCommandRange(filename, line1, line2)
-	let l:arg = {"file": shellescape(a:filename), "range": [a:line1, a:line2]}
-	return printf("%s %s --write-mode=overwrite --file-lines '[%s]'", g:rustfmt_command, g:rustfmt_options, json_encode(l:arg))
-endfunction
-
-function! s:RustfmtCommand(filename)
-	return g:rustfmt_command . " --write-mode=overwrite " . g:rustfmt_options . " " . shellescape(a:filename)
-endfunction
-
-function! s:RunRustfmt(command, curw, tmpname)
-	if exists("*systemlist")
-		let out = systemlist(a:command)
-	else
-		let out = split(system(a:command), '\r\?\n')
-	endif
-
-	if v:shell_error == 0 || v:shell_error == 3
-		" remove undo point caused via BufWritePre
-		try | silent undojoin | catch | endtry
-
-		" Replace current file with temp file, then reload buffer
-		call rename(a:tmpname, expand('%'))
-		silent edit!
-		let &syntax = &syntax
-
-		" only clear location list if it was previously filled to prevent
-		" clobbering other additions
-		if s:got_fmt_error
-			let s:got_fmt_error = 0
-			call setloclist(0, [])
-			lwindow
-		endif
-	elseif g:rustfmt_fail_silently == 0
-		" otherwise get the errors and put them in the location list
-		let errors = []
-
-		for line in out
-			" src/lib.rs:13:5: 13:10 error: expected `,`, or `}`, found `value`
-			let tokens = matchlist(line, '^\(.\{-}\):\(\d\+\):\(\d\+\):\s*\(\d\+:\d\+\s*\)\?\s*error: \(.*\)')
-			if !empty(tokens)
-				call add(errors, {"filename": @%,
-						 \"lnum":     tokens[2],
-						 \"col":      tokens[3],
-						 \"text":     tokens[5]})
-			endif
-		endfor
-
-		if empty(errors)
-			% | " Couldn't detect rustfmt error format, output errors
-		endif
-
-		if !empty(errors)
-			call setloclist(0, errors, 'r')
-			echohl Error | echomsg "rustfmt returned error" | echohl None
-		endif
-
-		let s:got_fmt_error = 1
-		lwindow
-		" We didn't use the temp file, so clean up
-		call delete(a:tmpname)
-	endif
-
-	call winrestview(a:curw)
-endfunction
-
-function! rustfmt#FormatRange(line1, line2)
-	let l:curw = winsaveview()
-	let l:tmpname = expand("%:p:h") . "/." . expand("%:p:t") . ".rustfmt"
-	call writefile(getline(1, '$'), l:tmpname)
-
-	let command = s:RustfmtCommandRange(l:tmpname, a:line1, a:line2)
-
-	call s:RunRustfmt(command, l:curw, l:tmpname)
-endfunction
-
-function! rustfmt#Format()
-	let l:curw = winsaveview()
-	let l:tmpname = expand("%:p:h") . "/." . expand("%:p:t") . ".rustfmt"
-	call writefile(getline(1, '$'), l:tmpname)
-
-	let command = s:RustfmtCommand(l:tmpname)
-
-	call s:RunRustfmt(command, l:curw, l:tmpname)
-endfunction
@@ -2,7 +2,7 @@
 " Language:    SQL
 " Maintainer:  David Fishburn <dfishburn dot vim at gmail dot com>
 " Version:     16.0
-" Last Change: 2017 Oct 15
+" Last Change: 2015 Dec 29
 " Homepage:    http://www.vim.org/scripts/script.php?script_id=1572
 " Usage:       For detailed help
 "              ":help sql.txt"
@@ -860,7 +860,7 @@ function! s:SQLCGetColumns(table_name, list_type)

         " Start characterwise visual mode
         " Advance right one character
-         " Search forward until one of the following:
+         " Search foward until one of the following:
         "     1.  Another select/update/delete statement
         "     2.  A ; at the end of a line (the delimiter)
         "     3.  The end of the file (incase no delimiter)
@@ -41,16 +41,9 @@ this autocmd might be useful:
     autocmd SourcePre */colors/blue_sky.vim set background=dark
 Replace "blue_sky" with the name of the colorscheme.

-In case you want to tweak a colorscheme after it was loaded, check out the
+In case you want to tweak a colorscheme after it was loaded, check out that
 ColorScheme autocmd event.

-To customize a colorscheme use another name, e.g.  "~/.vim/colors/mine.vim",
-and use `:runtime` to load the original colorscheme:
-	" load the "evening" colorscheme
-	runtime colors/evening.vim
-	" change the color of statements
-	hi Statement ctermfg=Blue guifg=Blue
-
 To see which highlight group is used where, find the help for
 "highlight-groups" and "group-name".

@@ -64,7 +57,6 @@ Search for "highlight_init".
 If you think you have a color scheme that is good enough to be used by others,
 please check the following items:

- Source the tools/check_colors.vim script to check for common mistakes.
 - Does it work in a color terminal as well as in the GUI?
 - Is "g:colors_name" set to a meaningful value?  In case of doubt you can do
  it this way:
@@ -1,6 +1,6 @@
 " Vim color file
 " Maintainer:	Bram Moolenaar <Bram@vim.org>
-" Last Change:	2016 Oct 10
+" Last Change:	2006 Apr 14

 " This color scheme uses a dark grey background.

@@ -46,8 +46,8 @@ hi CursorColumn term=reverse ctermbg=Black guibg=grey40
 hi CursorLine term=underline cterm=underline guibg=grey40

 " Groups for syntax highlighting
-hi Constant term=underline ctermfg=Magenta guifg=#ffa0a0
-hi Special term=bold ctermfg=LightRed guifg=Orange
+hi Constant term=underline ctermfg=Magenta guifg=#ffa0a0 guibg=grey5
+hi Special term=bold ctermfg=LightRed guifg=Orange guibg=grey5
 if &t_Co > 8
  hi Statement term=bold cterm=bold ctermfg=Yellow guifg=#ffff60 gui=bold
 endif
@@ -1,136 +0,0 @@
-" This script tests a color scheme for some errors. Load the scheme and source
-" this script. e.g. :e colors/desert.vim | :so test_colors.vim
-" Will output possible errors.
-
-let s:save_cpo= &cpo
-set cpo&vim
-
-func! Test_check_colors()
-  call cursor(1,1)
-  let err={}
-
-  " 1) Check g:colors_name is existing
-  if !search('\<\%(g:\)\?colors_name\>', 'cnW')
-    let err['colors_name'] = 'g:colors_name not set'
-  else
-    let err['colors_name'] = 'OK'
-  endif
-
-  " 2) Check for some well-defined highlighting groups
-  " Some items, check several groups, e.g. Diff, Spell
-  let hi_groups = ['ColorColumn', 'Diff', 'ErrorMsg', 'Folded',
-        \ 'FoldColumn', 'IncSearch', 'LineNr', 'ModeMsg', 'MoreMsg', 'NonText',
-        \ 'Normal', 'Pmenu', 'Todo', 'Search', 'Spell', 'StatusLine', 'TabLine',
-        \ 'Title', 'Visual', 'WarningMsg', 'WildMenu']
-  let groups={}
-  for group in hi_groups
-    if search('\c@suppress\s\+'.group, 'cnW')
-      " skip check, if the script contains a line like
-      " @suppress Visual:
-      let groups[group] = 'Ignoring '.group
-      continue
-    endif
-    if !search('hi\%[ghlight] \+'.group, 'cnW')
-      let groups[group] = 'No highlight definition for '.group
-      continue
-    endif
-    if !search('hi\%[ghlight] \+'.group. '.*fg=', 'cnW')
-      let groups[group] = 'Missing foreground color for '.group
-      continue
-    endif
-    if search('hi\%[ghlight] \+'.group. '.*guibg=', 'cnW') &&
-        \ !search('hi\%[ghlight] \+'.group. '.*ctermbg=', 'cnW')
-      let groups[group] = 'Missing bg terminal color for '.group
-      continue
-    endif
-    call search('hi\%[ghlight] \+'.group, 'cW')
-    " only check in the current line
-    if !search('guifg', 'cnW', line('.'))   || !search('ctermfg', 'cnW', line('.'))
-      " do not check for background colors, they could be intentionally left out
-      let groups[group] = 'Missing fg definition for '.group
-    endif
-    call cursor(1,1)
-  endfor
-  let err['highlight'] = groups
-
-  " 3) Check, that it does not set background highlighting
-  " Doesn't ':hi Normal ctermfg=253 ctermfg=233' also set the background sometimes?
-  let bg_set='\(set\?\|setl\(ocal\)\?\) .*\(background\|bg\)=\(dark\|light\)'
-  let bg_let='let \%([&]\%([lg]:\)\?\)\%(background\|bg\)\s*=\s*\([''"]\?\)\w\+\1'
-  let bg_pat='\%('.bg_set. '\|'.bg_let.'\)'
-  let line=search(bg_pat, 'cnW')
-  if search(bg_pat, 'cnW')
-    exe line
-    if search('hi \U\w\+\s\+\S', 'cbnW')
-      let err['background'] = 'Should not set background option after :hi statement'
-    endif
-  else
-    let err['background'] = 'OK'
-  endif
-  call cursor(1,1)
-
-  " 4) Check, that t_Co is checked
-  let pat = '[&]t_Co\s*[<>=]=\?\s*\d\+'
-  if !search(pat, 'ncW')
-    let err['t_Co'] = 'Does not check terminal for capable colors'
-  endif
-
-  " 5) Initializes correctly, e.g. should have a section like
-  " hi clear
-  " if exists("syntax_on")
-  " syntax reset
-  " endif
-  let pat='hi\%[ghlight]\s*clear\n\s*if\s*exists(\([''"]\)syntax_on\1)\n\s*syn\%[tax]\s*reset\n\s*endif'
-  if !search(pat, 'cnW')
-    let err['init'] = 'No initialization'
-  endif
-
-  " 6) Does not use :syn on
-  if search('syn\%[tax]\s\+on', 'cnW')
-    let err['background'] = 'Should not issue :syn on'
-  endif
-
-  " 7) Does not define filetype specfic groups like vimCommand, htmlTag,
-  let hi_groups = ['vim', 'html', 'python', 'sh', 'ruby']
-  for group in hi_groups
-    let pat='\Chi\%[ghlight]\s*\zs'.group.'\w\+\>'
-    if search(pat, 'cnW')
-      let line = search(pat, 'cW')
-      let err['filetype'] = get(err, 'filetype', 'Should not define: ') . matchstr(getline('.'), pat). ' '
-    endif
-    call cursor(1,1)
-  endfor
-  let g:err = err
-
-  " print Result
-  call Result(err)
-endfu
-
-fu! Result(err)
-  let do_roups = 0
-  echohl Title|echomsg "---------------"|echohl Normal
-  for key in sort(keys(a:err))
-    if key is# 'highlight'
-      let do_groups = 1
-      continue
-    else
-      if a:err[key] !~ 'OK'
-        echohl Title
-      endif
-      echomsg printf("%15s: %s", key, a:err[key])
-      echohl Normal
-    endif
-  endfor
-  echohl Title|echomsg "---------------"|echohl Normal
-  if do_groups
-    echohl Title | echomsg "Groups" | echohl Normal
-    for v1 in sort(keys(a:err['highlight']))
-      echomsg printf("%25s: %s", v1, a:err['highlight'][v1])
-    endfor
-  endif
-endfu
-
-call Test_check_colors()
-
-let &cpo = s:save_cpo
-unlet s:save_cpo
@@ -1,7 +1,7 @@
 " Vim compiler file
-" Compiler:             BDF to PCF Conversion
-" Previous Maintainer:  Nikolai Weibull <now@bitwi.se>
-" Latest Revision:      2006-04-19
+" Compiler:         BDF to PCF Conversion
+" Maintainer:       Nikolai Weibull <now@bitwi.se>
+" Latest Revision:  2006-04-19

 if exists("current_compiler")
  finish
@@ -1,35 +0,0 @@
-" Vim compiler file
-" Compiler:         Cargo Compiler
-" Maintainer:       Damien Radtke <damienradtke@gmail.com>
-" Latest Revision:  2014 Sep 24
-" For bugs, patches and license go to https://github.com/rust-lang/rust.vim
-
-if exists('current_compiler')
-	finish
-endif
-runtime compiler/rustc.vim
-let current_compiler = "cargo"
-
-let s:save_cpo = &cpo
-set cpo&vim
-
-if exists(':CompilerSet') != 2
-	command -nargs=* CompilerSet setlocal <args>
-endif
-
-if exists('g:cargo_makeprg_params')
-	execute 'CompilerSet makeprg=cargo\ '.escape(g:cargo_makeprg_params, ' \|"').'\ $*'
-else
-	CompilerSet makeprg=cargo\ $*
-endif
-
-" Ignore general cargo progress messages
-CompilerSet errorformat+=
-			\%-G%\\s%#Downloading%.%#,
-			\%-G%\\s%#Compiling%.%#,
-			\%-G%\\s%#Finished%.%#,
-			\%-G%\\s%#error:\ Could\ not\ compile\ %.%#,
-			\%-G%\\s%#To\ learn\ more\\,%.%#
-
-let &cpo = s:save_cpo
-unlet s:save_cpo
@@ -1,54 +0,0 @@
-" Vim compiler file
-" Compiler:     ConTeXt typesetting engine
-" Maintainer:   Nicola Vitacolonna <nvitacolonna@gmail.com>
-" Last Change:  2016 Oct 21
-
-if exists("current_compiler")
-  finish
-endif
-let s:keepcpo= &cpo
-set cpo&vim
-
-if exists(":CompilerSet") != 2    " older Vim always used :setlocal
-  command -nargs=* CompilerSet setlocal <args>
-endif
-
-" If makefile exists and we are not asked to ignore it, we use standard make
-" (do not redefine makeprg)
-if get(b:, 'context_ignore_makefile', get(g:, 'context_ignore_makefile', 0)) ||
-      \ (!filereadable('Makefile') && !filereadable('makefile'))
-  let current_compiler = 'context'
-  " The following assumes that the current working directory is set to the
-  " directory of the file to be typeset
-  let &l:makeprg = get(b:, 'context_mtxrun', get(g:, 'context_mtxrun', 'mtxrun'))
-        \ . ' --script context --autogenerate --nonstopmode --synctex='
-        \ . (get(b:, 'context_synctex', get(g:, 'context_synctex', 0)) ? '1' : '0')
-        \ . ' ' . get(b:, 'context_extra_options', get(g:, 'context_extra_options', ''))
-        \ . ' ' . shellescape(expand('%:p:t'))
-else
-  let current_compiler = 'make'
-endif
-
-let b:context_errorformat = ''
-      \ . '%-Popen source%.%#> %f,'
-      \ . '%-Qclose source%.%#> %f,'
-      \ . "%-Popen source%.%#name '%f',"
-      \ . "%-Qclose source%.%#name '%f',"
-      \ . '%Etex %trror%.%#mp error on line %l in file %f:%.%#,'
-      \ . 'tex %trror%.%#error on line %l in file %f: %m,'
-      \ . '%Elua %trror%.%#error on line %l in file %f:,'
-      \ . '%+Emetapost %#> error: %#,'
-      \ . '! error: %#%m,'
-      \ . '%-C %#,'
-      \ . '%C! %m,'
-      \ . '%Z[ctxlua]%m,'
-      \ . '%+C<*> %.%#,'
-      \ . '%-C%.%#,'
-      \ . '%Z...%m,'
-      \ . '%-Zno-error,'
-      \ . '%-G%.%#' " Skip remaining lines
-
-execute 'CompilerSet errorformat=' . escape(b:context_errorformat, ' ')
-
-let &cpo = s:keepcpo
-unlet s:keepcpo
@@ -1,16 +0,0 @@
-" Vim compiler file
-" Compiler:	csslint for CSS
-" Maintainer: Daniel Moch <daniel@danielmoch.com>
-" Last Change: 2016 May 21
-
-if exists("current_compiler")
-  finish
-endif
-let current_compiler = "csslint"
-
-if exists(":CompilerSet") != 2		" older Vim always used :setlocal
-  command -nargs=* CompilerSet setlocal <args>
-endif
-
-CompilerSet makeprg=csslint\ --format=compact
-CompilerSet errorformat=%-G,%-G%f:\ lint\ free!,%f:\ line\ %l\\,\ col\ %c\\,\ %trror\ -\ %m,%f:\ line\ %l\\,\ col\ %c\\,\ %tarning\ -\ %m,%f:\ line\ %l\\,\ col\ %c\\,\ %m
@@ -1,7 +1,7 @@
 " Vim compiler file
-" Compiler:             GNU C Compiler
-" Previous Maintainer:  Nikolai Weibull <now@bitwi.se>
-" Latest Revision:      2010-10-14
+" Compiler:         GNU C Compiler
+" Maintainer:       Nikolai Weibull <now@bitwi.se>
+" Latest Revision:  2010-10-14
 " 			added line suggested by Anton Lindqvist 2016 Mar 31

 if exists("current_compiler")
@@ -1,26 +0,0 @@
-" Vim compiler file
-" Compiler:         GHC Haskell Compiler
-" Maintainer:       Daniel Campoverde <alx@sillybytes.net>
-" Latest Revision:  2016-11-29
-
-if exists("current_compiler")
-  finish
-endif
-let current_compiler = "ghc"
-
-let s:cpo_save = &cpo
-set cpo&vim
-
-CompilerSet errorformat=
-    \%-G%.%#:\ build,
-    \%-G%.%#preprocessing\ library\ %.%#,
-    \%-G[%.%#]%.%#,
-    \%E%f:%l:%c:\ %m,
-    \%-G--%.%#
-
-if exists('g:compiler_ghc_ignore_unmatched_lines')
-  CompilerSet errorformat+=%-G%.%#
-endif
-
-let &cpo = s:cpo_save
-unlet s:cpo_save
@@ -1,16 +0,0 @@
-" Vim compiler file
-" Compiler:	Pylint for Python
-" Maintainer: Daniel Moch <daniel@danielmoch.com>
-" Last Change: 2016 May 20
-
-if exists("current_compiler")
-  finish
-endif
-let current_compiler = "pylint"
-
-if exists(":CompilerSet") != 2		" older Vim always used :setlocal
-  command -nargs=* CompilerSet setlocal <args>
-endif
-
-CompilerSet makeprg=pylint\ --output-format=text\ --msg-template=\"{path}:{line}:{column}:{C}:\ [{symbol}]\ {msg}\"\ --reports=no
-CompilerSet errorformat=%A%f:%l:%c:%t:\ %m,%A%f:%l:\ %m,%A%f:(%l):\ %m,%-Z%p^%.%#,%-G%.%#
@@ -1,8 +1,7 @@
 " Vim compiler file
-" Compiler:             sphinx >= 1.0.8, http://www.sphinx-doc.org
-" Description:          reStructuredText Documentation Format
-" Previous Maintainer:  Nikolai Weibull <now@bitwi.se>
-" Latest Revision:      2017-03-31
+" Compiler:         reStructuredText Documentation Format
+" Maintainer:       Nikolai Weibull <now@bitwi.se>
+" Latest Revision:  2006-04-19

 if exists("current_compiler")
  finish
@@ -12,18 +11,12 @@ let current_compiler = "rst"
 let s:cpo_save = &cpo
 set cpo&vim

-if exists(":CompilerSet") != 2
-  command -nargs=* CompilerSet setlocal <args>
-endif
-
-CompilerSet errorformat=
-      \%f\\:%l:\ %tEBUG:\ %m,
-      \%f\\:%l:\ %tNFO:\ %m,
-      \%f\\:%l:\ %tARNING:\ %m,
-      \%f\\:%l:\ %tRROR:\ %m,
-      \%f\\:%l:\ %tEVERE:\ %m,
-      \%f\\:%s:\ %tARNING:\ %m,
-      \%f\\:%s:\ %tRROR:\ %m,
+setlocal errorformat=
+      \%f:%l:\ (%tEBUG/0)\ %m,
+      \%f:%l:\ (%tNFO/1)\ %m,
+      \%f:%l:\ (%tARNING/2)\ %m,
+      \%f:%l:\ (%tRROR/3)\ %m,
+      \%f:%l:\ (%tEVERE/3)\ %m,
      \%D%*\\a[%*\\d]:\ Entering\ directory\ `%f',
      \%X%*\\a[%*\\d]:\ Leaving\ directory\ `%f',
      \%DMaking\ %*\\a\ in\ %f
@@ -1,46 +0,0 @@
-" Vim compiler file
-" Compiler:         Rust Compiler
-" Maintainer:       Chris Morgan <me@chrismorgan.info>
-" Latest Revision:  2013 Jul 12
-" For bugs, patches and license go to https://github.com/rust-lang/rust.vim
-
-if exists("current_compiler")
-	finish
-endif
-let current_compiler = "rustc"
-
-let s:cpo_save = &cpo
-set cpo&vim
-
-if exists(":CompilerSet") != 2
-	command -nargs=* CompilerSet setlocal <args>
-endif
-
-if exists("g:rustc_makeprg_no_percent") && g:rustc_makeprg_no_percent != 0
-	CompilerSet makeprg=rustc
-else
-	CompilerSet makeprg=rustc\ \%
-endif
-
-" Old errorformat (before nightly 2016/08/10)
-CompilerSet errorformat=
-			\%f:%l:%c:\ %t%*[^:]:\ %m,
-			\%f:%l:%c:\ %*\\d:%*\\d\ %t%*[^:]:\ %m,
-			\%-G%f:%l\ %s,
-			\%-G%*[\ ]^,
-			\%-G%*[\ ]^%*[~],
-			\%-G%*[\ ]...
-
-" New errorformat (after nightly 2016/08/10)
-CompilerSet errorformat+=
-			\%-G,
-			\%-Gerror:\ aborting\ %.%#,
-			\%-Gerror:\ Could\ not\ compile\ %.%#,
-			\%Eerror:\ %m,
-			\%Eerror[E%n]:\ %m,
-			\%Wwarning:\ %m,
-			\%Inote:\ %m,
-			\%C\ %#-->\ %f:%l:%c
-
-let &cpo = s:cpo_save
-unlet s:cpo_save
@@ -1,7 +1,7 @@
 " The default vimrc file.
 "
 " Maintainer:	Bram Moolenaar <Bram@vim.org>
-" Last change:	2017 Jun 13
+" Last change:	2016 Sep 02
 "
 " This is loaded if no vimrc file was found.
 " Except when Vim is run with "-u NONE" or "-C".
@@ -21,16 +21,7 @@ endif

 " Use Vim settings, rather than Vi settings (much better!).
 " This must be first, because it changes other options as a side effect.
-" Avoid side effects when it was already reset.
-if &compatible
-  set nocompatible
-endif
-
-" When the +eval feature is missing, the set command above will be skipped.
-" Use a trick to reset compatible only when the +eval feature is missing.
-silent! while 0
-  set nocompatible
-silent! endwhile
+set nocompatible

 " Allow backspacing over everything in insert mode.
 set backspace=indent,eol,start
@@ -106,13 +97,12 @@ if has("autocmd")
    au!

    " When editing a file, always jump to the last known cursor position.
-    " Don't do it when the position is invalid, when inside an event handler
-    " (happens when dropping a file on gvim) and for a commit message (it's
-    " likely a different one than last time).
+    " Don't do it when the position is invalid or when inside an event handler
+    " (happens when dropping a file on gvim).
    autocmd BufReadPost *
-      \ if line("'\"") >= 1 && line("'\"") <= line("$") && &ft !~# 'commit'
-      \ |   exe "normal! g`\""
-      \ | endif
+      \ if line("'\"") >= 1 && line("'\"") <= line("$") |
+      \   exe "normal! g`\"" |
+      \ endif

  augroup END

@@ -30,10 +30,8 @@ DOCS = \
 	filetype.txt \
 	fold.txt \
 	ft_ada.txt \
-	ft_rust.txt \
 	ft_sql.txt \
 	gui.txt \
-	gui_mac.txt \
 	gui_w32.txt \
 	gui_x11.txt \
 	hangulin.txt \
@@ -102,7 +100,6 @@ DOCS = \
 	tabpage.txt \
 	tagsrch.txt \
 	term.txt \
-	terminal.txt \
 	tips.txt \
 	todo.txt \
 	uganda.txt \
@@ -168,7 +165,6 @@ HTMLS = \
 	filetype.html \
 	fold.html \
 	ft_ada.html \
-	ft_rust.html \
 	ft_sql.html \
 	gui.html \
 	gui_w32.html \
@@ -238,7 +234,6 @@ HTMLS = \
 	tabpage.html \
 	tagsrch.html \
 	term.html \
-	terminal.html \
 	tips.html \
 	todo.html \
 	uganda.html \
@@ -344,7 +339,7 @@ xxd.man: xxd.1
 	nroff -man xxd.1 | sed -e s/.//g > xxd.man

 uganda.nsis.txt: uganda.txt
-	sed -e 's/[ 	]*\*[-a-zA-Z0-9.]*\*//g' -e 's/vim:tw=78:.*//' \
+	sed -e 's/[ 	]*\*[-a-zA-Z0-9.]*\*//g' -e 's/vim:tw=78://' \
 		uganda.txt | uniq >uganda.nsis.txt

 # Awk version of .txt to .html conversion.
@@ -376,10 +371,6 @@ tags.ref tags.html: tags
 perlhtml: tags $(DOCS)
 	./vim2html.pl tags $(DOCS)

-# Check URLs in the help with "curl".
-test_urls:
-	vim -S test_urls.vim
-
 clean:
 	-rm doctags *.html tags.ref

@@ -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).

@@ -1,4 +1,4 @@
-*autocmd.txt*   For Vim version 8.0.  Last change: 2018 Mar 15
+*autocmd.txt*   For Vim version 8.0.  Last change: 2016 Sep 21


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -21,6 +21,7 @@ For a basic explanation, see section |40.3| in the user manual.
 11. Disabling autocommands	|autocmd-disable|

 {Vi does not have any of these commands}
+{only when the |+autocmd| feature has not been disabled at compile time}

 ==============================================================================
 1. Introduction						*autocmd-intro*
@@ -32,7 +33,7 @@ files matching *.c.  You can also use autocommands to implement advanced
 features, such as editing compressed files (see |gzip-example|).  The usual
 place to put autocommands is in your .vimrc or .exrc file.

-				*E203* *E204* *E143* *E855* *E937* *E952*
+						*E203* *E204* *E143* *E855*
 WARNING: Using autocommands is very powerful, and may lead to unexpected side
 effects.  Be careful not to destroy your text.
 - It's a good idea to do some testing on an expendable copy of a file first.
@@ -56,8 +57,6 @@ effects.  Be careful not to destroy your text.
 			Add {cmd} to the list of commands that Vim will
 			execute automatically on {event} for a file matching
 			{pat} |autocmd-patterns|.
-			Note: A quote character is seen as argument to the
-			:autocmd and won't start a comment.
 			Vim always adds the {cmd} after existing autocommands,
 			so that the autocommands execute in the order in which
 			they were given.  See |autocmd-nested| for [nested].
@@ -69,14 +68,7 @@ Note: The ":autocmd" command can only be followed by another command when the
 '|' appears before {cmd}.  This works: >
 	:augroup mine | au! BufRead | augroup END
 But this sees "augroup" as part of the defined command: >
-	:augroup mine | au! BufRead * | augroup END
 	:augroup mine | au BufRead * set tw=70 | augroup END
-Instead you can put the group name into the command: >
-	:au! mine BufRead *
-	:au mine BufRead * set tw=70
-Or use `:execute`: >
-	:augroup mine | exe "au! BufRead *" | augroup END
-	:augroup mine | exe "au BufRead * set tw=70" | augroup END

 Note that special characters (e.g., "%", "<cword>") in the ":autocmd"
 arguments are not expanded when the autocommand is defined.  These will be
@@ -87,16 +79,11 @@ exception is that "<sfile>" is expanded when the autocmd is defined.  Example:

 Here Vim expands <sfile> to the name of the file containing this line.

-`:autocmd` adds to the list of autocommands regardless of whether they are
-already present.  When your .vimrc file is sourced twice, the autocommands
-will appear twice.  To avoid this, define your autocommands in a group, so
-that you can easily clear them: >
+When your .vimrc file is sourced twice, the autocommands will appear twice.
+To avoid this, put this command in your .vimrc file, before defining
+autocommands: >

-	augroup vimrc
-	  " Remove all vimrc autocommands
-	  autocmd!
-	  au BufNewFile,BufRead *.html so <sfile>:h/html.vim
-	augroup END
+	:autocmd!	" Remove ALL autocommands for the current group.

 If you don't want to remove all autocommands, you can instead use a variable
 to ensure that Vim includes the autocommands only once: >
@@ -143,15 +130,8 @@ prompt.  When one command outputs two messages this can happen anyway.

 :au[tocmd]! [group] {event}
 			Remove ALL autocommands for {event}.
-			Warning: You should not do this without a group for
-			|BufRead| and other common events, it can break
-			plugins, syntax highlighting, etc.

 :au[tocmd]! [group]	Remove ALL autocommands.
-			Note: a quote will be seen as argument to the :autocmd
-			and won't start a comment.
-			Warning: You should normally not do this without a
-			group, it breaks plugins, syntax highlighting, etc.

 When the [group] argument is not given, Vim uses the current group (as defined
 with ":augroup"); otherwise, Vim uses the group defined with [group].
@@ -262,7 +242,6 @@ Name			triggered by ~
 |BufCreate|		just after adding a buffer to the buffer list
 |BufDelete|		before deleting a buffer from the buffer list
 |BufWipeout|		before completely deleting a buffer
-|TerminalOpen|		after a terminal buffer was created

 |BufFilePre|		before changing the name of the current buffer
 |BufFilePost|		after changing the name of the current buffer
@@ -291,8 +270,7 @@ Name			triggered by ~
 |GUIFailed|		after starting the GUI failed
 |TermResponse|		after the terminal response to |t_RV| is received

-|QuitPre|		when using `:quit`, before deciding whether to exit
-|ExitPre|		when using a command that may make Vim exit
+|QuitPre|		when using `:quit`, before deciding whether to quit
 |VimLeavePre|		before exiting Vim, before writing the viminfo file
 |VimLeave|		before exiting Vim, after writing the viminfo file

@@ -301,8 +279,6 @@ Name			triggered by ~
 |FileChangedShellPost|	After handling a file changed since editing started
 |FileChangedRO|		before making the first change to a read-only file

-|DirChanged|		after the working directory has changed
-
 |ShellCmdPost|		after executing a shell command
 |ShellFilterPost|	after filtering with a shell command

@@ -330,10 +306,6 @@ Name			triggered by ~
 |CmdwinEnter|		after entering the command-line window
 |CmdwinLeave|		before leaving the command-line window

-|CmdlineChanged|	after a change was made to the command-line text
-|CmdlineEnter|		after the cursor moves to the command line
-|CmdlineLeave|		before the cursor leaves the command line
-
 |InsertEnter|		starting Insert mode
 |InsertChange|		when typing <Insert> while in Insert or Replace mode
 |InsertLeave|		when leaving Insert mode
@@ -342,10 +314,6 @@ Name			triggered by ~

 |TextChanged|		after a change was made to the text in Normal mode
 |TextChangedI|		after a change was made to the text in Insert mode
-			when popup menu is not visible
-|TextChangedP|		after a change was made to the text in Insert mode
-			when popup menu visible
-|TextYankPost|		after text is yanked or deleted

 |ColorScheme|		after loading a color scheme

@@ -515,29 +483,6 @@ CmdUndefined			When a user command is used but it isn't
 				command is defined.  An alternative is to
 				always define the user command and have it
 				invoke an autoloaded function.  See |autoload|.
-							*CmdlineChanged*
-CmdlineChanged			After a change was made to the text in the
-				command line.  Be careful not to mess up
-				the command line, it may cause Vim to lock up.
-				<afile> is set to a single character,
-				indicating the type of command-line.
-				|cmdwin-char|
-							*CmdlineEnter*
-CmdlineEnter			After moving the cursor to the command line,
-				where the user can type a command or search
-				string.
-				<afile> is set to a single character,
-				indicating the type of command-line.
-				|cmdwin-char|
-							*CmdlineLeave*
-CmdlineLeave			Before leaving the command line.
-				Also when abandoning the command line, after
-				typing CTRL-C or <Esc>.
-				When the commands result in an error the
-				command line is still executed.
-				<afile> is set to a single character,
-				indicating the type of command-line.
-				|cmdwin-char|
 							*CmdwinEnter*
 CmdwinEnter			After entering the command-line window.
 				Useful for setting options specifically for
@@ -648,21 +593,6 @@ FileChangedRO			Before making the first change to a read-only
 							*E881*
 				If the number of lines changes saving for undo
 				may fail and the change will be aborted.
-							*DirChanged*
-DirChanged			The working directory has changed in response
-				to the |:cd| or |:lcd| commands, or as a
-				result of the 'autochdir' option.
-				The pattern can be:
-					"window" to trigger on `:lcd
-					"global" to trigger on `:cd`
-					"auto"   to trigger on 'autochdir'.
-					"drop"	 to trigger on editing a file
-				<afile> is set to the new directory name.
-							*ExitPre*
-ExitPre				When using `:quit`, `:wq` in a way it makes
-				Vim exit, or using `:qall`, just after
-				|QuitPre|.  Can be used to close any
-				non-essential window.
 							*FileChangedShell*
 FileChangedShell		When Vim notices that the modification time of
 				a file has changed since editing started.
@@ -671,7 +601,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
@@ -682,7 +612,7 @@ FileChangedShell		When Vim notices that the modification time of
 				to tell Vim what to do next.
 				NOTE: When this autocommand is executed, the
 				current buffer "%" may be different from the
-				buffer that was changed, which is in "<afile>".
+				buffer that was changed "<afile>".
 				NOTE: The commands must not change the current
 				buffer, jump to another buffer or delete a
 				buffer.  *E246* *E811*
@@ -712,8 +642,7 @@ FileType			When the 'filetype' option has been set.  The
 				pattern is matched against the filetype.
 				<afile> can be used for the name of the file
 				where this option was set, and <amatch> for
-				the new value of 'filetype'.  Navigating to
-				another window or buffer is not allowed.
+				the new value of 'filetype'.
 				See |filetypes|.
 							*FileWriteCmd*
 FileWriteCmd			Before writing to a file, when not writing the
@@ -800,7 +729,7 @@ InsertCharPre			When a character is typed in Insert mode,
 				inserted literally.
 				It is not allowed to change the text |textlock|.
 				The event is not triggered when 'paste' is
-				set. {only with the +eval feature}
+				set.
 							*InsertEnter*
 InsertEnter			Just before starting Insert mode.  Also for
 				Replace mode and Virtual Replace mode.  The
@@ -878,7 +807,6 @@ QuitPre				When using `:quit`, `:wq` or `:qall`, before
 				or quits Vim.  Can be used to close any
 				non-essential window if the current window is
 				the last ordinary window.
-				Also see |ExitPre|.
 							*RemoteReply*
 RemoteReply			When a reply from a Vim that functions as
 				server was received |server2client()|.  The
@@ -947,7 +875,6 @@ SwapExists			Detected an existing swap file when starting
 				It is not allowed to change to another buffer,
 				change a buffer name or change directory
 				here.
-				{only available with the +eval feature}
 							*Syntax*
 Syntax				When the 'syntax' option has been set.  The
 				pattern is matched against the syntax name.
@@ -974,11 +901,6 @@ TermChanged			After the value of 'term' has changed.  Useful
 				for re-loading the syntax file to update the
 				colors, fonts and other terminal-dependent
 				settings.  Executed for all loaded buffers.
-							*TerminalOpen*
-TerminalOpen			Just after a terminal buffer was created, with
-				`:terminal` or |term_start()|. This event is
-				triggered even if the buffer is created
-				without a window, with the ++hidden option.
 							*TermResponse*
 TermResponse			After the response to |t_RV| is received from
 				the terminal.  The value of |v:termresponse|
@@ -1001,31 +923,6 @@ TextChangedI			After a change was made to the text in the
 				current buffer in Insert mode.
 				Not triggered when the popup menu is visible.
 				Otherwise the same as TextChanged.
-							*TextChangedP*
-TextChangedP			After a change was made to the text in the
-				current buffer in Insert mode, only when the
-				popup menu is visible.  Otherwise the same as
-				TextChanged.
-							*TextYankPost*
-TextYankPost			After text has been yanked or deleted in the
-				current buffer.  The following values of
-				|v:event| can be used to determine the operation
-				that triggered this autocmd:
-				   operator    	The operation performed.
-				   regcontents 	Text that was stored in the
-						register, as a list of lines,
-						like with: >
-						getreg(r, 1, 1)
-<				   regname	Name of the |register| or
-						empty string for the unnamed
-						register.
-				   regtype	Type of the register, see
-						|getregtype()|.
-				Not triggered when |quote_| is used nor when
-				called recursively.
-				It is not allowed to change the buffer text,
-				see |textlock|.
-				{only when compiled with the +eval feature}
 							*User*
 User				Never executed automatically.  To be used for
 				autocommands that are only executed with
@@ -1,4 +1,4 @@
-*change.txt*    For Vim version 8.0.  Last change: 2017 Feb 12
+*change.txt*    For Vim version 8.0.  Last change: 2016 Sep 11


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -635,14 +635,12 @@ For other systems the tmpnam() library function is used.
 			For the {pattern} see |pattern|.
 			{string} can be a literal string, or something
 			special; see |sub-replace-special|.
-							*E939*
 			When [range] and [count] are omitted, replace in the
-			current line only.  When [count] is given, replace in
-			[count] lines, starting with the last line in [range].
-			When [range] is omitted start in the current line.
-			[count] must be a positive number.  Also see
-			|cmdline-ranges|.
-
+			current line only.
+			When [count] is given, replace in [count] lines,
+			starting with the last line in [range].  When [range]
+			is omitted start in the current line.
+			Also see |cmdline-ranges|.
 			See |:s_flags| for [flags].

 :[range]s[ubstitute] [flags] [count]
@@ -686,7 +684,6 @@ g&			Synonym for `:%s//~/&` (repeat last substitute with
 							*:s_flags*
 The flags that you can use for the substitute commands:

-							*:&&*
 [&]	Must be the first one: Keep the flags from the previous substitute
 	command.  Examples: >
 		:&&
@@ -916,7 +913,8 @@ Exceptions:
 Substitute with an expression			*sub-replace-expression*
 						*sub-replace-\=* *s/\=*
 When the substitute string starts with "\=" the remainder is interpreted as an
-expression.
+expression.  This does not work recursively: a |substitute()| function inside
+the expression cannot use "\=" for the substitute string.

 The special meaning for characters as mentioned at |sub-replace-special| does
 not apply except for "<CR>".  A <NL> character is used as a line break, you
@@ -1,4 +1,4 @@
-*channel.txt*      For Vim version 8.0.  Last change: 2017 Aug 11
+*channel.txt*      For Vim version 8.0.  Last change: 2016 Sep 20


 		  VIM REFERENCE MANUAL	  by Bram Moolenaar
@@ -155,13 +155,7 @@ Use |ch_status()| to see if the channel could be opened.
 	func MyCloseHandler(channel)
 <		Vim will invoke callbacks that handle data before invoking
 		close_cb, thus when this function is called no more data will
-		be passed to the callbacks.
-							*channel-drop*
-"drop"		Specifies when to drop messages:
-		    "auto"	When there is no callback to handle a message.
-				The "close_cb" is also considered for this.
-		    "never"	All messages will be kept.
-
+		be received.
 							*waittime*
 "waittime"	The time to wait for the connection to be made in
 		milliseconds.  A negative number waits forever.
@@ -375,7 +369,7 @@ Leave out the fourth argument if no response is to be sent:
 ==============================================================================
 6. Using a RAW or NL channel				*channel-raw*

-If mode is RAW or NL then a message can be sent like this: >
+If mode is RAW or NL then a message can be send like this: >
    let response = ch_evalraw(channel, {string})

 The {string} is sent as-is.  The response will be what can be read from the
@@ -424,11 +418,7 @@ This uses the channel timeout.  To read without a timeout, just get any
 message that is available: >
 	let output = ch_read(channel, {'timeout': 0})
 When no message was available then the result is v:none for a JSON or JS mode
-channels, an empty string for a RAW or NL channel.  You can use |ch_canread()|
-to check if there is something to read.
-
-Note that when there is no callback, messages are dropped.  To avoid that add
-a close callback to the channel.
+channels, an empty string for a RAW or NL channel.

 To read all output from a RAW channel that is available: >
 	let output = ch_readraw(channel)
@@ -475,11 +465,6 @@ it like this: >
 Without the handler you need to read the output with |ch_read()| or
 |ch_readraw()|. You can do this in the close callback, see |read-in-close-cb|.

-Note that if the job exits before you read the output, the output may be lost.
-This depends on the system (on Unix this happens because closing the write end
-of a pipe causes the read end to get EOF).  To avoid this make the job sleep
-for a short while before it exits.
-
 The handler defined for "out_cb" will not receive stderr.  If you want to
 handle that separately, add an "err_cb" handler: >
    let job = job_start(command, {"out_cb": "MyHandler",
@@ -489,11 +474,6 @@ If you want to handle both stderr and stdout with one handler use the
 "callback" option: >
    let job = job_start(command, {"callback": "MyHandler"}) 

-Depending on the system, starting a job can put Vim in the background, the
-started job gets the focus.  To avoid that, use the `foreground()` function.
-This might not always work when called early, put in the callback handler or
-use a timer to call it after the job has started.
-
 You can send a message to the command with ch_evalraw().  If the channel is in
 JSON or JS mode you can use ch_evalexpr().

@@ -518,7 +498,7 @@ By default this reads the whole buffer.  This can be changed with the "in_top"
 and "in_bot" options.

 A special mode is when "in_top" is set to zero and "in_bot" is not set: Every
-time a line is added to the buffer, the last-but-one line will be sent to the
+time a line is added to the buffer, the last-but-one line will be send to the
 job stdin.  This allows for editing the last line and sending it when pressing
 Enter.
 							*channel-close-in*
@@ -536,7 +516,7 @@ If the job can take some time and you don't need intermediate results, you can
 add a close callback and read the output there: >

 	func! CloseHandler(channel)
-	  while ch_status(a:channel, {'part': 'out'}) == 'buffered'
+	  while ch_status(a:channel) == 'buffered'
 	    echomsg ch_read(a:channel)
 	  endwhile
 	endfunc
@@ -549,7 +529,7 @@ You will want to do something more useful than "echomsg".

 To start another process without creating a channel: >
    let job = job_start(command,
-	\ {"in_io": "null", "out_io": "null", "err_io": "null"})
+    	\ {"in_io": "null", "out_io": "null", "err_io": "null"})

 This starts {command} in the background, Vim does not wait for it to finish.

@@ -610,26 +590,21 @@ See |job_setoptions()| and |ch_setoptions()|.
 						*job-close_cb*
 "close_cb": handler	Callback for when the channel is closed.  Same as
 			"close_cb" on |ch_open()|, see |close_cb|.
-						*job-drop*
-"drop": when		Specifies when to drop messages.  Same as "drop" on
-			|ch_open()|, see |channel-drop|.  For "auto" the
-			exit_cb is not considered.
 						*job-exit_cb*
 "exit_cb": handler	Callback for when the job ends.  The arguments are the
 			job and the exit status.
-			Vim checks up to 10 times per second for jobs that
-			ended.  The check can also be triggered by calling
-			|job_status()|, which may then invoke the exit_cb
-			handler.
+			Vim checks about every 10 seconds for jobs that ended.
+			The check also be triggered by calling |job_status()|,
+			which may then invoke the exit_cb handler.
 			Note that data can be buffered, callbacks may still be
 			called after the process ends.
 							*job-timeout*
-"timeout": time		The time to wait for a request when blocking, E.g.
+"timeout"		The time to wait for a request when blocking, E.g.
 			when using ch_evalexpr().  In milliseconds.  The
 			default is 2000 (2 seconds).
 						*out_timeout* *err_timeout*
-"out_timeout": time	Timeout for stdout.  Only when using pipes.
-"err_timeout": time	Timeout for stderr.  Only when using pipes.
+"out_timeout"		Timeout for stdout.  Only when using pipes.
+"err_timeout"		Timeout for stderr.  Only when using pipes.
 			Note: when setting "timeout" the part specific mode is
 			overwritten.  Therefore set "timeout" first and the
 			part specific mode later.
@@ -641,23 +616,17 @@ See |job_setoptions()| and |ch_setoptions()|.
 			The default is "term".

 						*job-term*
-"term": "open"		Start a terminal in a new window and connect the job
-			stdin/stdout/stderr to it.  Similar to using
-			`:terminal`.
+"term": "open"		Start a terminal and connect the job
+			stdin/stdout/stderr to it.
 			NOTE: Not implemented yet!

 "channel": {channel}	Use an existing channel instead of creating a new one.
 			The parts of the channel that get used for the new job
 			will be disconnected from what they were used before.
-			If the channel was still used by another job this may
+			If the channel was still use by another job this may
 			cause I/O errors.
 			Existing callbacks and other settings remain.

-"pty": 1		Use a pty (pseudo-tty) instead of a pipe when
-			possible.  This is most useful in combination with a
-			terminal window, see |terminal|.
-			{only on Unix and Unix-like systems}
-
 				*job-in_io* *in_top* *in_bot* *in_name* *in_buf*
 "in_io": "null"		disconnect stdin (read from /dev/null)
 "in_io": "pipe"		stdin is connected to the channel (default)
@@ -672,7 +641,7 @@ See |job_setoptions()| and |ch_setoptions()|.
 "out_io": "null"	disconnect stdout (goes to /dev/null)
 "out_io": "pipe"	stdout is connected to the channel (default)
 "out_io": "file"	stdout writes to a file
-"out_io": "buffer"	stdout appends to a buffer (see below)
+"out_io": "buffer" 	stdout appends to a buffer (see below)
 "out_name": "/path/file" the name of the file or buffer to write to
 "out_buf": number	the number of the buffer to write to
 "out_modifiable": 0	when writing to a buffer, 'modifiable' will be off
@@ -685,7 +654,7 @@ See |job_setoptions()| and |ch_setoptions()|.
 "err_io": "null"	disconnect stderr  (goes to /dev/null)
 "err_io": "pipe"	stderr is connected to the channel (default)
 "err_io": "file"	stderr writes to a file
-"err_io": "buffer"	stderr appends to a buffer (see below)
+"err_io": "buffer" 	stderr appends to a buffer (see below)
 "err_name": "/path/file" the name of the file or buffer to write to
 "err_buf": number	the number of the buffer to write to
 "err_modifiable": 0	when writing to a buffer, 'modifiable' will be off
@@ -696,10 +665,6 @@ See |job_setoptions()| and |ch_setoptions()|.
 "block_write": number	only for testing: pretend every other write to stdin
 			will block

-"env": dict		environment variables for the new process
-"cwd": "/path/to/dir"	current working directory for the new process;
-			if the directory does not exist an error is given
-

 Writing to a buffer ~
 							*out_io-buffer*
@@ -735,6 +700,10 @@ The "out_msg" option can be used to specify whether a new buffer will have the
 first line set to "Reading from channel output...".  The default is to add the
 message.  "err_msg" does the same for channel error.

+'modifiable' option off, or write to a buffer that has 'modifiable' off.  That
+means that lines will be appended to the buffer, but the user can't easily
+change the buffer.
+
 When an existing buffer is to be written where 'modifiable' is off and the
 "out_modifiable" or "err_modifiable" options is not zero, an error is given
 and the buffer will not be written to.
@@ -1,4 +1,4 @@
-*cmdline.txt*   For Vim version 8.0.  Last change: 2017 Oct 19
+*cmdline.txt*   For Vim version 8.0.  Last change: 2016 Aug 27


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -229,10 +229,9 @@ CTRL-Y		When there is a modeless selection, copy the selection into
 		the clipboard. |modeless-selection|
 		If there is no selection CTRL-Y is inserted as a character.

-CTRL-M or CTRL-J		*c_CTRL-M* *c_CTRL-J* *c_<NL>* *c_<CR>* *c_CR*
+CTRL-J					*c_CTRL-J* *c_<NL>* *c_<CR>* *c_CR*
 <CR> or <NL>	start entered command
-
-CTRL-[						*c_CTRL-[* *c_<Esc>* *c_Esc*
+							*c_<Esc>* *c_Esc*
 <Esc>		When typed and 'x' not present in 'cpoptions', quit
 		Command-line mode without executing.  In macros or when 'x'
 		present in 'cpoptions', start entered command.
@@ -359,11 +358,8 @@ terminals)
 		List entries 6 to 12 from the search history: >
 			:history / 6,12
 <
-		List the penultimate entry from all histories: >
-			:history all -2
-<
-		List the most recent two entries from all histories: >
-			:history all -2,
+		List the recent five entries from all histories: >
+			:history all -5,

 :keepp[atterns] {command}			*:keepp* *:keeppatterns*
 		Execute {command}, without adding anything to the search
@@ -455,9 +451,6 @@ matches exactly one character.

 The 'wildignorecase' option can be set to ignore case in filenames.

-The 'wildmenu' option can be set to show the matches just above the command
-line.
-
 If you like tcsh's autolist completion, you can use this mapping:
 	:cnoremap X <C-L><C-D>
 (Where X is the command key to use, <C-L> is CTRL-L and <C-D> is CTRL-D)
@@ -826,21 +819,14 @@ Also see |`=|.
 			       *:<cword>* *:<cWORD>* *:<cfile>* *<cfile>*
 			       *:<sfile>* *<sfile>* *:<afile>* *<afile>*
 			       *:<abuf>* *<abuf>* *:<amatch>* *<amatch>*
-			       *:<cexpr>* *<cexpr>*
 			       *<slnum>* *E495* *E496* *E497* *E499* *E500*
 Note: these are typed literally, they are not special keys!
 	<cword>    is replaced with the word under the cursor (like |star|)
 	<cWORD>    is replaced with the WORD under the cursor (see |WORD|)
-	<cexpr>    is replaced with the word under the cursor, including more
-		   to form a C expression.  E.g., when the cursor is on "arg"
-		   of "ptr->arg" then the result is "ptr->arg"; when the
-		   cursor is on "]" of "list[idx]" then the result is
-		   "list[idx]".  This is used for |v:beval_text|.
 	<cfile>    is replaced with the path name under the cursor (like what
 		   |gf| uses)
 	<afile>    When executing autocommands, is replaced with the file name
-		   of the buffer being manipulated, or the file for a read or
-		   write.
+		   for a file read or write.
 	<abuf>     When executing autocommands, is replaced with the currently
 		   effective buffer number (for ":r file" and ":so file" it is
 		   the current buffer, the file being read/sourced is not in a
@@ -1070,10 +1056,10 @@ There are several ways to leave the command-line window:
 		Insert and in Normal mode.
 CTRL-C		Continue in Command-line mode.  The command-line under the
 		cursor is used as the command-line.  Works both in Insert and
-		in Normal mode.  There is no redraw, thus the window will
-		remain visible.
+		in Normal mode.  ":close" also works.  There is no redraw,
+		thus the window will remain visible.
 :quit		Discard the command line and go back to Normal mode.
-		":close", ":exit", ":xit" and CTRL-\ CTRL-N also work.
+		":exit", ":xit" and CTRL-\ CTRL-N also work.
 :qall		Quit Vim, unless there are changes in some buffer.
 :qall!		Quit Vim, discarding changes to any buffer.

@@ -1,4 +1,4 @@
-*debug.txt*     For Vim version 8.0.  Last change: 2017 Jul 15
+*debug.txt*     For Vim version 8.0.  Last change: 2012 Feb 11


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -53,7 +53,7 @@ Use this command to start Vim:
 	valgrind --log-file=valgrind.log --leak-check=full ./vim

 Note: Vim will run much slower.  If your .vimrc is big or you have several
-plugins you need to be patient for startup, or run with the "--clean"
+plugins you need to be patient for startup, or run with the "-u NONE"
 argument.

 There are often a few leaks from libraries, such as getpwuid() and
@@ -1,4 +1,4 @@
-*debugger.txt*  For Vim version 8.0.  Last change: 2017 Nov 21
+*debugger.txt*  For Vim version 8.0.  Last change: 2005 Mar 29


 		  VIM REFERENCE MANUAL    by Gordon Prieur
@@ -95,12 +95,10 @@ list and colors can be set via X resources (XmNballoonEvalFontList,
 XmNballoonEvalBackground, and XmNballoonEvalForeground).
 The 'balloondelay' option sets the delay before an attempt is made to show a
 balloon.
-The 'ballooneval' and/or the 'balloonevalterm' option needs to be set to
-switch it on.
+The 'ballooneval' option needs to be set to switch it on.

-Balloon evaluation is only available in the GUI when compiled with the
-|+balloon_eval| feature.  For the terminal the  |+balloon_eval_term| feature
-matters.
+Balloon evaluation is only available when compiled with the |+balloon_eval|
+feature.

 The Balloon evaluation functions are also used to show a tooltip for the
 toolbar.  The 'ballooneval' option does not need to be set for this.  But the
@@ -1,4 +1,4 @@
-*develop.txt*   For Vim version 8.0.  Last change: 2017 Jul 31
+*develop.txt*   For Vim version 8.0.  Last change: 2016 Jan 31


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -143,10 +143,9 @@ and its environment.

 VIM IS... NOT						*design-not*

- Vim is not a shell or an Operating System.  It does provide a terminal
-  window, in which you can run a shell or debugger.  E.g. to be able to do
-  this over an ssh connection.  But if you don't need a text editor with that
-  it is out of scope (use something like screen or tmux instead).
+- Vim is not a shell or an Operating System.  You will not be able to run a
+  shell inside Vim or use it to control a debugger.  This should work the
+  other way around: Use Vim as a component from a shell or in an IDE.
  A satirical way to say this: "Unlike Emacs, Vim does not attempt to include
  everything but the kitchen sink, but some people say that you can clean one
  with it.  ;-)"
@@ -178,7 +177,7 @@ The basic steps to make changes to the code:
 5. Make a patch with "git diff".  You can also create a pull request on
   github, but it's the diff that matters.
 6. Make a note about what changed, preferably mentioning the problem and the
-   solution.  Send an email to the |vim-dev| maillist with an explanation and
+   solution.  Send an email to the vim-dev maillist with an explanation and
   include the diff. Or create a pull request on github.


@@ -1,4 +1,4 @@
-*diff.txt*      For Vim version 8.0.  Last change: 2017 Oct 03
+*diff.txt*      For Vim version 8.0.  Last change: 2016 Aug 24


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -10,7 +10,7 @@ eight versions of the same file.

 The basics are explained in section |08.7| of the user manual.

-1. Starting diff mode		|start-vimdiff|
+1. Starting diff mode		|vimdiff|
 2. Viewing diffs		|view-diffs|
 3. Jumping to diffs		|jumpto-diffs|
 4. Copying diffs		|copy-diffs|
@@ -19,7 +19,7 @@ The basics are explained in section |08.7| of the user manual.
 {not in Vi}

 ==============================================================================
-1. Starting diff mode					*start-vimdiff*
+1. Starting diff mode

 The easiest way to start editing in diff mode is with the "vimdiff" command.
 This starts Vim as usual, and additionally sets up for viewing the differences
@@ -131,8 +131,6 @@ file for a moment and come back to the same file and be in diff mode again.
 		related options only happens in a window that has 'diff' set,
 		if the current window does not have 'diff' set then no options
 		in it are changed.
-		Hidden buffers are also removed from the list of diff'ed
-		buffers.

 The `:diffoff` command resets the relevant options to the values they had when
 using `:diffsplit`, `:diffpatch` , `:diffthis`. or starting Vim in diff mode.
@@ -166,8 +164,7 @@ The alignment of text will go wrong when:

 All the buffers edited in a window where the 'diff' option is set will join in
 the diff.  This is also possible for hidden buffers.  They must have been
-edited in a window first for this to be possible.  To get rid of the hidden
-buffers use `:diffoff!`.
+edited in a window first for this to be possible.

 					*:DiffOrig* *diff-original-file*
 Since 'diff' is a window-local option, it's possible to view the same buffer
@@ -226,8 +223,8 @@ The diffs are highlighted with these groups:
 				(searching from the end of the line).  The
 				text in between is highlighted.  This means
 				that parts in the middle that are still the
-				same are highlighted anyway.  The 'diffopt'
-				flags "iwhite" and "icase" are used here.
+				same are highlighted anyway.  Only "iwhite" of
+				'diffopt' is used here.
 |hl-DiffDelete|	DiffDelete	Deleted lines.  Also called filler lines,
 				because they don't really exist in this
 				buffer.
@@ -326,7 +323,7 @@ g:diff_translations to zero: >

    let g:diff_translations = 0
 <
-After setting this variable, reload the syntax script: >
+After setting this variable, Reload the syntax script: >

    set syntax=diff
 <
@@ -1,4 +1,4 @@
-*digraph.txt*   For Vim version 8.0.  Last change: 2016 Nov 04
+*digraph.txt*   For Vim version 8.0.  Last change: 2014 Jun 19


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -147,7 +147,7 @@ a standard meaning:
 	Two			2	Hook
 	Nine			9	Horn

-	Equals			=	Cyrillic (= used as second char)
+	Equals			=	Cyrillic (= used as second char) 
 	Asterisk		*	Greek
 	Percent sign		%	Greek/Cyrillic special
 	Plus			+	smalls: Arabic, capitals: Hebrew
@@ -926,7 +926,6 @@ char  digraph	hex	dec	official name ~
 †	/-	2020	8224	DAGGER
 ‡	/=	2021	8225	DOUBLE DAGGER
 ‥	..	2025	8229	TWO DOT LEADER
-…	,.	2026	8230	HORIZONTAL ELLIPSIS
 ‰	%0	2030	8240	PER MILLE SIGN
 ′	1'	2032	8242	PRIME
 ″	2'	2033	8243	DOUBLE PRIME
@@ -1,4 +1,4 @@
-*editing.txt*   For Vim version 8.0.  Last change: 2018 Feb 19
+*editing.txt*   For Vim version 8.0.  Last change: 2016 Aug 06


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -181,8 +181,7 @@ start editing another file, Vim will refuse this.  In order to overrule this
 protection, add a '!' to the command.  The changes will then be lost.  For
 example: ":q" will not work if the buffer was changed, but ":q!" will.  To see
 whether the buffer was changed use the "CTRL-G" command.  The message includes
-the string "[Modified]" if the buffer has been changed, or "+" if the 'm' flag
-is in 'shortmess'.
+the string "[Modified]" if the buffer has been changed.

 If you want to automatically save the changes without asking, switch on the
 'autowriteall' option.  'autowrite' is the associated Vi-compatible option
@@ -276,7 +275,7 @@ If you want to keep the changed buffer without saving it, switch on the

 							*:vie* *:view*
 :vie[w][!] [++opt] [+cmd] file
-			When used in Ex mode: Leave |Ex-mode|, go back to
+			When used in Ex mode: Leave |Ex mode|, go back to
 			Normal mode.  Otherwise same as |:edit|, but set
 			'readonly' option for this buffer.  {not in Vi}

@@ -617,16 +616,16 @@ list of the current window.
 			Also see |++opt| and |+cmd|.
 			{Vi: no ++opt}

-:[count]arge[dit][!] [++opt] [+cmd] {name} ..		*:arge* *:argedit*
-			Add {name}s to the argument list and edit it.
+:[count]arge[dit][!] [++opt] [+cmd] {name}		*:arge* *:argedit*
+			Add {name} to the argument list and edit it.
 			When {name} already exists in the argument list, this
 			entry is edited.
 			This is like using |:argadd| and then |:edit|.
-			Spaces in filenames have to be escaped with "\".
+			Note that only one file name is allowed, and spaces
+			inside the file name are allowed, like with |:edit|.
 			[count] is used like with |:argadd|.
-			If the current file cannot be |abandon|ed {name}s will
-			still be added to the argument list, but won't be
-			edited. No check for duplicates is done.
+			[!] is required if the current file cannot be
+			|abandon|ed.
 			Also see |++opt| and |+cmd|.
 			{not in Vi}

@@ -900,7 +899,7 @@ Note: When the 'write' option is off, you are not able to write any file.

 							*:w* *:write*
 						*E502* *E503* *E504* *E505*
-						*E512* *E514* *E667* *E796* *E949*
+						*E512* *E514* *E667* *E796*
 :w[rite] [++opt]	Write the whole buffer to the current file.  This is
 			the normal way to save changes to a file.  It fails
 			when the 'readonly' option is set or when there is
@@ -956,9 +955,6 @@ used, for example, when the write fails and you want to try again later with
 ":w #".  This can be switched off by removing the 'A' flag from the
 'cpoptions' option.

-Note that the 'fsync' option matters here.  If it's set it may make writes
-slower (but safer).
-
 							*:sav* *:saveas*
 :sav[eas][!] [++opt] {file}
 			Save the current buffer under the name {file} and set
@@ -980,12 +976,12 @@ WRITING WITH MULTIPLE BUFFERS				*buffer-write*

 							*:wa* *:wall*
 :wa[ll]			Write all changed buffers.  Buffers without a file
-			name cause an error message.  Buffers which are
-			readonly are not written. {not in Vi}
+			name or which are readonly are not written. {not in
+			Vi}

 :wa[ll]!		Write all changed buffers, even the ones that are
 			readonly.  Buffers without a file name are not
-			written and cause an error message. {not in Vi}
+			written. {not in Vi}


 Vim will warn you if you try to overwrite a file that has been changed
@@ -1112,7 +1108,6 @@ The names can be in upper- or lowercase.
 			window in the current tab page the current tab page is
 			closed |tab-page|.
 			Triggers the |QuitPre| autocommand event.
-			See |CTRL-W_q| for quitting another window.

 :conf[irm] q[uit]	Quit, but give prompt when changes have been made, or
 			the last file in the argument list has not been
@@ -1202,8 +1197,7 @@ MULTIPLE WINDOWS AND BUFFERS				*window-exit*
 :wqa[ll]! [++opt]
 :xa[ll]!	Write all changed buffers, even the ones that are readonly,
 		and exit Vim.  If there are buffers without a file name or
-		which cannot be written for another reason, or there is a
-		terminal with a running job, Vim will not quit.
+		which cannot be written for another reason, Vim will not quit.
 		{not in Vi}

 ==============================================================================
@@ -1333,11 +1327,9 @@ present in 'cpoptions' and "!" is not used in the command.
 :chd[ir][!] [path]	Same as |:cd|.

 							*:lc* *:lcd*
-:lc[d][!] {path}	Like |:cd|, but only set the current directory when
-			the cursor is in the current window.  The current
-			directory for other windows is not changed, switching
-			to another window will stop using {path}.
-			{not in Vi}
+:lc[d][!] {path}	Like |:cd|, but only set the current directory for the
+			current window.  The current directory for other
+			windows is not changed. {not in Vi}

 							*:lch* *:lchdir*
 :lch[dir][!]		Same as |:lcd|. {not in Vi}
@@ -1565,13 +1557,6 @@ If you want to automatically reload a file when it has been changed outside of
 Vim, set the 'autoread' option.  This doesn't work at the moment you write the
 file though, only when the file wasn't changed inside of Vim.

-If you do not want to be asked or automatically reload the file, you can use
-this: >
-	set buftype=nofile
-
-Or, when starting gvim from a shell: >
-	gvim file.log -c "set buftype=nofile"
-
 Note that if a FileChangedShell autocommand is defined you will not get a
 warning message or prompt.  The autocommand is expected to handle this.

@@ -1742,7 +1727,7 @@ There are three different types of searching:
   This searches the same directories, but in a different order.

   Note that completion for ":find", ":sfind", and ":tabfind" commands do not
-   currently work with 'path' items that contain a URL or use the double star
+   currently work with 'path' items that contain a url or use the double star
   with depth limiter (/usr/**2) or upward search (;) notations.

 vim:tw=78:ts=8:ft=help:norl:
@@ -1,4 +1,4 @@
-*filetype.txt*  For Vim version 8.0.  Last change: 2018 Feb 04
+*filetype.txt*  For Vim version 8.0.  Last change: 2016 Sep 09


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -43,7 +43,7 @@ Detail: The ":filetype on" command will load one of these files:
 	BufNewFile and BufRead events.  If the file type is not found by the
 	name, the file $VIMRUNTIME/scripts.vim is used to detect it from the
 	contents of the file.
-	When the GUI is running or will start soon, the |menu.vim| script is
+	When the GUI is running or will start soon, the menu.vim script is
 	also sourced.  See |'go-M'| about avoiding that.

 To add your own file types, see |new-filetype| below.  To search for help on a
@@ -353,12 +353,12 @@ define yourself.  There are a few ways to avoid this:
   You need to define your own mapping before the plugin is loaded (before
   editing a file of that type).  The plugin will then skip installing the
   default mapping.
-						*no_mail_maps*
+
 3. Disable defining mappings for a specific filetype by setting a variable,
   which contains the name of the filetype.  For the "mail" filetype this
   would be: >
 	:let no_mail_maps = 1
-<						*no_plugin_maps*
+
 4. Disable defining mappings for all filetypes by setting a variable: >
 	:let no_plugin_maps = 1
 <
@@ -573,8 +573,6 @@ Man {number} {name}

 Global mapping:
 <Leader>K	Displays the manual page for the word under the cursor.
-<Plug>ManPreGetPage  idem, allows for using a mapping: >
-			nmap <F1> <Plug>ManPreGetPage<CR>

 Local mappings:
 CTRL-]		Jump to the manual page for the word under the cursor.
@@ -602,17 +600,35 @@ MANPAGER				      *manpager.vim*
 The :Man command allows you to turn Vim into a manpager (that syntax highlights
 manpages and follows linked manpages on hitting CTRL-]).

-For bash,zsh,ksh or dash, add to the config file (.bashrc,.zshrc, ...)
+Works on:

-	export MANPAGER="vim -M +MANPAGER -"
+  - Linux
+  - Mac OS
+  - FreeBSD
+  - Cygwin
+  - Win 10 under Bash

-For (t)csh, add to the config file
+Untested:

-	setenv MANPAGER "vim -M +MANPAGER -"
+  - Amiga OS
+  - BeOS
+  - OS/2

-For fish, add to the config file
+For bash,zsh,ksh or dash by adding to the config file (.bashrc,.zshrc, ...)

-	set -x MANPAGER "vim -M +MANPAGER -"
+	export MANPAGER="env MAN_PN=1 vim -M +MANPAGER -"
+
+For (t)csh by adding to the config file
+
+	setenv MANPAGER "env MAN_PN=1 vim -M +MANPAGER -"
+
+For fish by adding to the config file
+
+	set -x MANPAGER "env MAN_PN=1 vim -M +MANPAGER -"
+
+If man sets the $MAN_PN environment variable, like man-db, the most common
+implementation on Linux and Mac OS, then the "env MAN_PN=1 " part above is
+superfluous.

 PDF							*ft-pdf-plugin*

@@ -635,7 +651,7 @@ By default the following options are set, in accordance with PEP8: >
 	setlocal expandtab shiftwidth=4 softtabstop=4 tabstop=8

 To disable this behaviour, set the following variable in your vimrc: >
-
+	
 	let g:python_recommended_style = 0


@@ -645,12 +661,6 @@ Since the text for this plugin is rather long it has been put in a separate
 file: |pi_spec.txt|.


-RUST							*ft-rust*
-
-Since the text for this plugin is rather long it has been put in a separate
-file: |ft_rust.txt|.
-
-
 SQL							*ft-sql*

 Since the text for this plugin is rather long it has been put in a separate
@@ -672,23 +682,4 @@ You can change the default by defining the variable g:tex_flavor to the format
 Currently no other formats are recognized.


-VIM							*ft-vim-plugin*
-
-The Vim filetype plugin defines mappings to move to the start and end of
-functions with [[ and ]].  Move around comments with ]" and [".
-
-The mappings can be disabled with: >
-	let g:no_vim_maps = 1
-
-
-ZIMBU							*ft-zimbu-plugin*
-
-The Zimbu filetype plugin defines mappings to move to the start and end of
-functions with [[ and ]].
-
-The mappings can be disabled with: >
-	let g:no_zimbu_maps = 1
-<
-
-
 vim:tw=78:ts=8:ft=help:norl:
@@ -1,4 +1,4 @@
-*fold.txt*      For Vim version 8.0.  Last change: 2017 Mar 18
+*fold.txt*      For Vim version 8.0.  Last change: 2016 Jan 02


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -64,7 +64,7 @@ whichever is lower.  These are empty or white lines and lines starting
 with a character in 'foldignore'.  White space is skipped before checking for
 characters in 'foldignore'.  For C use "#" to ignore preprocessor lines.

-When you want to ignore lines in another way, use the "expr" method.  The
+When you want to ignore lines in another way, use the 'expr' method.  The
 |indent()| function can be used in 'foldexpr' to get the indent of a line.


@@ -79,7 +79,7 @@ This will call a function to compute the fold level: >
 	:set foldexpr=MyFoldLevel(v:lnum)
 This will make a fold out of paragraphs separated by blank lines: >
 	:set foldexpr=getline(v:lnum)=~'^\\s*$'&&getline(v:lnum+1)=~'\\S'?'<1':1
-This does the same: >
+this does the same: >
 	:set foldexpr=getline(v:lnum-1)=~'^\\s*$'&&getline(v:lnum)=~'\\S'?'>1':1

 Note that backslashes must be used to escape characters that ":set" handles
@@ -139,7 +139,7 @@ fold level.  But note that foldlevel() may return -1 if the level is not known
 yet.  And it returns the level at the start of the line, while a fold might
 end in that line.

-It may happen that folds are not updated properly.  You can use |zx| or |zX|
+It may happened that folds are not updated properly.  You can use |zx| or |zX|
 to force updating folds.


@@ -203,7 +203,7 @@ and the level given by the marker:
 1. If a marker with the same fold level is encountered, the previous fold
   ends and another fold with the same level starts.
 2. If a marker with a higher fold level is found, a nested fold is started.
-3. If a marker with a lower fold level is found, all folds up to and including
+3. if a marker with a lower fold level is found, all folds up to and including
   this level end and a fold with the specified level starts.

 The number indicates the fold level.  A zero cannot be used (a marker with
@@ -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.
@@ -1,237 +0,0 @@
-*ft_rust.txt*      Filetype plugin for Rust
-
-==============================================================================
-CONTENTS                                                      *rust*
-
-1. Introduction                                                   |rust-intro|
-2. Settings                                                    |rust-settings|
-3. Commands                                                    |rust-commands|
-4. Mappings                                                    |rust-mappings|
-
-==============================================================================
-INTRODUCTION                                                      *rust-intro*
-
-This plugin provides syntax and supporting functionality for the Rust
-filetype.
-
-==============================================================================
-SETTINGS                                                       *rust-settings*
-
-This plugin has a few variables you can define in your vimrc that change the
-behavior of the plugin.
-
-                                                                *g:rustc_path*
-g:rustc_path~
-	Set this option to the path to rustc for use in the |:RustRun| and
-	|:RustExpand| commands. If unset, "rustc" will be located in $PATH: >
-	    let g:rustc_path = $HOME."/bin/rustc"
-<
-
-                                                  *g:rustc_makeprg_no_percent*
-g:rustc_makeprg_no_percent~
-	Set this option to 1 to have 'makeprg' default to "rustc" instead of
-	"rustc %": >
-	    let g:rustc_makeprg_no_percent = 1
-<
-
-                                                              *g:rust_conceal*
-g:rust_conceal~
-	Set this option to turn on the basic |conceal| support: >
-	    let g:rust_conceal = 1
-<
-
-                                                     *g:rust_conceal_mod_path*
-g:rust_conceal_mod_path~
-	Set this option to turn on |conceal| for the path connecting token
-	"::": >
-	    let g:rust_conceal_mod_path = 1
-<
-
-                                                          *g:rust_conceal_pub*
-g:rust_conceal_pub~
-	Set this option to turn on |conceal| for the "pub" token: >
-	    let g:rust_conceal_pub = 1
-<
-
-                                                     *g:rust_recommended_style*
-g:rust_recommended_style~
-        Set this option to enable vim indentation and textwidth settings to
-        conform to style conventions of the rust standard library (i.e. use 4
-        spaces for indents and sets 'textwidth' to 99). This option is enabled
-	by default. To disable it: >
-	    let g:rust_recommended_style = 0
-<
-
-                                                                 *g:rust_fold*
-g:rust_fold~
-	Set this option to turn on |folding|: >
-	    let g:rust_fold = 1
-<
-	Value		Effect ~
-	0		No folding
-	1		Braced blocks are folded. All folds are open by
-			default.
-	2		Braced blocks are folded. 'foldlevel' is left at the
-			global value (all folds are closed by default).
-
-                                                  *g:rust_bang_comment_leader*
-g:rust_bang_comment_leader~
-	Set this option to 1 to preserve the leader on multi-line doc comments
-	using the /*! syntax: >
-	    let g:rust_bang_comment_leader = 1
-<
-
-                                                 *g:ftplugin_rust_source_path*
-g:ftplugin_rust_source_path~
-	Set this option to a path that should be prepended to 'path' for Rust
-	source files: >
-	    let g:ftplugin_rust_source_path = $HOME.'/dev/rust'
-<
-
-                                                       *g:rustfmt_command*
-g:rustfmt_command~
-	Set this option to the name of the 'rustfmt' executable in your $PATH. If
-	not specified it defaults to 'rustfmt' : >
-	    let g:rustfmt_command = 'rustfmt'
-<
-                                                       *g:rustfmt_autosave*
-g:rustfmt_autosave~
-	Set this option to 1 to run |:RustFmt| automatically when saving a
-	buffer. If not specified it defaults to 0 : >
-	    let g:rustfmt_autosave = 0
-<
-                                                       *g:rustfmt_fail_silently*
-g:rustfmt_fail_silently~
-	Set this option to 1 to prevent 'rustfmt' from populating the
-	|location-list| with errors. If not specified it defaults to 0: >
-	    let g:rustfmt_fail_silently = 0
-<
-                                                       *g:rustfmt_options*
-g:rustfmt_options~
-	Set this option to a string of options to pass to 'rustfmt'. The
-	write-mode is already set to 'overwrite'. If not specified it
-	defaults to '' : >
-	    let g:rustfmt_options = ''
-<
-
-                                                          *g:rust_playpen_url*
-g:rust_playpen_url~
-	Set this option to override the URL for the playpen to use: >
-	    let g:rust_playpen_url = 'https://play.rust-lang.org/'
-<
-
-                                                        *g:rust_shortener_url*
-g:rust_shortener_url~
-	Set this option to override the URL for the URL shortener: >
-	    let g:rust_shortener_url = 'https://is.gd/'
-<
-
-
-==============================================================================
-COMMANDS                                                       *rust-commands*
-
-:RustRun  [args]                                                    *:RustRun*
-:RustRun! [rustc-args] [--] [args]
-		Compiles and runs the current file. If it has unsaved changes,
-		it will be saved first using |:update|. If the current file is
-		an unnamed buffer, it will be written to a temporary file
-		first. The compiled binary is always placed in a temporary
-		directory, but is run from the current directory.
-
-		The arguments given to |:RustRun| will be passed to the
-		compiled binary.
-
-		If ! is specified, the arguments are passed to rustc instead.
-		A "--" argument will separate the rustc arguments from the
-		arguments passed to the binary.
-
-		If |g:rustc_path| is defined, it is used as the path to rustc.
-		Otherwise it is assumed rustc can be found in $PATH.
-
-:RustExpand  [args]                                              *:RustExpand*
-:RustExpand! [TYPE] [args]
-		Expands the current file using --pretty and displays the
-		results in a new split. If the current file has unsaved
-		changes, it will be saved first using |:update|. If the
-		current file is an unnamed buffer, it will be written to a
-		temporary file first.
-
-		The arguments given to |:RustExpand| will be passed to rustc.
-		This is largely intended for specifying various --cfg
-		configurations.
-
-		If ! is specified, the first argument is the expansion type to
-		pass to rustc --pretty. Otherwise it will default to
-		"expanded".
-
-		If |g:rustc_path| is defined, it is used as the path to rustc.
-		Otherwise it is assumed rustc can be found in $PATH.
-
-:RustEmitIr [args]                                               *:RustEmitIr*
-		Compiles the current file to LLVM IR and displays the results
-		in a new split. If the current file has unsaved changes, it
-		will be saved first using |:update|. If the current file is an
-		unnamed buffer, it will be written to a temporary file first.
-
-		The arguments given to |:RustEmitIr| will be passed to rustc.
-
-		If |g:rustc_path| is defined, it is used as the path to rustc.
-		Otherwise it is assumed rustc can be found in $PATH.
-
-:RustEmitAsm [args]                                             *:RustEmitAsm*
-		Compiles the current file to assembly and displays the results
-		in a new split. If the current file has unsaved changes, it
-		will be saved first using |:update|. If the current file is an
-		unnamed buffer, it will be written to a temporary file first.
-
-		The arguments given to |:RustEmitAsm| will be passed to rustc.
-
-		If |g:rustc_path| is defined, it is used as the path to rustc.
-		Otherwise it is assumed rustc can be found in $PATH.
-
-:RustPlay                                                          *:RustPlay*
-		This command will only work if you have web-api.vim installed
-		(available at https://github.com/mattn/webapi-vim).  It sends the
-		current selection, or if nothing is selected, the entirety of the
-		current buffer to the Rust playpen, and emits a message with the
-		shortened URL to the playpen.
-
-		|g:rust_playpen_url| is the base URL to the playpen, by default
-		"https://play.rust-lang.org/".
-
-		|g:rust_shortener_url| is the base URL for the shortener, by
-		default "https://is.gd/"
-
-:RustFmt                                                       *:RustFmt*
-		Runs |g:rustfmt_command| on the current buffer. If
-		|g:rustfmt_options| is set then those will be passed to the
-		executable.
-
-		If |g:rustfmt_fail_silently| is 0 (the default) then it
-		will populate the |location-list| with the errors from
-		|g:rustfmt_command|. If |g:rustfmt_fail_silently| is set to 1
-		then it will not populate the |location-list|.
-
-:RustFmtRange                                                  *:RustFmtRange*
-		Runs |g:rustfmt_command| with selected range. See
-		|:RustFmt| for any other information.
-
-==============================================================================
-MAPPINGS                                                       *rust-mappings*
-
-This plugin defines mappings for |[[| and |]]| to support hanging indents.
-
-It also has a few other mappings:
-
-							*rust_<D-r>*
-<D-r>			Executes |:RustRun| with no arguments.
-			Note: This binding is only available in MacVim.
-
-							*rust_<D-R>*
-<D-R>			Populates the command line with |:RustRun|! using the
-			arguments given to the last invocation, but does not
-			execute it.
-			Note: This binding is only available in MacVim.
-
-==============================================================================
- vim:tw=78:sw=4:noet:ts=8:ft=help:norl:
@@ -1,4 +1,4 @@
-*gui.txt*       For Vim version 8.0.  Last change: 2018 Mar 06
+*gui.txt*       For Vim version 8.0.  Last change: 2014 Mar 08


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -67,7 +67,7 @@ When the GUI starts up initializations are carried out, in this order:
    executed as an Ex command.
  - If the user gvimrc file exists, it is sourced.  The name of this file is
    normally "$HOME/.gvimrc".  You can check this with ":version".
-  - For Win32, $HOME is set by Vim if needed, see |$HOME-windows|.
+  - For Win32, when $HOME is not set, "$VIM\_gvimrc" is used.
  - When a "_gvimrc" file is not found, ".gvimrc" is tried too.  And vice
    versa.
  The name of the first file found is stored in $MYGVIMRC, unless it was
@@ -79,8 +79,7 @@ When the GUI starts up initializations are carried out, in this order:
  and DOS/Win32 "_gvimrc" is tried first.

 NOTE: All but the first one are not carried out if Vim was started with
-"-u NONE" or "-u DEFAULTS" and no "-U" argument was given, or when started
-with "-U NONE".
+"-u NONE" and no "-U" argument was given, or when started with "-U NONE".

 All this happens AFTER the normal Vim initializations, like reading your
 .vimrc file.  See |initialization|.
@@ -134,7 +133,7 @@ task bar with the 'guiheadroom' option.
 :winp[os]
 		Display current position of the top left corner of the GUI vim
 		window in pixels.  Does not work in all versions.
-		Also see |getwinpos()|, |getwinposx()| and |getwinposy()|.
+		Also see |getwinposx()| and |getwinposy()|.

 :winp[os] {X} {Y}							*E466*
 		Put the GUI vim window at the given {X} and {Y} coordinates.
@@ -162,7 +161,7 @@ window Vim is running in with these commands: >
 							*gui-IME* *iBus*
 Input methods for international characters in X that rely on the XIM
 framework, most notably iBus, have been known to produce undesirable results
-in gvim. These may include an inability to enter spaces, or long delays
+in gVim. These may include an inability to enter spaces, or long delays
 between typing a character and it being recognized by the application.

 One workaround that has been successful, for unknown reasons, is to prevent
@@ -482,7 +481,6 @@ menus and menu items.  They are most useful for things that you can't remember
 what the key sequence was.

 For creating menus in a different language, see |:menutrans|.
-If you don't want to use menus at all, see |'go-M'|.

 							*menu.vim*
 The default menus are read from the file "$VIMRUNTIME/menu.vim".  See
@@ -499,22 +497,7 @@ in the menu (which can take a bit of time to load).  If you want to have all
 filetypes already present at startup, add: >
 	:let do_syntax_sel_menu = 1

-The following menuitems show all available color schemes, keymaps and compiler
-settings:
-	Edit > Color Scheme ~
-	Edit > Keymap ~
-	Tools > Set Compiler ~
-However, they can also take a bit of time to load, because they search all
-related files from the directories in 'runtimepath'.  Therefore they are
-loaded lazily (by the |CursorHold| event), or you can also load them manually.
-If you want to have all these items already present at startup, add: >
-	:let do_no_lazyload_menus = 1
-
-Note that the menu.vim is sourced when `:syntax on` or `:filetype on` is
-executed or after your .vimrc file is sourced.  This means that the 'encoding'
-option and the language of messages (`:language messages`) must be set before
-that (if you want to change them).
-
+<
 							*console-menus*
 Although this documentation is in the GUI section, you can actually use menus
 in console mode too.  You will have to load |menu.vim| explicitly then, it is
@@ -801,40 +784,10 @@ In the Win32 and GTK+ GUI, starting a menu name with ']' excludes that menu
 from the main menu bar.  You must then use the |:popup| or |:tearoff| command
 to display it.

-					*window-toolbar* *WinBar*
-Each window can have a local toolbar.  This uses the first line of the window,
-thus reduces the space for the text by one line.  The items in the toolbar
-must start with "WinBar".
-
-Only text can be used.  When using Unicode, special characters can be used to
-make the items look like icons.
-
-If the items do not fit then the last ones cannot be used.  The toolbar does
-not wrap.
-
-Note that Vim may be in any mode when executing these commands.  The menu
-should be defined for Normal mode and will be executed without changing the
-current mode. Thus if the current window is in Visual mode and the menu
-command does not intentionally change the mode, Vim will remain in Visual
-mode.  Best is to use `:nnoremenu` to avoid side effects.
-
-Example for debugger tools: >
-	nnoremenu 1.10 WinBar.Step :Step<CR>
-	nnoremenu 1.20 WinBar.Next :Next<CR>
-	nnoremenu 1.30 WinBar.Finish :Finish<CR>
-	nnoremenu 1.40 WinBar.Cont :Continue<CR>
-<
-The window toolbar uses the ToolbarLine and ToolbarButton highlight groups.
-
-When splitting the window the window toolbar is not copied to the new window.
-
 							*popup-menu*
 In the Win32, GTK+, Motif, Athena and Photon GUI, you can define the
 special menu "PopUp".  This is the menu that is displayed when the right mouse
 button is pressed, if 'mousemodel' is set to popup or popup_setpos.
-Example: >
-    nnoremenu 1.40 PopUp.&Paste	"+gP
-    menu PopUp


 5.3 Showing What Menus Are Mapped To			*showing-menus*
@@ -993,15 +946,10 @@ it behaves in a strange way.
 :popu[p] {name}			Popup the menu {name}.  The menu named must
 				have at least one subentry, but need not
 				appear on the menu-bar (see |hidden-menus|).
-				{only available for Win32, MacVim, and GTK GUI
-				or in the terminal when compiled with
-				+insert_expand}
+				{only available for Win32, MacVim, and GTK GUI}

 :popu[p]! {name}		Like above, but use the position of the mouse
 				pointer instead of the cursor.
-				In the terminal this is the last known
-				position, which is usually at the last click
-				or release (mouse movement is irrelevalt).

 Example: >
 	:popup File
@@ -1012,10 +960,6 @@ pointer if ! was used). >
 	:popup ]Toolbar
 This creates a popup menu that doesn't exist on the main menu-bar.

-Note that in the GUI the :popup command will return immediately, before a
-selection has been made.  In the terminal the commands waits for the user to
-make a selection.
-
 Note that a menu that starts with ']' will not be displayed.

 ==============================================================================
@@ -158,36 +158,55 @@ have files open in e.g. splits by changing the "Open files from applications"
 option in the General preference pane).  Finally, you can use Mac OS X System
 Services to open files in MacVim, see |macvim-services|.

-Use |mvim| script to start MacVim from Terminal.
-
-Or use the "open" command (this method can not be used to pass parameters to
+There are essentially two ways to start MacVim from Terminal: either call the
+Vim binary with the -g switch >
+	/Applications/MacVim.app/Contents/MacOS/Vim -g file ...
+or use the "open" command (this method can not be used to pass parameters to
 Vim) >
 	open -a MacVim file ...
 The advantage of using the latter method is that the settings relating to file
 opening in the preferences panel are respected, and files open instantly if
 |Quickstart| is enabled.

+To save yourself from having to type the entire path to the Vim binary each
+time you start MacVim, you could create an alias such as >
+	alias gvim='/Applications/MacVim.app/Contents/MacOS/Vim -g'
+and add that to "~/.profile".
+
+Note: Do NOT call the MacVim binary inside the app bundle to start MacVim.
+
+							*mvim*
+A more flexible way to start MacVim is to use the shell script "mvim" which
+comes bundled with MacVim.  Put this script in a folder in your path and then
+simply type "mvim" to start MacVim.  This script will try to find MacVim.app
+in various typical folders such as >
+	~/Applications              ~/Applications/vim
+	/Applications               /Applications/vim
+	/Applications/Utilities     /Applications/Utilities/vim
+If you would rather put MacVim.app in some other directory then that is also
+possible, simply set the environment variable VIM_APP_DIR to whatever folder
+you have placed MacVim.app in.
+
+The "mvim" script can be symlinked to in order to start up MacVim in different
+modes as follows (assuming you placed "mvim" in "/usr/local/bin"): >
+	* Diff:		ln -s /usr/local/bin/mvim mvimdiff
+	* Read-only:	ln -s /usr/local/bin/mvim mview
+	* Ex:		ln -s /usr/local/bin/mvim mex
+	* Restricted:	ln -s /usr/local/bin/mvim rmvim
+If the symlink destination starts with "m" (or "g"), Vim will start in GUI
+mode.  Removing the initial "m" from the above destination names makes Vim
+start without the GUI.  (In the last case, the destination name can be
+"rmvim", "rgvim" or "rvim".)
+
+Note: Starting MacVim by creating a symlink to >
+	.../MacVim.app/Contents/MacOS/Vim
+with 'ln -s' does not work.
+
 Once in terminal Vim it is possible to start MacVim by using the following
 command:
 	:gui [++opt] [+cmd] [-f|-b] [files...]
 Note: Forking ("-b") currently does not work.

-							*mvim*
-The "mvim" shell script bundled with MacVim. >
-	/Applications/MacVim.app/Contents/bin/mvim
-This is a wrapper script to launch Vim executable in the bundle.  Put this
-folder >
-	/Applications/MacVim.app/Contents/bin
-in your path and then simply type "mvim" to start MacVim from Terminal. >
-	$ mvim
-You can also specify files to open with. >
-	$ mvim file ...
-Also the bin folder has convenient scripts for diffing and opening file as the file is read-only. >
-	* Diff:		mvimdiff
-	* Read-only:	mview
-
-You can use "vim", "vimdiff", and "view" if you want to use non-GUI Vim.
-
 							*Quickstart*
 Quickstart ensures that new windows open instantaneously e.g. when <D-n> is
 pressed.  This feature can be enabled from the Advanced preferences pane (it
@@ -242,7 +261,6 @@ MMLoginShellArgument		login shell parameter [string]
 MMLoginShellCommand		which shell to use to launch Vim [string]
 MMNoFontSubstitution		disable automatic font substitution [bool]
 MMNoTitleBarWindow		hide title bar [bool]
-MMShareFindPboard		share search text to Find Pasteboard [bool]
 MMShowAddTabButton		enable "add tab" button on tabline [bool]
 MMTabMaxWidth			maximum width of a tab [int]
 MMTabMinWidth			minimum width of a tab [int]
@@ -686,7 +704,7 @@ prominent bugs/missing features.
 - The toolbar looks ugly and is not very useful.

 If you find new bugs then please post your findings to the vim_mac mailing
-list:							*vim_mac_group*   >
+list:							*vim_mac*   >
 	http://groups.google.com/group/vim_mac

 This is also the best place for making feature requests as well as for asking
@@ -1,4 +1,4 @@
-*gui_w32.txt*   For Vim version 8.0.  Last change: 2017 Oct 27
+*gui_w32.txt*   For Vim version 8.0.  Last change: 2014 Dec 20


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -49,6 +49,10 @@ If you want Vim to start with a maximized window, add this command to your
 vimrc or gvimrc file: >
 	au GUIEnter * simalt ~x
 <
+								*gui-w32s*
+There is a specific version of gvim.exe that runs under the Win32s subsystem
+of Windows 3.1 or 3.11.  See |win32s|.
+

 Using Vim as a plugin					*gui-w32-windowid*

@@ -96,10 +100,9 @@ when you have got a new version):
 You can also install Vim in the "Send To" menu:
 1. Start a Windows Explorer
 2. Navigate to your sendto directory:
+   Windows 95: %windir%\sendto (e.g. "c:\windows\sendto")
   Windows NT: %windir%\profiles\%user%\sendto (e.g.
-	       "c:\winnt\profiles\mattha\sendto")
-   Windows XP: C:\Documents and Settings\%user%\SendTo
-   Windows Vista: C:\Users\%user%\AppData\Roaming\Microsoft\Windows\SendTo .
+	       "c:\winnt\profiles\mattha\sendto").
 3. Right-click in the file pane and select New->Shortcut
 4. Follow the shortcut wizard, using the full path to VIM/GVIM.

@@ -271,17 +274,35 @@ WARNING: If you close this window with the "X" button, and confirm the
 question if you really want to kill the application, Vim may be killed too!
 (This does not apply to commands run asynchronously with ":!start".)

-The window in which the commands are executed will be the default you have set
-up for "Console" in Control Panel.
+In Windows 95, the window in which the commands are executed is always 25x80
+characters, to be as DOS compatible as possible (this matters!).  The default
+system font is used.  On NT, the window will be the default you have set up for
+"Console" in Control Panel.  On Win32s, the properties of the DOS box are
+determined by _default.pif in the windows directory.
+
+							*msdos-mode*
+If you get a dialog that says "This program is set to run in MS-DOS mode..."
+when you run an external program, you can solve this by changing the
+properties of the associated shortcut:
+- Use a Windows Explorer to find the command.com that is used.  It can be
+  c:\command.com, c:\dos\command.com, c:\windows\command.com, etc.
+- With the right mouse button, select properties of this command.com.
+- In the Program tab select "Advanced".
+- Unselect "MS-DOS mode".
+- Click "OK" twice.

 							*win32-!start*
 Normally, Vim waits for a command to complete before continuing (this makes
 sense for most shell commands which produce output for Vim to use).  If you
 want Vim to start a program and return immediately, you can use the following
-syntax: >
+syntax on W95 & NT: >
 	:!start [/min] {command}
 The optional "/min" causes the window to be minimized.

+On Win32s, you will have to go to another window instead.  Don't forget that
+you must tell Windows 3.1x to keep executing a DOS command in the background
+while you switch back to Vim.
+
 ==============================================================================
 5. Special colors					*win32-colors*

@@ -290,7 +311,7 @@ On Win32, the normal DOS colors can be used.  See |dos-colors|.
 Additionally the system configured colors can also be used.  These are known
 by the names Sys_XXX, where XXX is the appropriate system color name, from the
 following list (see the Win32 documentation for full descriptions).  Case is
-ignored.
+ignored.  Note: On Win32s not all of these colors are supported.

 Sys_3DDKShadow		Sys_3DFace			Sys_BTNFace
 Sys_3DHilight		Sys_3DHighlight			Sys_BTNHilight
@@ -382,8 +403,38 @@ Note that a menu that starts with ']' will not be displayed.
 ==============================================================================
 7. Command line arguments				*gui-w32-cmdargs*

-Command line arguments behave the same way as with the console application,
-see |win32-cmdargs|.
+Analysis of a command line into parameters is not standardised in MS Windows.
+Gvim has to provide logic to analyse a command line.  This logic is likely to
+be different from the default logic provided by a compilation system used to
+build vim.  The differences relate to unusual double quote (") usage.
+The arguments "C:\My Music\freude.txt" and "+/Sch\"iller" are handled in the
+same way.  The argument "+/Sch""iller" may be handled different by gvim and
+vim, depending what it was compiled with.
+
+The rules are:
+      a) A parameter is a sequence of graphic characters.
+      b) Parameters are separated by white space.
+      c) A parameter can be enclosed in double quotes to include white space.
+      d) A sequence of zero or more backslashes (\) and a double quote (")
+	is special.  The effective number of backslashes is halved, rounded
+	down.  An even number of backslashes reverses the acceptability of
+	spaces and tabs, an odd number of backslashes produces a literal
+	double quote.
+
+So:
+	"	is a special double quote
+	\"	is a literal double quote
+	\\"	is a literal backslash and a special double quote
+	\\\"	is a literal backslash and a literal double quote
+	\\\\"	is 2 literal backslashes and a special double quote
+	\\\\\"	is 2 literal backslashes and a literal double quote
+	etc.
+
+Example: >
+	gvim "C:\My Music\freude" +"set ignorecase" +/"\"foo\\" +\"bar\\\"
+
+opens "C:\My Music\freude" and executes the line mode commands: >
+	set ignorecase; /"foo\ and /bar\"

 ==============================================================================
 8. Various						*gui-w32-various*
@@ -1,4 +1,4 @@
-*gui_x11.txt*   For Vim version 8.0.  Last change: 2017 Jul 28
+*gui_x11.txt*   For Vim version 8.0.  Last change: 2016 Sep 12


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -288,9 +288,8 @@ For CDE "dtwm" (a derivative of Motif) add this line in the .Xdefaults: >
 For "mwm" (Motif window manager) the line would be: >
   Mwm*Vim*iconImage: /usr/local/share/vim/vim32x32.xpm

+Mouse Pointers Available in X11				*X11_mouse_shapes*

-Mouse Pointers Available in X11 ~
-						*X11_mouse_shapes*
 By using the |'mouseshape'| option, the mouse pointer can be automatically
 changed whenever Vim enters one of its various modes (e.g., Insert or
 Command).  Currently, the available pointers are:
@@ -364,9 +363,7 @@ to the GTK documentation, however little there is, on how to do this.
 See http://developer.gnome.org/doc/API/2.0/gtk/gtk-Resource-Files.html
 for more information.

-
-Tooltip Colors ~
-							*gtk-tooltip-colors*
+						*gtk-tooltip-colors*
 Example, which sets the tooltip colors to black on light-yellow: >

 	style "tooltips"
@@ -384,122 +381,15 @@ distribution.
 For GTK+ 3, an effect similar to the above can be obtained by adding the
 following snippet of CSS code to $XDG_HOME_DIR/gtk-3.0/gtk.css (usually,
 $HOME/.config/gtk-3.0/gtk.css):
-
-For GTK+ 3 < 3.20: >
-
+ >
 	.tooltip {
 		background-color: #ffffcc;
 		color: #000000;
 	}
 <
-For GTK+ 3 >= 3.20: >

-	tooltip {
-	    background-color: #ffffcc;
-	    text-shadow: none;
-	}
+Using Vim as a GTK+ plugin				*gui-gtk-socketid*

-	tooltip label {
-	    color: #2e3436;
-	}
-<
-
-A Quick Look at GTK+ CSS ~
-							*gtk-css*
-The contents of this subsection apply to GTK+ 3.20 or later which provides
-stable support for GTK+ CSS:
-
-	https://developer.gnome.org/gtk3/stable/theming.html
-
-GTK+ uses CSS for styling and layout of widgets.  In this subsection, we'll
-have a quick look at GTK+ CSS through simple, illustrative examples.
-
-Example 1.  Empty Space Adjustment ~
-
-By default, the toolbar and the tabline of the GTK+ 3 GUI are somewhat larger
-than those of the GTK+ 2 GUI.  Some people may want to make them look similar
-to the GTK+ 2 GUI in size.
-
-To do that, we'll try reducing empty space around icons and labels that looks
-apparently superfluous.
-
-Add the following lines to $XDG_HOME_DIR/gtk-3.0/gtk.css (usually,
-$HOME/.config/gtk-3.0/gtk.css): >
-
-	toolbar button {
-	    margin-top: -2px;
-	    margin-right: 0px;
-	    margin-bottom: -2px;
-	    margin-left: 0px;
-
-	    padding-top: 0px;
-	    padding-right: 0px;
-	    padding-bottom: 0px;
-	    padding-left: 0px
-	}
-
-	notebook tab {
-	    margin-top: -1px;
-	    margin-right: 3px;
-	    margin-bottom: -1px;
-	    margin-left: 3px;
-
-	    padding-top: 0px;
-	    padding-right: 0px;
-	    padding-bottom: 0px;
-	    padding-left: 0px
-	}
-<
-Since it's a CSS, they can be rewritten using shorthand: >
-
-	toolbar button {
-	    margin: -2px 0px;
-	    padding: 0px;
-	}
-
-	notebook tab {
-	    margin: -1px 3px;
-	    padding: 0px
-	}
-<
-Note: You might want to use 'toolbariconsize' to adjust the icon size, too.
-
-Note: Depending on the icon theme and/or the font in use, some extra tweaks
-may be needed for a satisfactory result.
-
-Note: In addition to margin and padding, you can use border.  For details,
-refer to the box model of CSS, e.g.,
-
-	https://www.w3schools.com/css/css_boxmodel.asp
-
-Example 2.  More Than Just Colors ~
-
-GTK+ CSS supports gradients as well: >
-
-	tooltip {
-	    background-image: -gtk-gradient(linear,
-					    0 0, 0 1,
-					    color-stop(0, #344752),
-					    color-stop(0.5, #546772),
-					    color-stop(1, #243742));
-	}
-
-	tooltip label {
-	    color: #f3f3f3;
-	}
-<
-Gradients can be used to make a GUI element visually distinguishable from
-others without relying on high contrast. Accordingly, effective use of them is
-a useful technique to give a theme a sense of unity in color and luminance.
-
-Note: Theming can be difficult since it must make every application look
-equally good; making a single application more charming often gets others
-unexpectedly less attractive or even deteriorates their usability.  Keep this
-in mind always when you try improving a theme.
-
-
-Using Vim as a GTK+ plugin ~
-							*gui-gtk-socketid*
 When the GTK+ version of Vim starts up normally, it creates its own top level
 window (technically, a 'GtkWindow').  GTK+ provides an embedding facility with
 its GtkSocket and GtkPlug widgets.  If one GTK+ application creates a
@@ -544,8 +434,8 @@ Note: Avoid use of --enable-gnome-check with GTK+ 3 GUI build.  The
 functionality mentioned above is consolidated in GTK+ 3.


-GNOME session support ~
-					*gui-gnome-session* *gnome-session*
+GNOME session support			*gui-gnome-session* *gnome-session*
+
 On logout, Vim shows the well-known exit confirmation dialog if any buffers
 are modified.  Clicking [Cancel] will stop the logout process.  Otherwise the
 current session is stored to disk by using the |:mksession| command, and
@@ -682,7 +572,7 @@ Of these three, Vim uses PRIMARY when reading and writing the "* register
 register.  Vim does not access the SECONDARY selection.

 Examples: (assuming the default option values)
- Select a URL in Visual mode in Vim.  Go to your browser and click the
+- Select an URL in Visual mode in Vim.  Go to your browser and click the
  middle mouse button in the URL text field.  The selected text will be
  inserted (hopefully!).  Note: in Firefox you can set the
  middlemouse.contentLoadURL preference to true in about:config, then the
@@ -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,12 +77,12 @@ $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
-font only in "font" setting for syntax.
+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
 in your .gvimrc, then you should do for syntax >
@@ -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
@@ -1,4 +1,4 @@
-*help.txt*	For Vim version 8.0.  Last change: 2017 Oct 28
+*help.txt*	For Vim version 8.0.  Last change: 2016 Sep 12

 			VIM - main help file
 									 k
@@ -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*
@@ -142,7 +142,6 @@ Special issues ~
 |print.txt|	printing
 |remote.txt|	using Vim as a server or client
 |term.txt|	using different terminals and mice
-|terminal.txt|	Terminal window support
 |digraph.txt|	list of available digraphs
 |mbyte.txt|	multi-byte text support
 |mlang.txt|	non-English language support
@@ -151,7 +150,6 @@ Special issues ~
 |hebrew.txt|	Hebrew language support and editing
 |russian.txt|	Russian language support and editing
 |ft_ada.txt|	Ada (the programming language) support
-|ft_rust.txt|	Filetype plugin for Rust
 |ft_sql.txt|	about the SQL filetype plugin
 |hangulin.txt|	Hangul (Korean) input mode
 |rileft.txt|	right-to-left editing mode
@@ -205,7 +203,6 @@ Standard plugins ~
 |pi_logipat.txt|   Logical operators on patterns
 |pi_netrw.txt|     Reading and writing files over a network
 |pi_paren.txt|     Highlight matching parens
-|pi_spec.txt|      Filetype plugin to work with rpm spec files
 |pi_tar.txt|       Tar file explorer
 |pi_vimball.txt|   Create a self-installing Vim script
 |pi_zip.txt|       Zip archive explorer
@@ -1,4 +1,4 @@
-*helphelp.txt*	For Vim version 8.0.  Last change: 2017 Mar 19
+*helphelp.txt*	For Vim version 8.0.  Last change: 2016 Apr 01


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -28,16 +28,10 @@ Help on help files					*helphelp*

 						*{subject}* *E149* *E661*
 :h[elp] {subject}	Like ":help", additionally jump to the tag {subject}.
-			For example:  >
-				:help options
-
-<			{subject} can include wildcards such as "*", "?" and
+			{subject} can include wildcards like "*", "?" and
 			"[a-z]":
 			   :help z?	jump to help for any "z" command
 			   :help z.	jump to the help for "z."
-			But when a tag exists it is taken literally:
-			   :help :?	jump to help for ":?"
-
 			If there is no full match for the pattern, or there
 			are several matches, the "best" match will be used.
 			A sophisticated algorithm is used to decide which
@@ -74,19 +68,18 @@ Help on help files					*helphelp*
 			example to find help for CTRL-V in Insert mode: >
 				:help i^V
 <
-			It is also possible to first do ":help" and then
+			To use a regexp |pattern|, first do ":help" and then
 			use ":tag {pattern}" in the help window.  The
 			":tnext" command can then be used to jump to other
 			matches, "tselect" to list matches and choose one. >
-				:help index
-				:tselect /.*mode
+				:help index| :tse z.

 <			When there is no argument you will see matches for
 			"help", to avoid listing all possible matches (that
 			would be very slow).
 			The number of matches displayed is limited to 300.

-			The `:help` command can be followed by '|' and another
+			This command can be followed by '|' and another
 			command, but you don't need to escape the '|' inside a
 			help command.  So these both work: >
 				:help |
@@ -142,8 +135,7 @@ Help on help files					*helphelp*
 			already opened, then the location list for that window
 			is used.  Otherwise, a new help window is opened and
 			the location list for that window is set.  The
-			location list for the current window is not changed
-			then.
+			location list for the current window is not changed.

 							*:exu* *:exusage*
 :exu[sage]		Show help on Ex commands.  Added to simulate the Nvi
@@ -315,7 +307,7 @@ the applicable Vim version.  The last field specifies the last modification
 date of the file.  Each field is separated by a tab.

 At the bottom of the help file, place a Vim modeline to set the 'textwidth'
-and 'tabstop' options and the 'filetype' to "help".  Never set a global option
+and 'tabstop' options and the 'filetype' to 'help'.  Never set a global option
 in such a modeline, that can have consequences undesired by whoever reads that
 help.

@@ -1,4 +1,4 @@
-*if_cscop.txt*  For Vim version 8.0.  Last change: 2018 Jan 21
+*if_cscop.txt*  For Vim version 8.0.  Last change: 2011 Jun 12


 		  VIM REFERENCE MANUAL    by Andy Kahn
@@ -91,10 +91,9 @@ suggested use.)
 2. Cscope related commands				*cscope-commands*

 		*:cscope* *:cs* *:scs* *:scscope* *E259* *E262* *E561* *E560*
-All cscope commands are accessed through suboptions to the cscope commands.
-	`:cscope` or `:cs` is the main command
-	`:scscope` or `:scs` does the same and splits the window
-	`:lcscope` or `:lcs` uses the location list, see |:lcscope|
+All cscope commands are accessed through suboptions to the main cscope
+command ":cscope".  The shortest abbreviation is ":cs".  The ":scscope"
+command does the same and also splits the window (short: "scs").

 The available subcommands are:

@@ -468,18 +467,36 @@ license or OS distribution), then you can download it for free from:
 	http://cscope.sourceforge.net/
 This is released by SCO under the BSD license.

+If you want a newer version of cscope, you will probably have to buy it.
+According to the (old) nvi documentation:
+
+	You can buy version 13.3 source with an unrestricted license
+	for $400 from AT&T Software Solutions by calling +1-800-462-8146.
+
+Also you can download cscope 13.x and mlcscope 14.x (multi-lingual cscope
+which supports C, C++, Java, lex, yacc, breakpoint listing, Ingres, and SDL)
+from World-Wide Exptools Open Source packages page:
+	http://www.bell-labs.com/project/wwexptools/packages.html
+
 In Solaris 2.x, if you have the C compiler license, you will also have
 cscope.  Both are usually located under /opt/SUNWspro/bin

+SGI developers can also get it.  Search for Cscope on this page:
+	http://freeware.sgi.com/index-by-alpha.html
+	https://toolbox.sgi.com/toolbox/utilities/cscope/
+The second one is for those who have a password for the SGI toolbox.
+
 There is source to an older version of a cscope clone (called "cs") available
 on the net.  Due to various reasons, this is not supported with Vim.

 The cscope interface/support for Vim was originally written by
 Andy Kahn <ackahn@netapp.com>.  The original structure (as well as a tiny
-bit of code) was adapted from the cscope interface in nvi.
+bit of code) was adapted from the cscope interface in nvi.  Please report
+any problems, suggestions, patches, et al., you have for the usage of
+cscope within Vim to him.
 							*cscope-win32*
-For a cscope version for Win32 see (seems abandoned):
-	https://code.google.com/archive/p/cscope-win32/
+For a cscope version for Win32 see:
+	http://code.google.com/p/cscope-win32/

 Win32 support was added by Sergey Khorev <sergey.khorev@gmail.com>.  Contact
 him if you have Win32-specific issues.
@@ -1,4 +1,4 @@
-*if_mzsch.txt*  For Vim version 8.0.  Last change: 2017 Oct 08
+*if_mzsch.txt*  For Vim version 8.0.  Last change: 2016 Jan 24


 		  VIM REFERENCE MANUAL    by Sergey Khorev
@@ -249,7 +249,7 @@ Windows							    *mzscheme-window*
 5. mzeval() Vim function				    *mzscheme-mzeval*

 To facilitate bi-directional interface, you can use |mzeval()| function to
-evaluate MzScheme expressions and pass their values to Vim script.
+evaluate MzScheme expressions and pass their values to VimL.

 ==============================================================================
 6. Using Function references				    *mzscheme-funcref*
@@ -278,15 +278,12 @@ When you don't use the MzScheme interface you don't need them, thus you can
 use Vim without these DLL files.
 NOTE: Newer version of MzScheme (Racket) require earlier (trampolined)
 initialisation via scheme_main_setup.  So Vim always loads the MzScheme DLL at
-startup if possible.  This may make Vim startup slower.
+startup if possible.

 To use the MzScheme interface the MzScheme DLLs must be in your search path.
 In a console window type "path" to see what directories are used.

-On MS-Windows the options 'mzschemedll' and 'mzschemegcdll' are used for the
-name of the library to load.  The initial value is specified at build time.
-
-The version of the DLL must match the MzScheme version Vim was compiled with.
+The names of the DLLs must match the MzScheme version Vim was compiled with.
 For MzScheme version 209 they will be "libmzsch209_000.dll" and
 "libmzgc209_000.dll". To know for sure look at the output of the ":version"
 command, look for -DDYNAMIC_MZSCH_DLL="something" and
@@ -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
@@ -1,4 +1,4 @@
-*if_perl.txt*   For Vim version 8.0.  Last change: 2017 Nov 24
+*if_perl.txt*   For Vim version 8.0.  Last change: 2015 Oct 16


 		  VIM REFERENCE MANUAL    by Sven Verdoolaege
@@ -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
@@ -112,7 +112,7 @@ possible.
 Here is an overview of the functions that are available to Perl: >

  :perl VIM::Msg("Text")		# displays a message
-  :perl VIM::Msg("Wrong!", "ErrorMsg")	# displays an error message
+  :perl VIM::Msg("Error", "ErrorMsg")	# displays an error message
  :perl VIM::Msg("remark", "Comment")	# displays a highlighted message
  :perl VIM::SetOption("ai")		# sets a vim option
  :perl $nbuf = VIM::Buffers()		# returns the number of buffers
@@ -1,4 +1,4 @@
-*if_pyth.txt*   For Vim version 8.0.  Last change: 2018 Jan 30
+*if_pyth.txt*   For Vim version 8.0.  Last change: 2016 Sep 17


 		  VIM REFERENCE MANUAL    by Paul Moore
@@ -16,8 +16,6 @@ The Python Interface to Vim				*python* *Python*
 8. pyeval(), py3eval() Vim functions		|python-pyeval|
 9. Dynamic loading				|python-dynamic|
 10. Python 3					|python3|
-11. Python X					|python_x|
-12. Building with Python support		|python-building|

 {Vi does not have any of these commands}

@@ -175,8 +173,8 @@ vim.eval(str)						*python-eval*

 	    :py tagList = vim.eval('taglist("eval_expr")')
 <	The latter will return a python list of python dicts, for instance:
-	[{'cmd': '/^eval_expr(arg, nextcmd)$/', 'static': 0, 'name': ~
-	'eval_expr', 'kind': 'f', 'filename': './src/eval.c'}] ~
+	[{'cmd': '/^eval_expr(arg, nextcmd)$/', 'static': 0, 'name':
+	'eval_expr', 'kind': 'f', 'filename': './src/eval.c'}]

 vim.bindeval(str)					*python-bindeval*
 	Like |python-eval|, but returns special objects described in 
@@ -677,11 +675,11 @@ vim.Function object				*python-Function*
                     dictionary. Note that explicit `self` keyword used when 
                     calling resulting object overrides this attribute.
        auto_rebind  Boolean. True if partial created from this Python object 
-                     and stored in the Vim script dictionary should be
-                     automatically rebound to the dictionary it is stored in
-                     when this dictionary is indexed. Exposes Vim internal
-                     difference between `dict.func` (auto_rebind=True) and
-                     `function(dict.func,dict)` (auto_rebind=False). This
+                     and stored in the VimL dictionary should be automatically 
+                     rebound to the dictionary it is stored in when this 
+                     dictionary is indexed. Exposes Vim internal difference 
+                     between `dict.func` (auto_rebind=True) and 
+                     `function(dict.func,dict)` (auto_rebind=False). This 
                     attribute makes no sense if `self` attribute is `None`.

    Constructor additionally accepts `args`, `self` and `auto_rebind` 
@@ -712,10 +710,7 @@ vim.Function object				*python-Function*
 8. pyeval() and py3eval() Vim functions			*python-pyeval*

 To facilitate bi-directional interface, you can use |pyeval()| and |py3eval()| 
-functions to evaluate Python expressions and pass their values to Vim script.
-|pyxeval()| is also available.
-
-The Python value "None" is converted to v:none.
+functions to evaluate Python expressions and pass their values to VimL.

 ==============================================================================
 9. Dynamic loading					*python-dynamic*
@@ -734,11 +729,9 @@ To use the Python interface the Python DLL must be in your search path.  In a
 console window type "path" to see what directories are used.  The 'pythondll'
 or 'pythonthreedll' option can be also used to specify the Python DLL.

-The name of the DLL should match the Python version Vim was compiled with.
-Currently the name for Python 2 is "python27.dll", that is for Python 2.7.
-That is the default value for 'pythondll'.  For Python 3 it is python36.dll
-(Python 3.6).  To know for sure edit "gvim.exe" and search for
-"python\d*.dll\c".
+The name of the DLL must match the Python version Vim was compiled with.
+Currently the name is "python24.dll".  That is for Python 2.4.  To know for
+sure edit "gvim.exe" and search for "python\d*.dll\c".


 Unix ~
@@ -809,8 +802,7 @@ Raising SystemExit exception in python isn't endorsed way to quit vim, use: >
 You can test what Python version is available with: >
 	if has('python')
 	  echo 'there is Python 2.x'
-	endif
-  	if has('python3')
+  	elseif has('python3')
 	  echo 'there is Python 3.x'
 	endif

@@ -819,109 +811,5 @@ dynamically, these has() calls will try to load them.  If only one can be
 loaded at a time, just checking if Python 2 or 3 are available will prevent
 the other one from being available.

-To avoid loading the dynamic library, only check if Vim was compiled with
-python support: >
-	if has('python_compiled')
-	  echo 'compiled with Python 2.x support'
-	  if has('python_dynamic')
-	    echo 'Python 2.x dynamically loaded'
-	  endif
-	endif
-  	if has('python3_compiled')
-	  echo 'compiled with Python 3.x support'
-	  if has('python3_dynamic')
-	    echo 'Python 3.x dynamically loaded'
-	  endif
-	endif
-
-This also tells you whether Python is dynamically loaded, which will fail if
-the runtime library cannot be found.
-
-==============================================================================
-11. Python X						*python_x* *pythonx*
-
-Because most python code can be written so that it works with python 2.6+ and
-python 3 the pyx* functions and commands have been written.  They work exactly
-the same as the Python 2 and 3 variants, but select the Python version using
-the 'pyxversion' setting.
-
-You should set 'pyxversion' in your |.vimrc| to prefer Python 2 or Python 3
-for Python commands. If you change this setting at runtime you may risk that
-state of plugins (such as initialization) may be lost.
-
-If you want to use a module, you can put it in the {rtp}/pythonx directory.
-See |pythonx-directory|.
-
-							*:pyx* *:pythonx*
-The `:pyx` and `:pythonx` commands work similar to `:python`.  A simple check
-if the `:pyx` command is working: >
-	:pyx print("Hello")
-
-To see what version of Python is being used: >
-	:pyx import sys
-	:pyx print(sys.version)
-<
-					*:pyxfile* *python_x-special-comments*
-The `:pyxfile` command works similar to `:pyfile`.  However you can add one of
-these comments to force Vim using `:pyfile` or `:py3file`: >
-  #!/any string/python2		" Shebang. Must be the first line of the file.
-  #!/any string/python3		" Shebang. Must be the first line of the file.
-  # requires python 2.x		" Maximum lines depend on 'modelines'.
-  # requires python 3.x		" Maximum lines depend on 'modelines'.
-Unlike normal modelines, the bottom of the file is not checked.
-If none of them are found, the 'pyxversion' setting is used.
-							*W20* *W21*
-If Vim does not support the selected Python version a silent message will be
-printed.  Use `:messages` to read them.
-
-							*:pyxdo*
-The `:pyxdo` command works similar to `:pydo`.
-
-							*has-pythonx*
-You can test if pyx* commands are available with: >
-	if has('pythonx')
-	  echo 'pyx* commands are available. (Python ' . &pyx . ')'
-	endif
-
-When compiled with only one of |+python| or |+python3|, the has() returns 1.
-When compiled with both |+python| and |+python3|, the test depends on the
-'pyxversion' setting.  If 'pyxversion' is 0, it tests Python 3 first, and if
-it is not available then Python 2.  If 'pyxversion' is 2 or 3, it tests only
-Python 2 or 3 respectively.
-
-Note that for `has('pythonx')` to work it may try to dynamically load Python 3
-or 2.  This may have side effects, especially when Vim can only load one of
-the two.
-
-If a user prefers Python 2 and want to fallback to Python 3, he needs to set
-'pyxversion' explicitly in his |.vimrc|.  E.g.: >
-	if has('python')
-	  set pyx=2
-	elseif has('python3')
-	  set pyx=3
-	endif
-
-==============================================================================
-12. Building with Python support			*python-building*
-
-A few hints for building with Python 2 or 3 support.
-
-UNIX
-
-See src/Makefile for how to enable including the Python interface.
-
-On Ubuntu you will want to install these packages for Python 2:
-	python
-	python-dev
-For Python 3:
-	python3
-	python3-dev
-For Python 3.6:
-	python3.6
-	python3.6-dev
-
-If you have more than one version of Python 3, you need to link python3 to the
-one you prefer, before running configure.
-
 ==============================================================================
 vim:tw=78:ts=8:ft=help:norl:
@@ -1,4 +1,4 @@
-*if_ruby.txt*   For Vim version 8.0.  Last change: 2018 Mar 15
+*if_ruby.txt*   For Vim version 8.0.  Last change: 2016 Sep 01


 		  VIM REFERENCE MANUAL    by Shugo Maeda
@@ -72,7 +72,7 @@ To see what version of Ruby you have: >

 							*:rubyfile* *:rubyf*
 :rubyf[ile] {file}	Execute the Ruby script in {file}.  This is the same as
-			`:ruby load 'file'`, but allows file name completion.
+			":ruby load 'file'", but allows file name completion.

 Executing Ruby commands is not possible in the |sandbox|.

@@ -207,22 +207,21 @@ MS-Windows ~

 You need to install the right version of Ruby for this to work.  You can find
 the package to download from:
-http://rubyinstaller.org/downloads/
-Currently that is rubyinstaller-2.2.5.exe
+http://www.garbagecollect.jp/ruby/mswin32/en/download/release.html
+Currently that is ruby-1.9.2-p136-i386-mswin32.zip

 To use the Ruby interface the Ruby DLL must be in your search path.  In a
 console window type "path" to see what directories are used.  The 'rubydll'
 option can be also used to specify the Ruby DLL.

 The name of the DLL must match the Ruby version Vim was compiled with.
-Currently the name is "msvcrt-ruby220.dll".  That is for Ruby 2.2.X.  To know
+Currently the name is "msvcrt-ruby191.dll".  That is for Ruby 1.9.1.  To know
 for sure edit "gvim.exe" and search for "ruby\d*.dll\c".

-If you want to build Vim with RubyInstaller 1.9 or 2.X using MSVC, you need
-some tricks.  See the src/INSTALLpc.txt for detail.
-
-If Vim is built with RubyInstaller 2.4 or later, you may also need to add
-"C:\Ruby<version>\bin\ruby_builtin_dlls" to the PATH environment variable.
+If you want to build Vim with Ruby 1.9.1, you need to edit the config.h file
+and comment-out the check for _MSC_VER.
+You may also need to rename the include directory name to match the version,
+strangely for Ruby 1.9.3 the directory is called 1.9.1.


 Unix ~
@@ -324,21 +324,6 @@ The examples below assume a 'shiftwidth' of 4.
 		  {                          {
 		      void function();       void function();
 		  }                          }
-<
-							*cino-E*
-	EN    Indent inside C++ linkage specifications (extern "C" or
-	      extern "C++") N characters extra compared to a normal block.
-	      (default 0).
-
-		cino=			   cino=E-s >
-		  extern "C" {               extern "C" {
-		      void function();       void function();
-		  }                          }
-
-		  extern "C"                 extern "C"
-		  {                          {
-		      void function();       void function();
-		  }                          }
 <
 							*cino-p*
 	pN    Parameter declarations for K&R-style function declarations will
@@ -569,7 +554,7 @@ The examples below assume a 'shiftwidth' of 4.


 The defaults, spelled out in full, are:
-	cinoptions=>s,e0,n0,f0,{0,}0,^0,L-1,:s,=s,l0,b0,gs,hs,N0,E0,ps,ts,is,+s,
+	cinoptions=>s,e0,n0,f0,{0,}0,^0,L-1,:s,=s,l0,b0,gs,hs,N0,ps,ts,is,+s,
 			c3,C0,/0,(2s,us,U0,w0,W0,k0,m0,j0,J0,)20,*70,#0

 Vim puts a line in column 1 if:
@@ -1,4 +1,4 @@
-*index.txt*     For Vim version 8.0.  Last change: 2017 Aug 02
+*index.txt*     For Vim version 8.0.  Last change: 2016 Aug 27


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -309,10 +309,10 @@ tag		char	      note action in Normal mode	~
 |B|		B		1  cursor N WORDS backward
 |C|		["x]C		2  change from the cursor position to the end
 				   of the line, and N-1 more lines [into
-				   register x]; synonym for "c$"
+				   buffer x]; synonym for "c$"
 |D|		["x]D		2  delete the characters under the cursor
 				   until the end of the line and N-1 more
-				   lines [into register x]; synonym for "d$"
+				   lines [into buffer x]; synonym for "d$"
 |E|		E		1  cursor forward to the end of WORD N
 |F|		F{char}		1  cursor to the Nth occurrence of {char} to
 				   the left
@@ -329,13 +329,13 @@ tag		char	      note action in Normal mode	~
 				   opposite direction
 |O|		O		2  begin a new line above the cursor and
 				   insert text, repeat N times
-|P|		["x]P		2  put the text [from register x] before the
+|P|		["x]P		2  put the text [from buffer x] before the
 				   cursor N times
 |Q|		Q		   switch to "Ex" mode
 |R|		R		2  enter replace mode: overtype existing
 				   characters, repeat the entered text N-1
 				   times
-|S|		["x]S		2  delete N lines [into register x] and start
+|S|		["x]S		2  delete N lines [into buffer x] and start
 				   insert; synonym for "cc".
 |T|		T{char}		1  cursor till after Nth occurrence of {char}
 				   to the left
@@ -343,8 +343,8 @@ tag		char	      note action in Normal mode	~
 |V|		V		   start linewise Visual mode
 |W|		W		1  cursor N WORDS forward
 |X|		["x]X		2  delete N characters before the cursor [into
-				   register x]
-|Y|		["x]Y		   yank N lines [into register x]; synonym for
+				   buffer x]
+|Y|		["x]Y		   yank N lines [into buffer x]; synonym for
 				   "yy"
 |ZZ|		ZZ		   store current file if modified, and exit
 |ZQ|		ZQ		   exit current file always
@@ -367,12 +367,12 @@ tag		char	      note action in Normal mode	~
 |`}|		`}		1  cursor to the end of the current paragraph
 |a|		a		2  append text after the cursor N times
 |b|		b		1  cursor N words backward
-|c|		["x]c{motion}	2  delete Nmove text [into register x] and
-				   start insert
-|cc|		["x]cc		2  delete N lines [into register x] and start
+|c|		["x]c{motion}	2  delete Nmove text [into buffer x] and start
 				   insert
-|d|		["x]d{motion}	2  delete Nmove text [into register x]
-|dd|		["x]dd		2  delete N lines [into register x]
+|cc|		["x]cc		2  delete N lines [into buffer x] and start
+				   insert
+|d|		["x]d{motion}	2  delete Nmove text [into buffer x]
+|dd|		["x]dd		2  delete N lines [into buffer x]
 |do|		do		2  same as ":diffget"
 |dp|		dp		2  same as ":diffput"
 |e|		e		1  cursor forward to the end of word N
@@ -398,16 +398,16 @@ tag		char	      note action in Normal mode	~
 |q?|		q?		   edit ? command-line in command-line window
 |r|		r{char}		2  replace N chars with {char}
 |s|		["x]s		2  (substitute) delete N characters [into
-				   register x] and start insert
+				   buffer x] and start insert
 |t|		t{char}		1  cursor till before Nth occurrence of {char}
 				   to the right
 |u|		u		2  undo changes
 |v|		v		   start characterwise Visual mode
 |w|		w		1  cursor N words forward
 |x|		["x]x		2  delete N characters under and after the
-				   cursor [into register x]
-|y|		["x]y{motion}	   yank Nmove text [into register x]
-|yy|		["x]yy		   yank N lines [into register x]
+				   cursor [into buffer x]
+|y|		["x]y{motion}	   yank Nmove text [into buffer x]
+|yy|		["x]yy		   yank N lines [into buffer x]
 |z|		z{char}		   commands starting with 'z', see |z| below
 |{|		{		1  cursor N paragraphs backward
 |bar|		|		1  cursor to column N
@@ -528,11 +528,8 @@ tag		command		   action in Normal mode	~
 |CTRL-W_CTRL-]|	CTRL-W CTRL-]	   same as "CTRL-W ]"
 |CTRL-W_CTRL-^|	CTRL-W CTRL-^	   same as "CTRL-W ^"
 |CTRL-W_CTRL-_|	CTRL-W CTRL-_	   same as "CTRL-W _"
-|CTRL-W_quote|	CTRL-W "	   terminal window: paste register
 |CTRL-W_+|	CTRL-W +	   increase current window height N lines
 |CTRL-W_-|	CTRL-W -	   decrease current window height N lines
-|CTRL-W_.|	CTRL-W .	   terminal window: type CTRL-W
-|CTRL-W_:|	CTRL-W :	   same as |:|, edit a command line
 |CTRL-W_<|	CTRL-W <	   decrease current window width N columns
 |CTRL-W_=|	CTRL-W =	   make all windows the same height & width
 |CTRL-W_>|	CTRL-W >	   increase current window width N columns
@@ -540,7 +537,6 @@ tag		command		   action in Normal mode	~
 |CTRL-W_J|	CTRL-W J	   move current window to the very bottom
 |CTRL-W_K|	CTRL-W K	   move current window to the very top
 |CTRL-W_L|	CTRL-W L	   move current window to the far right
-|CTRL-W_N|	CTRL-W N	   terminal window: go to Terminal Normal mode
 |CTRL-W_P|	CTRL-W P	   go to preview window
 |CTRL-W_R|	CTRL-W R	   rotate windows upwards N times
 |CTRL-W_S|	CTRL-W S	   same as "CTRL-W s"
@@ -1006,14 +1002,12 @@ tag		command	      action in Command-line editing mode	~
 |c_CTRL-L|	CTRL-L		do completion on the pattern in front of the
 				cursor and insert the longest common part
 |c_<CR>|	<CR>		execute entered command
-|c_CTRL-M|	CTRL-M		same as <CR>
+|c_<CR>|	CTRL-M		same as <CR>
 |c_CTRL-N|	CTRL-N		after using 'wildchar' with multiple matches:
-				go to next match, otherwise: recall older
-				command-line from history.
+				go to next match, otherwise: same as <Down>
 		CTRL-O		not used
 |c_CTRL-P|	CTRL-P		after using 'wildchar' with multiple matches:
-				go to previous match, otherwise: recall older
-				command-line from history.
+				go to previous match, otherwise: same as <Up>
 |c_CTRL-Q|	CTRL-Q		same as CTRL-V, unless it's used for terminal
 				control flow
 |c_CTRL-R|	CTRL-R {0-9a-z"%#*:= CTRL-F CTRL-P CTRL-W CTRL-A}
@@ -1032,7 +1026,7 @@ tag		command	      action in Command-line editing mode	~
 		CTRL-Y		copy (yank) modeless selection
 		CTRL-Z		not used (reserved for suspend)
 |c_<Esc>|	<Esc>		abandon command-line without executing it
-|c_CTRL-[|	CTRL-[		same as <Esc>
+|c_<Esc>|	CTRL-[		same as <Esc>
 |c_CTRL-\_CTRL-N| CTRL-\ CTRL-N	go to Normal mode, abandon command-line
 |c_CTRL-\_CTRL-G| CTRL-\ CTRL-G	go to mode specified with 'insertmode',
 				abandon command-line
@@ -1448,10 +1442,6 @@ tag	      command	      action ~
 |:python|	:py[thon]	execute Python command
 |:pydo|		:pyd[o]		execute Python command for each line
 |:pyfile|	:pyf[ile]	execute Python script file
-|:pyx|		:pyx		execute |python_x| command
-|:pythonx|	:pythonx	same as :pyx
-|:pyxdo|	:pyxd[o]	execute |python_x| command for each line
-|:pyxfile|	:pyxf[ile]	execute |python_x| script file
 |:quit|		:q[uit]		quit current window (when one window quit Vim)
 |:quitall|	:quita[ll]	quit Vim
 |:qall|		:qa[ll]		quit Vim
@@ -1579,23 +1569,18 @@ tag	      command	      action ~
 |:tcldo|	:tcld[o]	execute Tcl command for each line
 |:tclfile|	:tclf[ile]	execute Tcl script file
 |:tearoff|	:te[aroff]	tear-off a menu
-|:terminal|	:ter[minal]	open a terminal window
 |:tfirst|	:tf[irst]	jump to first matching tag
 |:throw|	:th[row]	throw an exception
 |:tjump|	:tj[ump]	like ":tselect", but jump directly when there
 				is only one match
 |:tlast|	:tl[ast]	jump to last matching tag
-|:tmapclear|	:tmapc[lear]	remove all mappings for Terminal-Job mode
-|:tmap|		:tma[p]		like ":map" but for Terminal-Job mode
 |:tmenu|	:tm[enu]	define menu tooltip
 |:tnext|	:tn[ext]	jump to next matching tag
-|:tnoremap|	:tno[remap]	like ":noremap" but for Terminal-Job mode
 |:topleft|	:to[pleft]	make split window appear at top or far left
 |:tprevious|	:tp[revious]	jump to previous matching tag
 |:trewind|	:tr[ewind]	jump to first matching tag
 |:try|		:try		execute commands, abort on error or exception
 |:tselect|	:ts[elect]	list matching tags and select one
-|:tunmap|	:tunma[p]	like ":unmap" but for Terminal-Job mode
 |:tunmenu|	:tu[nmenu]	remove menu tooltip
 |:undo|		:u[ndo]		undo last change(s)
 |:undojoin|	:undoj[oin]	join next change with previous undo block
@@ -1,4 +1,4 @@
-*insert.txt*    For Vim version 8.0.  Last change: 2018 Feb 10
+*insert.txt*    For Vim version 8.0.  Last change: 2016 Jan 31


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -159,8 +159,7 @@ CTRL-R CTRL-R {0-9a-z"%#*+/:.-=}			*i_CTRL-R_CTRL-R*
 CTRL-R CTRL-O {0-9a-z"%#*+/:.-=}			*i_CTRL-R_CTRL-O*
 		Insert the contents of a register literally and don't
 		auto-indent.  Does the same as pasting with the mouse
-		|<MiddleMouse>|. When the register is linewise this will
-		insert the text above the current line, like with `P`.
+		|<MiddleMouse>|.
 		Does not replace characters!
 		The '.' register (last inserted text) is still inserted as
 		typed.  {not in Vi}
@@ -433,7 +432,7 @@ An example for using CTRL-G U: >
 	inoremap ( ()<C-G>U<Left>

 This makes it possible to use the cursor keys in Insert mode, without breaking
-the undo sequence and therefore using |.| (redo) will work as expected.
+the undo sequence and therefore using |.| (redo) will work as expected. 
 Also entering a text like (with the "(" mapping from above): >

   Lorem ipsum (dolor
@@ -634,13 +633,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| |i_CTRL-P|
+13. keywords in 'complete'				|i_CTRL-N|

-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).
+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).

 Also see the 'infercase' option if you want to adjust the case of the match.

@@ -1103,10 +1102,8 @@ items:
 			item with the same word is already present.
 	empty		when non-zero this match will be added even when it is
 			an empty string
-	user_data 	custom data which is associated with the item and
-			available in |v:completed_item|

-All of these except "icase", "dup" and "empty" must be a string.  If an item
+All of these except 'icase', 'dup' and 'empty' must be a string.  If an item
 does not meet these requirements then an error message is given and further
 items in the list are not used.  You can mix string and Dictionary items in
 the returned list.
@@ -1198,8 +1195,6 @@ The menu is used when:

 The 'pumheight' option can be used to set a maximum height.  The default is to
 use all space available.
-The 'pumwidth' option can be used to set a minimum width.  The default is 15
-characters.

 There are three states:
 1. A complete match has been inserted, e.g., after using CTRL-N or CTRL-P.
@@ -1300,8 +1295,7 @@ it here: http://ctags.sourceforge.net/  Version 5.6 or later is recommended.
 For version 5.5.4 you should add a patch that adds the "typename:" field:
 	ftp://ftp.vim.org/pub/vim/unstable/patches/ctags-5.5.4.patch
 A compiled .exe for MS-Windows can be found at:
-	http://ctags.sourceforge.net/
-	https://github.com/universal-ctags/ctags-win32
+	http://georgevreilly.com/vim/ctags.html

 If you want to complete system functions you can do something like this.  Use
 ctags to generate a tags file for all the system header files: >
@@ -1477,7 +1471,7 @@ The completions provided by CTRL-X CTRL-O are sensitive to the context:

 Notes:
 - Vim will load/evaluate code in order to provide completions.  This may
-   cause some code execution, which may be a concern. This is no longer
+   cause some code execution, which may be a concern. This is no longer 
   enabled by default, to enable this feature add >
     let g:rubycomplete_buffer_loading = 1
 <- In context 1 above, Vim can parse the entire buffer to add a list of
@@ -1533,15 +1527,15 @@ that begin with the filetype, "php", in this case.  For example these syntax
 groups are included by default with the PHP: phpEnvVar, phpIntVar,
 phpFunctions.

-If you wish non-filetype syntax items to also be included, you can use a
-regular expression syntax (added in version 13.0 of
-autoload\syntaxcomplete.vim) to add items.  Looking at the output from
-":syntax list" while editing a PHP file I can see some of these entries: >
+If you wish non-filetype syntax items to also be included, you can use a 
+regular expression syntax (added in version 13.0 of autoload\syntaxcomplete.vim)
+to add items.  Looking at the output from ":syntax list" while editing a PHP file 
+I can see some of these entries: >
    htmlArg,htmlTag,htmlTagName,javaScriptStatement,javaScriptGlobalObjects

 To pick up any JavaScript and HTML keyword syntax groups while editing a PHP
-file, you can use 3 different regexs, one for each language.  Or you can
-simply restrict the include groups to a particular value, without using
+file, you can use 3 different regexs, one for each language.  Or you can 
+simply restrict the include groups to a particular value, without using 
 a regex string: >
    let g:omni_syntax_group_include_php = 'php\w\+,javaScript\w\+,html\w\+'
    let g:omni_syntax_group_include_php = 'phpFunctions,phpMethods'
@@ -1554,9 +1548,9 @@ highlight.  These items will be available within the omni completion list.

 Some people may find this list unwieldy or are only interested in certain
 items.  There are two ways to prune this list (if necessary).  If you find
-certain syntax groups you do not wish displayed you can use two different
-methods to identify these groups.  The first specifically lists the syntax
-groups by name.  The second uses a regular expression to identify both
+certain syntax groups you do not wish displayed you can use two different 
+methods to identify these groups.  The first specifically lists the syntax 
+groups by name.  The second uses a regular expression to identify both 
 syntax groups.  Simply add one the following to your vimrc: >
    let g:omni_syntax_group_exclude_php = 'phpCoreConstant,phpConstant'
    let g:omni_syntax_group_exclude_php = 'php\w*Constant'
@@ -1579,22 +1573,22 @@ vimrc: >

 For plugin developers, the plugin exposes a public function OmniSyntaxList.
 This function can be used to request a List of syntax items.  When editing a
-SQL file (:e syntax.sql) you can use the ":syntax list" command to see the
+SQL file (:e syntax.sql) you can use the ":syntax list" command to see the 
 various groups and syntax items.  For example: >
-    syntax list
+    syntax list 

-Yields data similar to this:
-    sqlOperator    xxx some prior all like and any escape exists in is not ~
-                       or intersect minus between distinct ~
-                       links to Operator ~
-    sqlType        xxx varbit varchar nvarchar bigint int uniqueidentifier ~
-                       date money long tinyint unsigned xml text smalldate ~
-                       double datetime nchar smallint numeric time bit char ~
-                       varbinary binary smallmoney ~
-                       image float integer timestamp real decimal ~
+Yields data similar to this: >
+    sqlOperator    xxx some prior all like and any escape exists in is not 
+                       or intersect minus between distinct
+                       links to Operator
+    sqlType        xxx varbit varchar nvarchar bigint int uniqueidentifier 
+                       date money long tinyint unsigned xml text smalldate 
+                       double datetime nchar smallint numeric time bit char 
+                       varbinary binary smallmoney
+                       image float integer timestamp real decimal

 There are two syntax groups listed here: sqlOperator and sqlType.  To retrieve
-a List of syntax items you can call OmniSyntaxList a number of different
+a List of syntax items you can call OmniSyntaxList a number of different 
 ways.  To retrieve all syntax items regardless of syntax group:  >
    echo OmniSyntaxList( [] )

@@ -1611,6 +1605,7 @@ From within a plugin, you would typically assign the output to a List: >
    let myKeywords = []
    let myKeywords = OmniSyntaxList( ['sqlKeyword'] )

+    

 SQL							*ft-sql-omni*

@@ -1,4 +1,4 @@
-*intro.txt*     For Vim version 8.0.  Last change: 2018 Jan 24
+*intro.txt*     For Vim version 8.0.  Last change: 2016 Sep 24


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -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


@@ -96,18 +96,21 @@ mention that.

 						*mail-list* *maillist*
 There are several mailing lists for Vim:
-<vim@vim.org>					*vim-use* *vim_use*
+<vim@vim.org>
 	For discussions about using existing versions of Vim: Useful mappings,
 	questions, answers, where to get a specific version, etc.  There are
 	quite a few people watching this list and answering questions, also
 	for beginners.  Don't hesitate to ask your question here.
-<vim-dev@vim.org>				*vim-dev* *vim_dev* *vimdev*
+<vim-dev@vim.org>				*vim-dev* *vimdev*
 	For discussions about changing Vim: New features, porting, patches,
 	beta-test versions, etc.
-<vim-announce@vim.org>				*vim-announce* *vim_announce*
+<vim-announce@vim.org>				*vim-announce*
 	Announcements about new versions of Vim; also for beta-test versions
 	and ports to different systems.  This is a read-only list.
-<vim-mac@vim.org>				*vim-mac* *vim_mac*
+<vim-multibyte@vim.org>				*vim-multibyte*
+	For discussions about using and improving the multi-byte aspects of
+	Vim.
+<vim-mac@vim.org>				*vim-mac*
 	For discussions about using and improving the Macintosh version of
 	Vim.

@@ -138,19 +141,14 @@ There are two ways to report bugs, both work:
   see the message.  If you don't want that, e.g. because it is a security
   issue, send it to <bugs@vim.org>, this only goes to the Vim maintainer
   (that's Bram).
-2. Open an issue on GitHub: https://github.com/vim/vim/issues
+2. Open issue on GitHub: https://github.com/vim/vim/issues
   The text will be forwarded to the vim-dev maillist.

 Please be brief; all the time that is spent on answering mail is subtracted
 from the time that is spent on improving Vim!  Always give a reproducible
-example and try to find out which settings or other things trigger the bug.
-
-Preferably start Vim with: >
-	vim --clean -u reproduce.vim
-Where reproduce.vim is a script that reproduces the problem.  Try different
-machines, if relevant (is this an MS-Windows specific bug perhaps?).
-
-Send me patches if you can!
+example and try to find out which settings or other things influence the
+appearance of the bug.  Try different machines, if possible.  Send me patches
+if you can!

 It will help to include information about the version of Vim you are using and
 your setup.  You can get the information with this command: >
@@ -264,10 +262,6 @@ Vim would never have become what it is now, without the help of these people!
 	Juergen Weigert		Lattice version, AUX improvements, UNIX and
 				MS-DOS ports, autoconf
 	Stefan 'Sec' Zehl	Maintainer of vim.org
-	Yasuhiro Matsumoto	many MS-Windows improvements
-	Ken Takata		fixes and features
-	Kazunobu Kuriyama	GTK 3
-	Christian Brabandt	many fixes, features, user support, etc.

 I wish to thank all the people that sent me bug reports and suggestions.  The
 list is too long to mention them all here.  Vim would not be the same without
@@ -534,7 +528,7 @@ examples and use them directly.  Or type them literally, including the '<' and
 ==============================================================================
 5. Modes, introduction				*vim-modes-intro* *vim-modes*

-Vim has seven BASIC modes:
+Vim has six BASIC modes:

 					*Normal* *Normal-mode* *command-mode*
 Normal mode		In Normal mode you can enter all the normal editor
@@ -570,12 +564,7 @@ Ex mode			Like Command-line mode, but after entering a command
 			you remain in Ex mode.  Very limited editing of the
 			command line.  |Ex-mode|

-Terminal-Job mode	Interacting with a job in a terminal window.  Typed
-			keys go to the job and the job output is displayed in
-			the terminal window.  See |terminal| about how to
-			switch to other modes.
-
-There are seven ADDITIONAL modes.  These are variants of the BASIC modes:
+There are six ADDITIONAL modes.  These are variants of the BASIC modes:

 				*Operator-pending* *Operator-pending-mode*
 Operator-pending mode	This is like Normal mode, but after an operator
@@ -601,10 +590,6 @@ Insert Normal mode	Entered when CTRL-O given in Insert mode.  This is
 			If the 'showmode' option is on "-- (insert) --" is
 			shown at the bottom of the window.

-Terminal-Normal mode	Using Normal mode in a terminal window.  Making
-			changes is impossible.  Use an insert command, such as
-			"a" or "i", to return to Terminal-Job mode.
-
 Insert Visual mode	Entered when starting a Visual selection from Insert
 			mode, e.g., by using CTRL-O and then "v", "V" or
 			CTRL-V.  When the Visual selection ends, Vim returns
@@ -679,8 +664,6 @@ Normal mode from any other mode.  This can be used to make sure Vim is in
 Normal mode, without causing a beep like <Esc> would.  However, this does not
 work in Ex mode.  When used after a command that takes an argument, such as
 |f| or |m|, the timeout set with 'ttimeoutlen' applies.
-When focus is in a terminal window, CTRL-\ CTRL-N goes to Normal mode for only
-one command, see |t_CTRL-\_CTRL-N|.

 	*CTRL-\_CTRL-G* *i_CTRL-\_CTRL-G* *c_CTRL-\_CTRL-G* *v_CTRL-\_CTRL-G*
 The command CTRL-\ CTRL-G or <C-\><C-G> can be used to go to Insert mode when
@@ -843,12 +826,10 @@ by Vim.  {Vi: not ok}
 ==============================================================================
 8. Definitions						*definitions*

-  buffer		Contains lines of text, usually read from a file.
  screen		The whole area that Vim uses to work in.  This can be
 			a terminal emulator window.  Also called "the Vim
 			window".
-  window		A view on a buffer.  There can be multiple windows for
-			one buffer.
+  window		A view on a buffer.

 A screen contains one or more windows, separated by status lines and with the
 command line at the bottom.
@@ -1,4 +1,4 @@
-*map.txt*       For Vim version 8.0.  Last change: 2017 Sep 23
+*map.txt*       For Vim version 8.0.  Last change: 2016 Aug 26


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -29,7 +29,7 @@ manual.
 1. Key mapping				*key-mapping* *mapping* *macro*

 Key mapping is used to change the meaning of typed keys.  The most common use
-is to define a sequence of commands for a function key.  Example: >
+is to define a sequence commands for a function key.  Example: >

 	:map <F2> a<C-R>=strftime("%c")<CR><Esc>

@@ -55,7 +55,6 @@ modes.
 :im[ap]	{lhs} {rhs}		|mapmode-i|		*:im* *:imap*
 :lm[ap]	{lhs} {rhs}		|mapmode-l|		*:lm* *:lmap*
 :cm[ap]	{lhs} {rhs}		|mapmode-c|		*:cm* *:cmap*
-:tma[p]	{lhs} {rhs}		|mapmode-t|		*:tma* *:tmap*
 			Map the key sequence {lhs} to {rhs} for the modes
 			where the map command applies.  The result, including
 			{rhs}, is then further scanned for mappings.  This
@@ -72,7 +71,6 @@ modes.
 :ino[remap] {lhs} {rhs}		|mapmode-i|	*:ino* *:inoremap*
 :ln[oremap] {lhs} {rhs}		|mapmode-l|	*:ln*  *:lnoremap*
 :cno[remap] {lhs} {rhs}		|mapmode-c|	*:cno* *:cnoremap*
-:tno[remap] {lhs} {rhs}		|mapmode-t|	*:tno* *:tnoremap*
 			Map the key sequence {lhs} to {rhs} for the modes
 			where the map command applies.  Disallow mapping of
 			{rhs}, to avoid nested and recursive mappings.  Often
@@ -89,7 +87,6 @@ modes.
 :iu[nmap] {lhs}			|mapmode-i|		*:iu*   *:iunmap*
 :lu[nmap] {lhs}			|mapmode-l|		*:lu*   *:lunmap*
 :cu[nmap] {lhs}			|mapmode-c|		*:cu*   *:cunmap*
-:tunma[p] {lhs}			|mapmode-t|		*:tunma* *:tunmap*
 			Remove the mapping of {lhs} for the modes where the
 			map command applies.  The mapping may remain defined
 			for other modes where it applies.
@@ -108,7 +105,6 @@ modes.
 :imapc[lear]			|mapmode-i|		*:imapc*  *:imapclear*
 :lmapc[lear]			|mapmode-l|		*:lmapc*  *:lmapclear*
 :cmapc[lear]			|mapmode-c|		*:cmapc*  *:cmapclear*
-:tmapc[lear]			|mapmode-t|		*:tmapc*  *:tmapclear*
 			Remove ALL mappings for the modes where the map
 			command applies.  {not in Vi}
 			Use the <buffer> argument to remove buffer-local
@@ -125,7 +121,6 @@ modes.
 :im[ap]				|mapmode-i|
 :lm[ap]				|mapmode-l|
 :cm[ap]				|mapmode-c|
-:tma[p]				|mapmode-t|
 			List all key mappings for the modes where the map
 			command applies.  Note that ":map" and ":map!" are
 			used most often, because they include the other modes.
@@ -140,7 +135,6 @@ modes.
 :im[ap] {lhs}			|mapmode-i|		*:imap_l*
 :lm[ap] {lhs}			|mapmode-l|		*:lmap_l*
 :cm[ap] {lhs}			|mapmode-c|		*:cmap_l*
-:tma[p] {lhs}			|mapmode-t|		*:tmap_l*
 			List the key mappings for the key sequences starting
 			with {lhs} in the modes where the map command applies.
 			{not in Vi}
@@ -191,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 typed they are used.
+already type they are used.

 						*:map-<silent>* *:map-silent*
 To define a mapping which will not be echoed on the command line, add
@@ -324,7 +318,6 @@ Overview of which map command works in which mode.  More details below.
 :imap  :inoremap :iunmap    Insert
 :lmap  :lnoremap :lunmap    Insert, Command-line, Lang-Arg
 :cmap  :cnoremap :cunmap    Command-line
-:tmap  :tnoremap :tunmap    Terminal-Job


    COMMANDS				      MODES ~
@@ -365,10 +358,6 @@ Therefore the ":map" and ":map!" commands enter and display mappings for
 several modes.  In Vim you can use the ":nmap", ":vmap", ":omap", ":cmap" and
 ":imap" commands to enter mappings for each mode separately.

-							*mapmode-t*
-The terminal mappings are used in a terminal window, when typing keys for the
-job running in the terminal.  See |terminal-typing|.
-
 							*omap-info*
 Operator-pending mappings can be used to define a movement command that can be
 used with any operator.  Simple example: ":omap { w" makes "y{" work like "yw"
@@ -429,7 +418,6 @@ When listing mappings the characters in the first two columns are:
 	i	Insert
 	l	":lmap" mappings for Insert, Command-line and Lang-Arg
 	c	Command-line
-	t	Terminal-Job

 Just before the {rhs} a special character can appear:
 	*	indicates that it is not remappable
@@ -596,8 +584,7 @@ Upper and lowercase differences are ignored.

 							*map-comments*
 It is not possible to put a comment after these commands, because the '"'
-character is considered to be part of the {lhs} or {rhs}. However, one can
-use |", since this starts a new, empty command with a comment.
+character is considered to be part of the {lhs} or {rhs}.

 							*map_bar* *map-bar*
 Since the '|' character is used to separate a map command from the next
@@ -694,7 +681,7 @@ option).  After that it assumes that the 'q' is to be interpreted as such.  If
 you type slowly, or your system is slow, reset the 'timeout' option.  Then you
 might want to set the 'ttimeout' option.

-			      				*map-precedence*
+                            				*map-precedence*
 Buffer-local mappings (defined using |:map-<buffer>|) take precedence over
 global mappings.  When a buffer-local mapping is the same as a global mapping,
 Vim will use the buffer-local mapping.  In addition, Vim will use a complete
@@ -810,7 +797,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*
@@ -1291,10 +1278,8 @@ completion can be enabled:
 	-complete=highlight	highlight groups
 	-complete=history	:history suboptions
 	-complete=locale	locale names (as output of locale -a)
-	-complete=mapclear	buffer argument
 	-complete=mapping	mapping name
 	-complete=menu		menus
-	-complete=messages	|:messages| suboptions
 	-complete=option	options
 	-complete=packadd	optional package |pack-add| names
 	-complete=shellcmd	Shell command
@@ -1427,8 +1412,6 @@ The valid escape sequences are
 	<line1>	The starting line of the command range.
 						*<line2>*
 	<line2>	The final line of the command range.
-						*<range>*
-	<range> The number of items in the command range: 0, 1 or 2
 						*<count>*
 	<count>	Any count supplied (as described for the '-range'
 		and '-count' attributes).
@@ -1,4 +1,4 @@
-*mbyte.txt*     For Vim version 8.0.  Last change: 2018 Jan 21
+*mbyte.txt*     For Vim version 8.0.  Last change: 2016 Jul 21


 		  VIM REFERENCE MANUAL	  by Bram Moolenaar et al.
@@ -26,9 +26,8 @@ For changing the language of messages and menus see |mlang.txt|.
 7.  Input on X11			|mbyte-XIM|
 8.  Input on MS-Windows			|mbyte-IME|
 9.  Input with a keymap			|mbyte-keymap|
-10. Input with imactivatefunc()		|mbyte-func|
-11. Using UTF-8				|mbyte-utf8|
-12. Overview of options			|mbyte-options|
+10. Using UTF-8				|mbyte-utf8|
+11. Overview of options			|mbyte-options|

 NOTE: This file contains UTF-8 characters.  These may show up as strange
 characters or boxes when using another encoding.
@@ -833,9 +832,6 @@ Use the RPM or port for your system.

  Currently, GUI Vim supports three styles, |OverTheSpot|, |OffTheSpot| and
  |Root|.
-  When compiled with |+GUI_GTK| feature, GUI Vim supports two styles,
-  |OnTheSpot| and |OverTheSpot|.  You can select the style with the 'imstyle'
-  option.

 *.  on-the-spot						*OnTheSpot*
    Preedit Area and Status Area are performed by the client application in
@@ -1255,35 +1251,7 @@ Combining forms:
 ﭏ    0xfb4f  Xal  alef-lamed

 ==============================================================================
-10.  Input with imactivatefunc()				*mbyte-func*
-
-Vim has the 'imactivatefunc' and 'imstatusfunc' options. These are useful to
-activate/deactivate the input method from Vim in any way, also with an external
-command. For example, fcitx provide fcitx-remote command: >
-
-	set iminsert=2
-	set imsearch=2
-	set imcmdline
-
-	set imactivatefunc=ImActivate
-	function! ImActivate(active)
-	  if a:active
-	    call system('fcitx-remote -o')
-	  else
-	    call system('fcitx-remote -c')
-	  endif
-	endfunction
-
-	set imstatusfunc=ImStatus
-	function! ImStatus()
-	  return system('fcitx-remote')[0] is# '2'
-	endfunction
-
-Using this script, you can activate/deactivate XIM via Vim even when it is not
-compiled with |+xim|.
-
-==============================================================================
-11. Using UTF-8				*mbyte-utf8* *UTF-8* *utf-8* *utf8*
+10. Using UTF-8				*mbyte-utf8* *UTF-8* *utf-8* *utf8*
 							*Unicode* *unicode*
 The Unicode character set was designed to include all characters from other
 character sets.  Therefore it is possible to write text in any language using
@@ -1431,7 +1399,7 @@ not everybody is able to type a composing character.


 ==============================================================================
-12. Overview of options					*mbyte-options*
+11. Overview of options					*mbyte-options*

 These options are relevant for editing multi-byte files.  Check the help in
 options.txt for detailed information.
@@ -1,4 +1,4 @@
-*message.txt*   For Vim version 8.0.  Last change: 2018 Feb 04
+*message.txt*   For Vim version 8.0.  Last change: 2016 Sep 01


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -76,7 +76,7 @@ See `:messages` above.
 LIST OF MESSAGES
 			*E222* *E228* *E232* *E256* *E293* *E298* *E304* *E317*
 			*E318* *E356* *E438* *E439* *E440* *E316* *E320* *E322*
-			*E323* *E341* *E473* *E570* *E685* *E950*  >
+			*E323* *E341* *E473* *E570* *E685*  >
  Add to read buffer
  makemap: Illegal mode
  Cannot create BalloonEval with both message and callback
@@ -97,7 +97,6 @@ LIST OF MESSAGES
  Internal error
  Internal error: {function}
  fatal error in cs_manage_matches
-  Invalid count for del_bytes(): {N}

 This is an internal error.  If you can reproduce it, please send in a bug
 report. |bugs|
@@ -130,9 +129,8 @@ closed properly.  Mostly harmless.
  Command too recursive

 This happens when an Ex command executes an Ex command that executes an Ex
-command, etc.  The limit is 200 or the value of 'maxfuncdepth', whatever is
-larger.  When it's more there probably is an endless loop.  Probably a
-|:execute| or |:source| command is involved.
+command, etc.  This is only allowed 200 times.  When it's more there probably
+is an endless loop.  Probably a |:execute| or |:source| command is involved.

 							*E254*  >
  Cannot allocate color {name}
@@ -464,6 +462,12 @@ changed.  To avoid the message reset the 'warn' option.
 Something inside Vim went wrong and resulted in a NULL pointer.  If you know
 how to reproduce this problem, please report it. |bugs|

+							*E172*  >
+  Only one file name allowed
+
+The ":edit" command only accepts one file name.  When you want to specify
+several files for editing use ":next" |:next|.
+
 						*E41* *E82* *E83* *E342*  >
  Out of memory!
  Out of memory!  (allocating {number} bytes)
@@ -640,9 +644,6 @@ starts.  It can be fixed in one of these ways:
 - Just write the file again the next day.  Or set your clock to the next day,
  write the file twice and set the clock back.

-If you get W11 all the time, you may need to disable "Acronis Active
-Protection" or register Vim as a trusted service/application.
-
 							*W12*  >
  Warning: File "{filename}" has changed and the buffer was changed in Vim as well

@@ -766,13 +767,6 @@ Example: >
 You tried to execute a command that is neither an Ex command nor
 a user-defined command.

-							*E943*  >
-  Command table needs to be updated, run 'make cmdidxs'
-
-This can only happen when changing the source code, when adding a command in
-src/ex_cmds.h.  The lookup table then needs to be updated, by running: >
-	make cmdidxs
-
 ==============================================================================
 3. Messages						*messages*

@@ -1,4 +1,4 @@
-*mlang.txt*     For Vim version 8.0.  Last change: 2017 Mar 04
+*mlang.txt*     For Vim version 8.0.  Last change: 2016 Jan 16


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -179,7 +179,6 @@ Send an e-mail to the Vim maintainer <maintainer@vim.org>.
 			special characters like "&" and "<Tab>" need to be
 			included.  Spaces and dots need to be escaped with a
 			backslash, just like in other |:menu| commands.
-			Case in {english} is ignored.

 See the $VIMRUNTIME/lang directory for examples.

@@ -1,4 +1,4 @@
-*motion.txt*    For Vim version 8.0.  Last change: 2017 Oct 15
+*motion.txt*    For Vim version 8.0.  Last change: 2016 Jul 12


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -193,7 +193,7 @@ l		or					*l*

 							*$* *<End>* *<kEnd>*
 $  or <End>		To the end of the line.  When a count is given also go
-			[count - 1] lines downward. |inclusive| motion.
+			[count - 1] lines downward |inclusive|.
 			In Visual mode the cursor goes to just after the last
 			character in the line.
 			When 'virtualedit' is active, "$" may move the cursor
@@ -915,7 +915,6 @@ was made yet in the current file.
 			then the position can be near the end of what the
 			command changed.  For example when inserting a word,
 			the position will be on the last character.
-			To jump to older changes use |g;|.
 			{not in Vi}

 							*'(* *`(*
@@ -1317,10 +1316,7 @@ the current line is included.  You can then use "%" to go to the matching line.
 H			To line [count] from top (Home) of window (default:
 			first line on the window) on the first non-blank
 			character |linewise|.  See also 'startofline' option.
-			Cursor is adjusted for 'scrolloff' option, unless an
-			operator is pending, in which case the text may
-			scroll.  E.g. "yH" yanks from the first visible line
-			until the cursor line (inclusive).
+			Cursor is adjusted for 'scrolloff' option.

 						*M*
 M			To Middle line of window, on the first non-blank
@@ -1330,10 +1326,7 @@ M			To Middle line of window, on the first non-blank
 L			To line [count] from bottom of window (default: Last
 			line on the window) on the first non-blank character
 			|linewise|.  See also 'startofline' option.
-			Cursor is adjusted for 'scrolloff' option, unless an
-			operator is pending, in which case the text may
-			scroll.  E.g. "yL" yanks from the cursor to the last
-			visible line.
+			Cursor is adjusted for 'scrolloff' option.

 <LeftMouse>		Moves to the position on the screen where the mouse
 			click is |exclusive|.  See also |<LeftMouse>|.  If the
@@ -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.
@@ -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
@@ -1,4 +1,4 @@
-*os_mac.txt*    For Vim version 8.0.  Last change: 2018 Jan 21
+*os_mac.txt*    For Vim version 8.0.  Last change: 2006 Apr 30


 		  VIM REFERENCE MANUAL    by Bram Moolenaar et al.
@@ -16,13 +16,11 @@ Carbon version of Vim here:
 	http://macvim.org/

 1. Filename Convention		|mac-filename|
-2. .vimrc and .vim files	|mac-vimfile|
-3. Standard mappings		|mac-standard-mappings|
-4. FAQ				|mac-faq|
-5. Known Lack			|mac-lack|
-6. Mac Bug Report		|mac-bug|
-7. Compiling Vim		|mac-compile|
-8. The darwin feature		|mac-darwin-feature|
+2. .vimrc an .vim files		|mac-vimfile|
+3. FAQ				|mac-faq|
+4. Known Lack			|mac-lack|
+5. Mac Bug Report		|mac-bug|
+6. Compiling Vim		|mac-compile|

 There was a Mac port for version 3.0 of Vim.  Here are the first few lines
 from the old file:
@@ -78,18 +76,7 @@ the |'nocompatible'| option is set, otherwise it will only handle mac format
 files.

 ==============================================================================
-3. Standard mappings				*mac-standard-mappings*
-
-The following mappings are available for cut/copy/paste from/to clipboard.
-
-key		Normal	Visual	  Insert	Description ~
-Command-v	"*P	"-d"*P    <C-R>*	paste text       *<D-v>*
-Command-c		"*y			copy Visual text *<D-c>*
-Command-x		"*d			cut Visual text  *<D-x>*
-Backspace		"*d			cut Visual text
-
-==============================================================================
-4. Mac FAQ						*mac-faq*
+3. Mac FAQ						*mac-faq*

 On the internet:  http://macvim.org/OSX/index.php#FAQ

@@ -112,13 +99,13 @@ A: The following trick works with most shells.  Put it in your vimrc file.
 	let $PATH = matchstr(s:path, 'VIMPATH\zs.\{-}\ze\n')

 ==============================================================================
-5. Mac Lack						*mac-lack*
+4. Mac Lack						*mac-lack*

 In a terminal CTRL-^ needs to be entered as Shift-Control-6.  CTRL-@ as
 Shift-Control-2.

 ==============================================================================
-6. Mac Bug Report					*mac-bug*
+5. Mac Bug Report					*mac-bug*

 When reporting any Mac specific bug or feature change, please use the vim-mac
 maillist |vim-mac|.  However, you need to be subscribed.  An alternative is to
@@ -127,60 +114,9 @@ send a message to the current MacVim maintainers:
 	mac@vim.org

 ==============================================================================
-7. Compiling Vim					*mac-compile*
+6. Compiling Vim					*mac-compile*

 See the file "src/INSTALLmac.txt" that comes with the source files.

-==============================================================================
-8. The Darwin Feature					*mac-darwin-feature*
-
-If you have a Mac that isn't very old, you will be running OS X, also called
-Darwin.  The last pre-Darwin OS was Mac OS 9.  The darwin feature makes Vim
-use Darwin-specific properties.
-
-What is accomplished with this feature is two-fold:
-
- Make Vim interoperable with the system clipboard.
- Incorporate into Vim a converter module that bridges the gap between some
-  character encodings specific to the platform and those known to Vim.
-
-Needless to say, both are not to be missed for any decent text editor to work
-nicely with other applications running on the same desktop environment.
-
-As Vim is not an application dedicated only to macOS, we need an extra feature
-to add in order for it to offer the same user experience that our users on
-other platforms enjoy to people on macOS.
-
-For brevity, the feature is referred to as "darwin" to signify it one of the
-Vim features that are specific to that particular platform.
-
-The feature is a configuration option.  Accordingly, whether it is enabled or
-not is determined at build time; once it is selected to be enabled, it is
-compiled in and hence cannot be disabled at runtime.
-
-The feature is enabled by default.  For most macOS users, that should be
-sufficient unless they have specific needs mentioned briefly below.
-
-If you want to disable it, pass `--disable-darwin` to the configure script: >
-
-    ./configure --disable-darwin <other options>
-
-and then run `make` to build Vim.  The order of the options doesn't matter.
-
-To make sure at runtime whether or not the darwin feature is compiled in, you
-can use `has('osxdarwin')` which returns 1 if the feature is compiled in; 0
-otherwise.  For backward compatibility, you can still use `macunix` instead of
-`osxdarwin`.
-
-Notable use cases where `--disable-darwin` is turned out to be useful are:
-
- When you want to use |x11-selection| instead of the system clipboard.
- When you want to use |x11-clientserver|.
-
-Since both have to make use of X11 inter-client communication for them to work
-properly, and since the communication mechanism can come into conflict with
-the system clipboard, the darwin feature should be disabled to prevent Vim
-from hanging at runtime.
-

 vim:tw=78:ts=8:ft=help:norl:
@@ -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
@@ -1,4 +1,4 @@
-*os_win32.txt*  For Vim version 8.0.  Last change: 2017 Mar 21
+*os_win32.txt*  For Vim version 8.0.  Last change: 2016 Aug 28


 		  VIM REFERENCE MANUAL    by George Reilly
@@ -7,18 +7,20 @@
 						*win32* *Win32* *MS-Windows*
 This file documents the idiosyncrasies of the Win32 version of Vim.

-The Win32 version of Vim works on Windows XP, Vista, 7, 8 and 10.  There are
-both console and GUI versions.
+The Win32 version of Vim works on Windows NT, 95, 98, ME, XP, Vista and
+Windows 7.  There are both console and GUI versions.

 The 32 bit version also runs on 64 bit MS-Windows systems.

+There is GUI version for use in the Win32s subsystem in Windows 3.1[1].  You
+can also use the 32-bit DOS version of Vim instead.  See |os_msdos.txt|.
+
 1. Known problems		|win32-problems|
 2. Startup			|win32-startup|
 3. Restore screen contents	|win32-restore|
 4. Using the mouse		|win32-mouse|
-5. Running under Windows 95	|win32-win95|
-6. Running under Windows 3.1	|win32-win3.1|
-7. Win32 mini FAQ		|win32-faq|
+5. Running under Windows 3.1	|win32-win3.1|
+6. Win32 mini FAQ		|win32-faq|

 Additionally, there are a number of common Win32 and DOS items:
 File locations			|dos-locations|
@@ -41,7 +43,20 @@ The GUI version was made by George V. Reilly and Robert Webb.
 For compiling see "src/INSTALLpc.txt".			*win32-compiling*

 ==============================================================================
-1. Known problems					*win32-problems*
+1. Known problems				*windows95* *win32-problems*
+
+There are a few known problems with running in a console on Windows 95.  As
+far as we know, this is the same in Windows 98 and Windows ME.
+
+Comments from somebody working at Microsoft: "Win95 console support has always
+been and will always be flaky".
+1.  Dead key support doesn't work.
+2.  Resizing the window with ":set columns=nn lines=nn" works, but executing
+    external commands MAY CAUSE THE SYSTEM TO HANG OR CRASH.
+3.  Screen updating is slow, unless you change 'columns' or 'lines' to a
+    non-DOS value.  But then the second problem applies!
+
+If this bothers you, use the 32 bit MS-DOS version or the Win32 GUI version.

 When doing file name completion, Vim also finds matches for the short file
 name.  But Vim will still find and use the corresponding long file name.  For
@@ -81,45 +96,10 @@ The directory of the Vim executable is appended to $PATH.  This is mostly to
 make "!xxd" work, as it is in the Tools menu.  And it also means that when
 executable() returns 1 the executable can actually be executed.

-Command line arguments					*win32-cmdargs*
+Quotes in file names					*win32-quotes*

-Analysis of a command line into parameters is not standardised in MS Windows.
-Vim and gvim used to use different logic to parse it (before 7.4.432), and the
-logic was also depended on what it was compiled with.  Now Vim and gvim both
-use the CommandLineToArgvW() Win32 API, so they behave in the same way.
-
-The basic rules are:					*win32-backslashes*
-      a) A parameter is a sequence of graphic characters.
-      b) Parameters are separated by white space.
-      c) A parameter can be enclosed in double quotes to include white space.
-      d) A sequence of zero or more backslashes (\) and a double quote (")
-	is special.  The effective number of backslashes is halved, rounded
-	down.  An even number of backslashes reverses the acceptability of
-	spaces and tabs, an odd number of backslashes produces a literal
-	double quote.
-
-So:
-	"	is a special double quote
-	\"	is a literal double quote
-	\\"	is a literal backslash and a special double quote
-	\\\"	is a literal backslash and a literal double quote
-	\\\\"	is 2 literal backslashes and a special double quote
-	\\\\\"	is 2 literal backslashes and a literal double quote
-	etc.
-
-Example: >
-	vim "C:\My Music\freude" +"set ignorecase" +/"\"foo\\" +\"bar\\\"
-
-opens "C:\My Music\freude" and executes the line mode commands: >
-	set ignorecase; /"foo\ and /bar\"
-
-These rules are also described in the reference of the CommandLineToArgvW API:
-    https://msdn.microsoft.com/en-us/library/windows/desktop/bb776391.aspx
-
-							*win32-quotes*
-There are additional rules for quotes (which are not well documented).
-As described above, quotes inside a file name (or any other command line
-argument) can be escaped with a backslash.  E.g. >
+Quotes inside a file name (or any other command line argument) can be escaped
+with a backslash.  E.g. >
 	vim -c "echo 'foo\"bar'"

 Alternatively use three quotes to get one: >
@@ -161,20 +141,60 @@ When the mouse doesn't work, try disabling the "Quick Edit Mode" feature of
 the console.

 ==============================================================================
-5. Running under Windows 95				*win32-win95*
-					*windows95* *windows98* *windowsme*
-Windows 95/98/ME support was removed in patch 8.0.0029  If you want to use it
-you will need to get a version older than that.
+5. Running under Windows 3.1				*win32-win3.1*

-==============================================================================
-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.
+						*win32s* *windows-3.1*
+There was a special version of Gvim that runs under Windows 3.1 and 3.11.
 Support was removed in patch 7.4.1363.

 ==============================================================================
-7. Win32 mini FAQ					*win32-faq*
+6. Win32 mini FAQ					*win32-faq*
+
+Q. Why does the Win32 version of Vim update the screen so slowly on Windows 95?
+A. The support for Win32 console mode applications is very buggy in Win95.
+   For some unknown reason, the screen updates very slowly when Vim is run at
+   one of the standard resolutions (80x25, 80x43, or 80x50) and the 16-bit DOS
+   version updates the screen much more quickly than the Win32 version.
+   However, if the screen is set to some other resolution, such as by ":set
+   columns=100" or ":set lines=40", screen updating becomes about as fast as
+   it is with the 16-bit version.
+
+   WARNING: Changing 'columns' may make Windows 95 crash while updating the
+   window (complaints --> Microsoft).  Since this mostly works, this has not
+   been disabled, but be careful with changing 'columns'.
+
+   Changing the screen resolution makes updates faster, but it brings
+   additional problems.  External commands (e.g., ":!dir") can cause Vim to
+   freeze when the screen is set to a non-standard resolution, particularly
+   when 'columns' is not equal to 80.  It is not possible for Vim to reliably
+   set the screen resolution back to the value it had upon startup before
+   running external commands, so if you change the number of 'lines' or
+   'columns', be very, very careful.  In fact, Vim will not allow you to
+   execute external commands when 'columns' is not equal to 80, because it is
+   so likely to freeze up afterwards.
+
+   None of the above applies on Windows NT.  Screen updates are fast, no
+   matter how many 'lines' or 'columns' the window has, and external commands
+   do not cause Vim to freeze.
+
+Q. So if the Win32 version updates the screen so slowly on Windows 95 and the
+   16-bit DOS version updates the screen quickly, why would I want to run the
+   Win32 version?
+A. Firstly, the Win32 version isn't that slow, especially when the screen is
+   set to some non-standard number of 'lines' or 'columns'.  Secondly, the
+   16-bit DOS version has some severe limitations: It can't do big changes and
+   it doesn't know about long file names.  The Win32 version doesn't have these
+   limitations and it's faster overall (the same is true for the 32-bit DJGPP
+   DOS version of Vim).  The Win32 version is smarter about handling the
+   screen, the mouse, and the keyboard than the DJGPP version is.
+
+Q. And what about the 16-bit DOS version versus the Win32 version on NT?
+A. There are no good reasons to run the 16-bit DOS version on NT.  The Win32
+   version updates the screen just as fast as the 16-bit version does when
+   running on NT.  All of the above disadvantages apply.  Finally, DOS
+   applications can take a long time to start up and will run more slowly.  On
+   non-Intel NT platforms, the DOS version is almost unusably slow, because it
+   runs on top of an 80x86 emulator.

 Q. How do I change the font?
 A. In the GUI version, you can use the 'guifont' option.  Example: >
@@ -182,6 +202,47 @@ A. In the GUI version, you can use the 'guifont' option.  Example: >
 <  In the console version, you need to set the font of the console itself.
   You cannot do this from within Vim.

+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
+   font instead.
+
+Q. Why can't I paste into Vim when running Windows 95?
+A. In the properties dialog box for the MS-DOS window, go to "MS-DOS
+   Prompt/Misc/Fast pasting" and make sure that it is NOT checked.  You should
+   also do ":set paste" in Vim to avoid unexpected effects.	|'paste'|
+
+Q. How do I type dead keys on Windows 95, in the console version?
+   (A dead key is an accent key, such as acute, grave, or umlaut, that doesn't
+   produce a character by itself, but when followed by another key, produces
+   an accented character, such as a-acute, e-grave, u-umlaut, n-tilde, and so
+   on.  Very useful for most European languages.  English-language keyboard
+   layouts don't use dead keys, as far as we know.)
+A. You don't.  The console mode input routines simply do not work correctly in
+   Windows 95, and I have not been able to work around them.  In the words
+   of a senior developer at Microsoft:
+	Win95 console support has always been and will always be flaky.
+
+	The flakiness is unavoidable because we are stuck between the world of
+	MS-DOS keyboard TSRs like KEYB (which wants to cook the data;
+	important for international) and the world of Win32.
+
+	So keys that don't "exist" in MS-DOS land (like dead keys) have a
+	very tenuous existence in Win32 console land.  Keys that act
+	differently between MS-DOS land and Win32 console land (like
+	capslock) will act flaky.
+
+	Don't even _mention_ the problems with multiple language keyboard
+	layouts...
+
+   You may be able to fashion some sort of workaround with the digraphs
+   mechanism.							|digraphs|
+
+   The best solution is to use the Win32 GUI version gvim.exe.  Alternatively,
+   you can try one of the DOS versions of Vim where dead keys reportedly do
+   work.
+
 Q. How do I type dead keys on Windows NT?
 A. Dead keys work on NT 3.51.  Just type them as you would in any other
   application.
@@ -247,19 +308,10 @@ A. You can't!  This is a limitation of the NT console.  NT 5.0 is reported to
   be able to set the blink rate for all console windows at the same time.

 							*:!start*
-Q. How can I asynchronously run an external command or program, or open a
-   document or URL with its default program?
-A. When using :! to run an external command, you can run it with "start". For
-   example, to run notepad: >
-	:!start notepad
-<   To open "image.jpg" with the default image viewer: >
-        :!start image.jpg
-<   To open the folder of the current file in Windows Explorer: >
-        :!start %:h
-<   To open the Vim home page with the default browser: >
-        :!start http://www.vim.org/
-<
-   Using "start" stops Vim switching to another screen, opening a new console,
+Q. How can I run an external command or program asynchronously?
+A. When using :! to run an external command, you can run it with "start": >
+	:!start winfile.exe<CR>
+<  Using "start" stops Vim switching to another screen, opening a new console,
   or waiting for the program to complete; it indicates that you are running a
   program that does not affect the files you are editing.  Programs begun
   with :!start do not get passed Vim's open file handles, which means they do
@@ -297,6 +349,28 @@ A. You have two possible solutions depending on what you want:
 <  The first command runs notepad minimized and the second one runs it
   normally.

+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!
+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
+   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).
+   2) Open the file "_DEFAULT.PIF" in your Windows directory.
+   3) Changes the display option from "Full Screen" to "Windowed".
+   4) Save and exit.
+
+   To test, start Vim and type >
+	:!dir C:\<CR>".
+<  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
+   W3.1x, or am I stuck with 80x25?
+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.
+
 						*windows-icon*
 Q. I don't like the Vim icon, can I change it?
 A. Yes, place your favorite icon in bitmaps/vim.ico in a directory of
@@ -1,4 +1,4 @@
-*pattern.txt*   For Vim version 8.0.  Last change: 2018 Mar 13
+*pattern.txt*   For Vim version 8.0.  Last change: 2016 Sep 11


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -869,13 +869,10 @@ $	At end of pattern or in front of "\|", "\)" or "\n" ('magic' on):
 \%V	Match inside the Visual area.  When Visual mode has already been
 	stopped match in the area that |gv| would reselect.
 	This is a |/zero-width| match.  To make sure the whole pattern is
-	inside the Visual area put it at the start and just before the end of
-	the pattern, e.g.: >
-		/\%Vfoo.*ba\%Vr
-<	This also works if only "foo bar" was Visually selected. This: >
+	inside the Visual area put it at the start and end of the pattern,
+	e.g.: >
 		/\%Vfoo.*bar\%V
-<	would match "foo bar" if the Visual selection continues after the "r".
-	Only works for the current buffer.
+<	Only works for the current buffer.

 						*/\%#* *cursor-position*
 \%#	Matches with the cursor position.  Only works when matching in a
@@ -905,7 +902,7 @@ $	At end of pattern or in front of "\|", "\)" or "\n" ('magic' on):
 	becomes invalid.  Vim doesn't automatically update the matches.
 	Similar to moving the cursor for "\%#" |/\%#|.

-						*/\%l* */\%>l* */\%<l* *E951*
+						*/\%l* */\%>l* */\%<l*
 \%23l	Matches in a specific line.
 \%<23l	Matches above a specific line (lower line number).
 \%>23l	Matches below a specific line (higher line number).
@@ -1076,40 +1073,34 @@ x	A single character, with no special meaning, matches itself
 	":s/[/x/" searches for "[/x" and replaces it with nothing.  It does
 	not search for "[" and replaces it with "x"!

-								*E944* *E945*
 	If the sequence begins with "^", it matches any single character NOT
 	in the collection: "[^xyz]" matches anything but 'x', 'y' and 'z'.
 	- If two characters in the sequence are separated by '-', this is
 	  shorthand for the full list of ASCII characters between them.  E.g.,
-	  "[0-9]" matches any decimal digit. If the starting character exceeds
-	  the ending character, e.g. [c-a], E944 occurs. Non-ASCII characters
-	  can be used, but the character values must not be more than 256 apart
-	  in the old regexp engine. For example, searching by [\u3000-\u4000]
-	  after setting re=1 emits a E945 error. Prepending \%#=2 will fix it.
+	  "[0-9]" matches any decimal digit.  Non-ASCII characters can be
+	  used, but the character values must not be more than 256 apart.
 	- A character class expression is evaluated to the set of characters
 	  belonging to that character class.  The following character classes
 	  are supported:
-		  Name	      Func	Contents ~
-*[:alnum:]*	  [:alnum:]   isalnum	ASCII letters and digits
-*[:alpha:]*	  [:alpha:]   isalpha  	ASCII letters
-*[:blank:]*	  [:blank:]     	space and tab
-*[:cntrl:]*	  [:cntrl:]   iscntrl 	ASCII control characters
-*[:digit:]*	  [:digit:]     	decimal digits '0' to '9'
-*[:graph:]*	  [:graph:]   isgraph	ASCII printable characters excluding
-					space
-*[:lower:]*	  [:lower:]   (1)	lowercase letters (all letters when
+			  Name		Contents ~
+*[:alnum:]*		  [:alnum:]     ASCII letters and digits
+*[:alpha:]*		  [:alpha:]     ASCII letters
+*[:blank:]*		  [:blank:]     space and tab characters
+*[:cntrl:]*		  [:cntrl:]     control characters
+*[:digit:]*		  [:digit:]     decimal digits
+*[:graph:]*		  [:graph:]     printable characters excluding space
+*[:lower:]*		  [:lower:]     lowercase letters (all letters when
 					'ignorecase' is used)
-*[:print:]*	  [:print:]   (2) 	printable characters including space
-*[:punct:]*	  [:punct:]   ispunct	ASCII punctuation characters
-*[:space:]*	  [:space:]     	whitespace characters: space, tab, CR,
-					NL, vertical tab, form feed
-*[:upper:]*	  [:upper:]   (3)	uppercase letters (all letters when
+*[:print:]*		  [:print:]     printable characters including space
+*[:punct:]*		  [:punct:]     ASCII punctuation characters
+*[:space:]*		  [:space:]     whitespace characters
+*[:upper:]*		  [:upper:]     uppercase letters (all letters when
 					'ignorecase' is used)
-*[:xdigit:]*	  [:xdigit:]    	hexadecimal digits: 0-9, a-f, A-F
-*[:return:]*	  [:return:]		the <CR> character
-*[:tab:]*	  [:tab:]		the <Tab> character
-*[:escape:]*	  [:escape:]		the <Esc> character
-*[:backspace:]*	  [:backspace:]		the <BS> character
+*[:xdigit:]*		  [:xdigit:]    hexadecimal digits
+*[:return:]*		  [:return:]	the <CR> character
+*[:tab:]*		  [:tab:]	the <Tab> character
+*[:escape:]*		  [:escape:]	the <Esc> character
+*[:backspace:]*		  [:backspace:]	the <BS> character
 	  The brackets in character class expressions are additional to the
 	  brackets delimiting a collection.  For example, the following is a
 	  plausible pattern for a UNIX filename: "[-./[:alnum:]_~]\+" That is,
@@ -1120,13 +1111,6 @@ x	A single character, with no special meaning, matches itself
 	  regexp engine.  See |two-engines|.  In the future these items may
 	  work for multi-byte characters.  For now, to get all "alpha"
 	  characters you can use: [[:lower:][:upper:]].
-
-	  The "Func" column shows what library function is used.  The
-	  implementation depends on the system.  Otherwise:
-	  (1) Uses islower() for ASCII and Vim builtin rules for other
-	  characters when built with the |+multi_byte| feature.
-	  (2) Uses Vim builtin rules
-	  (3) As with (1) but using isupper()
 							*/[[=* *[==]*
 	- An equivalence class.  This means that characters are matched that
 	  have almost the same meaning, e.g., when ignoring accents.  This
@@ -1166,8 +1150,7 @@ x	A single character, with no special meaning, matches itself
 	- Matching with a collection can be slow, because each character in
 	  the text has to be compared with each character in the collection.
 	  Use one of the other atoms above when possible.  Example: "\d" is
-	  much faster than "[0-9]" and matches the same characters.  However,
-	  the new |NFA| regexp engine deals with this better than the old one.
+	  much faster than "[0-9]" and matches the same characters.

 						*/\%[]* *E69* *E70* *E369*
 \%[]	A sequence of optionally matched atoms.  This always matches.
@@ -1,4 +1,4 @@
-*pi_getscript.txt*  For Vim version 7.0.  Last change: 2017 Aug 01
+*pi_getscript.txt*  For Vim version 7.0.  Last change: 2013 Nov 29
 >
 		GETSCRIPT REFERENCE MANUAL  by Charles E. Campbell
 <
@@ -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 %
@@ -389,7 +389,7 @@ v36 Apr 22, 2013 : * (glts) suggested use of plugin/**/*.vim instead of
 		     plugin/*.vim in globpath() call.
 		   * (Andy Wokula) got warning message when setting
 		     g:loaded_getscriptPlugin
-v35 Apr 07, 2012 : * (MengHuan Yu) pointed out that the script URL has
+v35 Apr 07, 2012 : * (MengHuan Yu) pointed out that the script url has
 		     changed (somewhat).  However, it doesn't work, and
 		     the original one does (under Linux). I'll make it
 		     yet-another-option.
@@ -1,4 +1,4 @@
-*pi_gzip.txt*   For Vim version 8.0.  Last change: 2016 Nov 06
+*pi_gzip.txt*   For Vim version 8.0.  Last change: 2012 Jul 19


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -27,8 +27,6 @@ with these extensions:
 	*.bz2		bzip2
 	*.lzma		lzma
 	*.xz		xz
-	*.lz		lzip
-	*.zst		zstd

 That's actually the only thing you need to know.  There are no options.

@@ -1,4 +1,4 @@
-*pi_logipat.txt*	Logical Patterns			Jun 22, 2015
+*logiPat.txt*	Logical Patterns				Jun 22, 2015

 Author:  Charles E. Campbell  <NdrOchip@ScampbellPfamily.AbizM>
 Copyright: (c) 2004-2015 by Charles E. Campbell	*logiPat-copyright*
@@ -1,4 +1,4 @@
-*pi_netrw.txt*  For Vim version 8.0.  Last change: 2017 Nov 03
+*pi_netrw.txt*  For Vim version 8.0.  Last change: 2016 Apr 20

 	    ------------------------------------------------
 	    NETRW REFERENCE MANUAL    by Charles E. Campbell
@@ -6,7 +6,7 @@
 Author:  Charles E. Campbell  <NdrOchip@ScampbellPfamily.AbizM>
 	  (remove NOSPAM from Campbell's email first)

-Copyright: Copyright (C) 2017 Charles E Campbell    *netrw-copyright*
+Copyright: Copyright (C) 2016 Charles E Campbell    *netrw-copyright*
 	The VIM LICENSE applies to the files in this package, including
 	netrw.vim, pi_netrw.txt, netrwFileHandlers.vim, netrwSettings.vim, and
 	syntax/netrw.vim.  Like anything else that's free, netrw.vim and its
@@ -17,6 +17,7 @@ Copyright: Copyright (C) 2017 Charles E Campbell    *netrw-copyright*
 	holder be liable for any damages resulting from the use of this
 	software. Use at your own risk!

+
 		*netrw*
 		*dav*    *ftp*    *netrw-file*  *rcp*    *scp*
 		*davs*   *http*   *netrw.vim*   *rsync*  *sftp*
@@ -72,7 +73,7 @@ Copyright: Copyright (C) 2017 Charles E Campbell    *netrw-copyright*
      Improving Browsing..................................|netrw-ssh-hack|
      Listing Bookmarks And History.......................|netrw-qb|
      Making A New Directory..............................|netrw-d|
-      Making The Browsing Directory The Current Directory.|netrw-cd|
+      Making The Browsing Directory The Current Directory.|netrw-c|
      Marking Files.......................................|netrw-mf|
      Unmarking Files.....................................|netrw-mF|
      Marking Files By Location List......................|netrw-qL|
@@ -82,7 +83,6 @@ Copyright: Copyright (C) 2017 Charles E Campbell    *netrw-copyright*
      Marked Files: Arbitrary Shell Command, En Bloc......|netrw-mX|
      Marked Files: Arbitrary Vim Command.................|netrw-mv|
      Marked Files: Argument List.........................|netrw-ma| |netrw-mA|
-      Marked Files: Buffer List...........................|netrw-cb| |netrw-cB|
      Marked Files: Compression And Decompression.........|netrw-mz|
      Marked Files: Copying...............................|netrw-mc|
      Marked Files: Diff..................................|netrw-md|
@@ -155,7 +155,7 @@ Windows' ftp doesn't support .netrc; however, one may have in one's .vimrc:  >

   let g:netrw_ftp_cmd= 'c:\Windows\System32\ftp -s:C:\Users\MyUserName\MACHINE'
 <
-Netrw will substitute the host's machine name for "MACHINE" from the URL it is
+Netrw will substitute the host's machine name for "MACHINE" from the url it is
 attempting to open, and so one may specify >
 	userid
 	password
@@ -212,7 +212,7 @@ EXTERNAL APPLICATIONS AND PROTOCOLS			*netrw-externapp* {{{2
          http:   g:netrw_http_cmd     = "fetch"      elseif fetch is available
 	  http:   *g:netrw_http_put_cmd* = "curl -T"
 	   rcp:   *g:netrw_rcp_cmd*      = "rcp"
-	 rsync:   *g:netrw_rsync_cmd*    = "rsync"     (see |g:netrw_rsync_sep|)
+	 rsync:   *g:netrw_rsync_cmd*    = "rsync -a"
 	   scp:   *g:netrw_scp_cmd*      = "scp -q"
 	  sftp:   *g:netrw_sftp_cmd*     = "sftp"
 	  file:   *g:netrw_file_cmd*     = "elinks" or "links"
@@ -223,7 +223,7 @@ EXTERNAL APPLICATIONS AND PROTOCOLS			*netrw-externapp* {{{2

 		    elinks : "-source >"
 		    links  : "-dump >"
-		    curl   : "-L -o"
+		    curl   : "-o"
 		    wget   : "-q -O"
 		    fetch  : "-o"
 <
@@ -238,7 +238,7 @@ EXTERNAL APPLICATIONS AND PROTOCOLS			*netrw-externapp* {{{2

 READING						*netrw-read* *netrw-nread* {{{2

-	Generally, one may just use the URL notation with a normal editing
+	Generally, one may just use the url notation with a normal editing
 	command, such as >

 		:e ftp://[user@]machine/path
@@ -260,7 +260,7 @@ READING						*netrw-read* *netrw-nread* {{{2

 WRITING					*netrw-write* *netrw-nwrite* {{{2

-	One may just use the URL notation with a normal file writing
+	One may just use the url notation with a normal file writing
 	command, such as >

 		:w ftp://[user@]machine/path
@@ -281,7 +281,7 @@ WRITING					*netrw-write* *netrw-nwrite* {{{2

 SOURCING					*netrw-source* {{{2

-	One may just use the URL notation with the normal file sourcing
+	One may just use the url notation with the normal file sourcing
 	command, such as >

 		:so ftp://[user@]machine/path
@@ -479,7 +479,7 @@ file using root-relative paths, use the full path:
 ==============================================================================
 4. Network-Oriented File Transfer			*netrw-xfer* {{{1

-Network-oriented file transfer under Vim is implemented by a vim script
+Network-oriented file transfer under Vim is implemented by a VimL-based script
 (<netrw.vim>) using plugin techniques.  It currently supports both reading and
 writing across networks using rcp, scp, ftp or ftp+<.netrc>, scp, fetch,
 dav/cadaver, rsync, or sftp.
@@ -532,7 +532,7 @@ variable (ex. scp uses the variable g:netrw_scp_cmd, which is defaulted to
 	let g:netrw_sftp_cmd= '"c:\Program Files\PuTTY\psftp.exe"'
 <
 (note: it has been reported that windows 7 with putty v0.6's "-batch" option
-       doesn't work, so its best to leave it off for that system)
+       doesn't work, so it's best to leave it off for that system)

 See |netrw-p8| for more about putty, pscp, psftp, etc.

@@ -734,11 +734,11 @@ such as netrw.
 The usual read/write commands are supported.  There are also a few
 additional commands available.  Often you won't need to use Nwrite or
 Nread as shown in |netrw-transparent| (ie. simply use >
-  :e URL
-  :r URL
-  :w URL
+  :e url
+  :r url
+  :w url
 instead, as appropriate) -- see |netrw-urls|.  In the explanations
-below, a {netfile} is a URL to a remote file.
+below, a {netfile} is an url to a remote file.

 						*:Nwrite*  *:Nw*
 :[range]Nw[rite]	Write the specified lines to the current
@@ -868,11 +868,9 @@ variables listed below, and may be modified by the user.
    g:netrw_http_cmd     var   ="fetch -o"     if      fetch is available
    g:netrw_http_cmd     var   ="wget -O"      else if wget  is available
    g:netrw_http_put_cmd var   ="curl -T"
-    |g:netrw_list_cmd|     var   ="ssh USEPORT HOSTNAME ls -Fa"
+    |g:netrw_list_cmd|    var   ="ssh USEPORT HOSTNAME ls -Fa"
    g:netrw_rcp_cmd      var   ="rcp"
-    g:netrw_rsync_cmd    var   ="rsync"
-    *g:netrw_rsync_sep*    var   ="/"            used to separate the hostname
-                                               from the file spec
+    g:netrw_rsync_cmd    var   ="rsync -a"
    g:netrw_scp_cmd      var   ="scp -q"
    g:netrw_sftp_cmd     var   ="sftp" >
    -------------------------------------------------------------------------
@@ -1009,7 +1007,7 @@ where [protocol] is typically scp or ftp.  As an example, try: >
 	vim ftp://ftp.home.vim.org/pub/vim/
 <
 For local directories, the trailing slash is not required.  Again, because it's
-easy to miss: to browse remote directories, the URL must terminate with a
+easy to miss: to browse remote directories, the url must terminate with a
 slash!

 If you'd like to avoid entering the password repeatedly for remote directory
@@ -1079,9 +1077,9 @@ QUICK REFERENCE: MAPS				*netrw-browse-maps* {{{2
 	 <c-r>	Browse using a gvim server                           |netrw-ctrl-r|
 	 <c-tab> Shrink/expand a netrw/explore window                |netrw-c-tab|
 	   -	Makes Netrw go up one directory                      |netrw--|
-	   a	Cycles between normal display,                       |netrw-a|
+	   a	Toggles between normal display,                      |netrw-a|
 	    	hiding (suppress display of files matching g:netrw_list_hide)
-	    	and showing (display only files which match g:netrw_list_hide)
+	    	showing (display only files which match g:netrw_list_hide)
 	   c	Make browsing directory the current directory        |netrw-c|
 	   C	Setting the editing window                           |netrw-C|
 	   d	Make a directory                                     |netrw-d|
@@ -1092,7 +1090,6 @@ QUICK REFERENCE: MAPS				*netrw-browse-maps* {{{2
 	   gh	Quick hide/unhide of dot-files                       |netrw-gh|
 	   gn	Make top of tree the directory below the cursor      |netrw-gn|
 	   i	Cycle between thin, long, wide, and tree listings    |netrw-i|
-	   I	Toggle the displaying of the banner                  |netrw-I|
 	   mb	Bookmark current directory                           |netrw-mb|
 	   mc	Copy marked files to marked-file target directory    |netrw-mc|
 	   md	Apply diff to marked files (up to 3)                 |netrw-md|
@@ -1172,26 +1169,25 @@ QUICK REFERENCE: COMMANDS	*netrw-explore-cmds* *netrw-browse-cmds* {{{2

 BANNER DISPLAY						*netrw-I*

-One may toggle the displaying of the banner by pressing "I".
+One may toggle the banner display on and off by pressing "I".

 Also See: |g:netrw_banner|


-BOOKMARKING A DIRECTORY		*netrw-mb* *netrw-bookmark* *netrw-bookmarks* {{{2
+BOOKMARKING A DIRECTORY *netrw-mb* *netrw-bookmark* *netrw-bookmarks* {{{2

 One may easily "bookmark" the currently browsed directory by using >

 	mb
 <
 								*.netrwbook*
-Bookmarks are retained in between sessions of vim in a file called .netrwbook
-as a |List|, which is typically stored in the first directory on the user's
-'|runtimepath|'; entries are kept in sorted order.
+Bookmarks are retained in between sessions in a $HOME/.netrwbook file, and are
+kept in sorted order.

 If there are marked files and/or directories, mb will add them to the bookmark
 list.

-								*netrw-:NetrwMB*
+*netrw-:NetrwMB*
 Addtionally, one may use :NetrwMB to bookmark files or directories. >

 	:NetrwMB[!] [files/directories]
@@ -1210,7 +1206,7 @@ The :NetrwMB command is available outside of netrw buffers (once netrw has been
 invoked in the session).

 The file ".netrwbook" holds bookmarks when netrw (and vim) is not active.  By
-default, its stored on the first directory on the user's |'runtimepath'|.
+default, it's stored on the first directory on the user's |'runtimepath'|.

 Related Topics:
 	|netrw-gb| how to return (go) to a bookmark
@@ -1422,20 +1418,20 @@ Related Topics:

 CHANGING TO A PREDECESSOR DIRECTORY		*netrw-u* *netrw-updir* {{{2

-Every time you change to a new directory (new for the current session), netrw
-will save the directory in a recently-visited directory history list (unless
-|g:netrw_dirhistmax| is zero; by default, it holds ten entries).  With the "u"
-map, one can change to an earlier directory (predecessor).  To do the
-opposite, see |netrw-U|.
+Every time you change to a new directory (new for the current session),
+netrw will save the directory in a recently-visited directory history
+list (unless |g:netrw_dirhistmax| is zero; by default, it's ten).  With the
+"u" map, one can change to an earlier directory (predecessor).  To do
+the opposite, see |netrw-U|.

-The "u" map also accepts counts to go back in the history several slots.  For
-your convenience, qb (see |netrw-qb|) lists the history number which may be
-used in that count.
+The "u" map also accepts counts to go back in the history several slots.
+For your convenience, qb (see |netrw-qb|) lists the history number which may
+be used in that count.

 						*.netrwhist*
 See |g:netrw_dirhistmax| for how to control the quantity of history stack
 slots.  The file ".netrwhist" holds history when netrw (and vim) is not
-active.  By default, its stored on the first directory on the user's
+active.  By default, it's stored on the first directory on the user's
 |'runtimepath'|.

 Related Topics:
@@ -1471,10 +1467,10 @@ changing the top of the tree listing.

 NETRW CLEAN					*netrw-clean* *:NetrwClean* {{{2

-With :NetrwClean one may easily remove netrw from one's home directory;
+With NetrwClean one may easily remove netrw from one's home directory;
 more precisely, from the first directory on your |'runtimepath'|.

-With :NetrwClean!, netrw will attempt to remove netrw from all directories on
+With NetrwClean!, netrw will attempt to remove netrw from all directories on
 your |'runtimepath'|.  Of course, you have to have write/delete permissions
 correct to do this.

@@ -1506,7 +1502,7 @@ Netrw determines which special handler by the following method:
    If g:netrw_browsex_viewer == '-', then netrwFileHandlers#Invoke() will be
    used instead (see |netrw_filehandler|).

-  * for Windows 32 or 64, the URL and FileProtocolHandler dlls are used.
+  * for Windows 32 or 64, the url and FileProtocolHandler dlls are used.
  * for Gnome (with gnome-open): gnome-open is used.
  * for KDE (with kfmclient)   : kfmclient is used
  * for Mac OS X               : open is used.
@@ -1522,10 +1518,9 @@ will apply a special handler to it (like "x" works when in a netrw buffer).
 One may also use visual mode (see |visual-start|) to select the text that the
 special handler will use.  Normally gx uses expand("<cfile>") to pick up the
 text under the cursor; one may change what |expand()| uses via the
-|g:netrw_gx| variable (options include "<cword>", "<cWORD>").  Note that
-expand("<cfile>") depends on the |'isfname'| setting.  Alternatively, one may
-select the text to be used by gx by making a visual selection (see
-|visual-block|) and then pressing gx.
+|g:netrw_gx| variable.  Alternatively, one may select the text to be used by
+gx via first making a visual selection (see |visual-block|) or by changing
+the |'isfname'| option (which is global, so netrw doesn't modify it).

 Associated setting variables:
 	|g:netrw_gx|	control how gx picks up the text under the cursor
@@ -1617,11 +1612,6 @@ A further approach is to delete files which match a pattern.
      This will cause the matching files to be marked.  Then,
      press "D".

-If your vim has 7.4 with patch#1107, then |g:netrw_localrmdir| no longer
-is used to remove directories; instead, vim's |delete()| is used with
-the "d" option.  Please note that only empty directories may be deleted
-with the "D" mapping.  Regular files are deleted with |delete()|, too.
-
 The |g:netrw_rm_cmd|, |g:netrw_rmf_cmd|, and |g:netrw_rmdir_cmd| variables are
 used to control the attempts to remove remote files and directories.  The
 g:netrw_rm_cmd is used with files, and its default value is:
@@ -1685,18 +1675,17 @@ DIRECTORY EXPLORATION COMMANDS  {{{2
 	  The [N] specifies a |g:netrw_winsize| just for the new :Lexplore
 	  window.

-	  Those who like this method often also like tree style displays;
+	  Those who like this method often also often like tree style displays;
 	  see |g:netrw_liststyle|.

-:[N]Lexplore! [dir] is similar to :Lexplore, except that the full-height
-	  Explorer window will open on the right hand side and an
-	  uninitialized |g:netrw_chgwin| will be set to 1 (eg. edits will
-	  preferentially occur in the leftmost window).
-
 	  Also see: |netrw-C|           |g:netrw_browse_split|   |g:netrw_wiw|
 		    |netrw-p| |netrw-P|   |g:netrw_chgwin|
 		    |netrw-c-tab|       |g:netrw_winsize|

+:[N]Lexplore! is like :Lexplore, except that the full-height Explorer window
+	  will open on the right hand side and an uninitialized |g:netrw_chgwin|
+	  will be set to 1.
+
 						*netrw-:Sexplore*
 :[N]Sexplore will always split the window before invoking the local-directory
 	  browser.  As with Explore, the splitting is normally done
@@ -1858,11 +1847,9 @@ EXECUTING FILE UNDER CURSOR VIA SYSTEM()			*netrw-X* {{{2

 Pressing X while the cursor is atop an executable file will yield a prompt
 using the filename asking for any arguments.  Upon pressing a [return], netrw
-will then call |system()| with that command and arguments.  The result will be
-displayed by |:echomsg|, and so |:messages| will repeat display of the result.
-Ansi escape sequences will be stripped out.
-
-See |cmdline-window| for directions for more on how to edit the arguments.
+will then call |system()| with that command and arguments.  The result will
+be displayed by |:echomsg|, and so |:messages| will repeat display of the
+result.  Ansi escape sequences will be stripped out.


 FORCING TREATMENT AS A FILE OR DIRECTORY	*netrw-gd* *netrw-gf* {{{2
@@ -2085,7 +2072,7 @@ Associated setting variables:	|g:netrw_localmkdir|   |g:netrw_mkdir_cmd|
 				|g:netrw_remote_mkdir| |netrw-%|


-MAKING THE BROWSING DIRECTORY THE CURRENT DIRECTORY	*netrw-cd* {{{2
+MAKING THE BROWSING DIRECTORY THE CURRENT DIRECTORY	*netrw-c* {{{2

 By default, |g:netrw_keepdir| is 1.  This setting means that the current
 directory will not track the browsing directory. (done for backwards
@@ -2100,9 +2087,6 @@ the two directories the same, use the "c" map (just type c).  That map will
 set Vim's notion of the current directory to netrw's current browsing
 directory.

-*netrw-c* : This map's name has been changed from "c" to cd (see |netrw-cd|).
-          This change was done to allow for |netrw-cb| and |netrw-cB| maps.
-
 Associated setting variable: |g:netrw_keepdir|

 MARKING FILES					*netrw-:MF*	*netrw-mf* {{{2
@@ -2147,7 +2131,6 @@ The following netrw maps make use of marked files:
    |netrw-mg|	Apply vimgrep to marked files
    |netrw-mm|	Move marked files to target
    |netrw-mp|	Print marked files
-    |netrw-ms|	Netrw will source marked files
    |netrw-mt|	Set target for |netrw-mm| and |netrw-mc|
    |netrw-mT|	Generate tags using marked files
    |netrw-mv|	Apply vim command to marked files
@@ -2222,9 +2205,6 @@ converts "*" into ".*" (see |regexp|) and marks files based on that.  In the
 future I may make it possible to use |regexp|s instead of glob()-style
 expressions (yet-another-option).

-See |cmdline-window| for directions on more on how to edit the regular
-expression.
-

 MARKED FILES, ARBITRARY VIM COMMAND				*netrw-mv*  {{{2
 	    (See |netrw-mf| and |netrw-mr| for how to mark files)
@@ -2238,9 +2218,8 @@ the local marked file list, individually:
 	* run vim command
 	* sil! keepalt wq!

-A prompt, "Enter vim command: ", will be issued to elicit the vim command you
-wish used.  See |cmdline-window| for directions for more on how to edit the
-command.
+A prompt, "Enter vim command: ", will be issued to elicit the vim command
+you wish used.


 MARKED FILES, ARBITRARY SHELL COMMAND				*netrw-mx* {{{2
@@ -2291,17 +2270,7 @@ MARKED FILES: ARGUMENT LIST				*netrw-ma* *netrw-mA*
 Using ma, one moves filenames from the marked file list to the argument list.
 Using mA, one moves filenames from the argument list to the marked file list.

-See Also: |netrw-cb| |netrw-cB| |netrw-qF| |argument-list| |:args|
-
-
-MARKED FILES: BUFFER LIST				*netrw-cb* *netrw-cB*
-	    (See |netrw-mf| and |netrw-mr| for how to mark files)
-		      (uses the global marked-file list)
-
-Using cb, one moves  filenames from the marked file list to the buffer list.
-Using cB, one copies filenames from the buffer list to the marked file list.
-
-See Also: |netrw-ma| |netrw-mA| |netrw-qF| |buffer-list| |:buffers|
+See Also: |netrw-qF| |argument-list| |:args|


 MARKED FILES: COMPRESSION AND DECOMPRESSION		*netrw-mz* {{{2
@@ -2337,8 +2306,8 @@ One may also copy directories and their contents (local only) to a target
 directory.

 Associated setting variables:
-	|g:netrw_localcopycmd|		|g:netrw_localcopycmdopt|
-	|g:netrw_localcopydircmd|	|g:netrw_localcopydircmdopt|
+	|g:netrw_localcopycmd|
+	|g:netrw_localcopydircmd|
 	|g:netrw_ssh_cmd|

 MARKED FILES: DIFF						*netrw-md* {{{2
@@ -2483,8 +2452,8 @@ When a remote set of files are tagged, the resulting tags file is "obtained";
 ie. a copy is transferred to the local system's directory.  The now local tags
 file is then modified so that one may use it through the network.  The
 modification made concerns the names of the files in the tags; each filename is
-preceded by the netrw-compatible URL used to obtain it.  When one subsequently
-uses one of the go to tag actions (|tags|), the URL will be used by netrw to
+preceded by the netrw-compatible url used to obtain it.  When one subsequently
+uses one of the go to tag actions (|tags|), the url will be used by netrw to
 edit the desired file and go to the tag.

 Associated setting variables: |g:netrw_ctags| |g:netrw_ssh_cmd|
@@ -2586,8 +2555,8 @@ your browsing preferences.  (see also: |netrw-settings|)
 				    editing.  It will also use the specified tab
 				    and window numbers to perform editing
 				    (see |clientserver|, |netrw-ctrl-r|)
-				This option does not affect the production of
-				|:Lexplore| windows.
+				This option does not affect |:Lexplore|
+				windows.

 				Related topics:
 				    |g:netrw_alto|	|g:netrw_altv|
@@ -2746,7 +2715,6 @@ your browsing preferences.  (see also: |netrw-settings|)
  *g:netrw_home*		The home directory for where bookmarks and
 				history are saved (as .netrwbook and
 				.netrwhist).
-				Netrw uses |expand()|on the string.
 				 default: the first directory on the
 				         |'runtimepath'|

@@ -2767,7 +2735,7 @@ your browsing preferences.  (see also: |netrw-settings|)
 				 default: (if ssh is executable)
 				          "ssh HOSTNAME ls -FLa"

-  *g:netrw_list_cmd_options*	If this variable exists, then its contents are
+ *g:netrw_list_cmd_options*	If this variable exists, then its contents are
 				appended to the g:netrw_list_cmd.  For
 				example, use "2>/dev/null" to get rid of banner
 				messages on unix systems.
@@ -2793,52 +2761,26 @@ your browsing preferences.  (see also: |netrw-settings|)
 				 let g:netrw_list_hide= netrw_gitignore#Hide().'.*\.swp$'
 				default: ""

-  *g:netrw_localcopycmd*	="cp"           Linux/Unix/MacOS/Cygwin
-				=expand("$COMSPEC")             Windows
+  *g:netrw_localcopycmd*	="cp" Linux/Unix/MacOS/Cygwin
+				="copy" Windows
 				Copies marked files (|netrw-mf|) to target
 				directory (|netrw-mt|, |netrw-mc|)

-  *g:netrw_localcopycmdopt*	=''             Linux/Unix/MacOS/Cygwin
-  				=' \c copy'                     Windows
-				Options for the |g:netrw_localcopycmd|
-
-  *g:netrw_localcopydircmd*	="cp"           Linux/Unix/MacOS/Cygwin
- 				=expand("$COMSPEC")             Windows
+ *g:netrw_localcopydircmd*	="cp -R"	Linux/Unix/MacOS/Cygwin
+				="xcopy /e /c /h/ /i /k"	Windows
 				Copies directories to target directory.
 				(|netrw-mc|, |netrw-mt|)

-  *g:netrw_localcopydircmdopt*	=" -R"          Linux/Unix/MacOS/Cygwin
-				=" /c xcopy /e /c /h/ /i /k"    Windows
-				Options for |g:netrw_localcopydircmd|
+  *g:netrw_localmkdir*		command for making a local directory
+				 default: "mkdir"

-  *g:netrw_localmkdir*		="mkdir"        Linux/Unix/MacOS/Cygwin
-				=expand("$COMSPEC")             Windows
-                                command for making a local directory
-
-  *g:netrw_localmkdiropt*	=""             Linux/Unix/MacOS/Cygwin
-				=" /c mkdir"                    Windows
-				Options for |g:netrw_localmkdir|
-
-  *g:netrw_localmovecmd*	="mv"           Linux/Unix/MacOS/Cygwin
-				=expand("$COMSPEC")             Windows
+  *g:netrw_localmovecmd*	="mv" Linux/Unix/MacOS/Cygwin
+				="move" Windows
 				Moves marked files (|netrw-mf|) to target
 				directory (|netrw-mt|, |netrw-mm|)

-  *g:netrw_localmovecmdopt*	=""             Linux/Unix/MacOS/Cygwin
-				=" /c move"                     Windows
-				Options for |g:netrw_localmovecmd|
-
-  *g:netrw_localrmdir*		="rmdir"        Linux/Unix/MacOS/Cygwin
- 				=expand("$COMSPEC")             Windows
-				Remove directory command (rmdir)
-				This variable is only used if your vim is
-				earlier than 7.4 or if your vim doesn't
-				have patch#1107.  Otherwise, |delete()|
-				is used with the "d" option.
-
-  *g:netrw_localrmdiropt*	=""             Linux/Unix/MacOS/Cygwin
-				=" /c rmdir"                    Windows
-				Options for |g:netrw_localrmdir|
+  *g:netrw_localrmdir*		remove directory command (rmdir)
+				 default: "rmdir"

  *g:netrw_maxfilenamelen*	=32 by default, selected so as to make long
 				    listings fit on 80 column displays.
@@ -2951,23 +2893,17 @@ your browsing preferences.  (see also: |netrw-settings|)
 					netrwTilde   : *
 					netrwTmp     : tmp* *tmp

-				In addition, those groups mentioned in
-				|'suffixes'| are also added to the special
-				file highlighting group.
-				 These syntax highlighting groups are linked
-				to netrwGray or Folded by default
-				(see |hl-Folded|), but one may put lines like >
+				These syntax highlighting groups are linked
+				to Folded or DiffChange by default
+				(see |hl-Folded| and |hl-DiffChange|), but
+				one may put lines like >
 					hi link netrwCompress Visual
 <				into one's <.vimrc> to use one's own
 				preferences.  Alternatively, one may
-				put such specifications into >
-					.vim/after/syntax/netrw.vim.
-<				 The netrwGray highlighting is set up by
-				netrw when >
-	       				* netrwGray has not been previously
-					  defined
-					* the gui is running
-<				 As an example, I myself use a dark-background
+				put such specifications into
+				.vim/after/syntax/netrw.vim.
+
+				As an example, I myself use a dark-background
 				colorscheme with the following in
 				.vim/after/syntax/netrw.vim: >

@@ -3202,8 +3138,8 @@ If there are no marked files: (see |netrw-mf|)

    Renaming files and directories involves moving the cursor to the
    file/directory to be moved (renamed) and pressing "R".  You will then be
-    queried for what you want the file/directory to be renamed to.  You may
-    select a range of lines with the "V" command (visual selection), and then
+    queried for what you want the file/directory to be renamed to  You may select
+    a range of lines with the "V" command (visual selection), and then
    press "R"; you will be queried for each file as to what you want it
    renamed to.

@@ -3235,20 +3171,16 @@ If there are marked files:  (see |netrw-mf|)

    Note that moving files is a dangerous operation; copies are safer.  That's
    because a "move" for remote files is actually a copy + delete -- and if
-    the copy fails and the delete succeeds you may lose the file.
+    the copy fails and the delete does not, you may lose the file.
    Use at your own risk.

-The *g:netrw_rename_cmd* variable is used to implement remote renaming.  By
-default its value is: >
+The g:netrw_rename_cmd variable is used to implement remote renaming.  By
+default its value is:

 	ssh HOSTNAME mv
-<
-One may rename a block of files and directories by selecting them with
-V (|linewise-visual|) when using thin style.

-See |cmdline-editing| for more on how to edit the command line; in particular,
-you'll find <ctrl-f> (initiates cmdline window editing) and <ctrl-c> (uses the
-command line under the cursor) useful in conjunction with the R command.
+One may rename a block of files and directories by selecting them with
+V (|linewise-visual|) when using thin style


 SELECTING SORTING STYLE			*netrw-s* *netrw-sort* {{{2
@@ -3269,8 +3201,8 @@ number.  Subsequent selection of a file to edit (|netrw-cr|) will use that
 window.

 	* C : by itself, will select the current window holding a netrw buffer
-	  for subsequent editing via |netrw-cr|.  The C mapping is only available
-	  while in netrw buffers.
+	  for editing via |netrw-cr|.  The C mapping is only available while in
+	  netrw buffers.

 	* [count]C : the count will be used as the window number to be used
 	  for subsequent editing via |netrw-cr|.
@@ -3283,7 +3215,7 @@ window.
 Using >
 	let g:netrw_chgwin= -1
 will restore the default editing behavior
-(ie. subsequent editing will use the current window).
+(ie. editing will use the current window).

 Related topics:			|netrw-cr| |g:netrw_browse_split|
 Associated setting variables:	|g:netrw_chgwin|
@@ -3304,9 +3236,9 @@ only if your terminal supports differentiating <c-tab> from a plain

  * Else bring up a |:Lexplore| window

-If |g:netrw_usetab| exists and is zero, or if there is a pre-existing mapping
+If |g:netrw_usetab| exists or is zero, or if there is a pre-existing mapping
 for <c-tab>, then the <c-tab> will not be mapped.  One may map something other
-than a <c-tab>, too: (but you'll still need to have had |g:netrw_usetab| set). >
+than a <c-tab>, too: (but you'll still need to have had g:netrw_usetab set) >

 	nmap <unique> (whatever)	<Plug>NetrwShrink
 <
@@ -3339,10 +3271,9 @@ The user function is passed one argument; it resembles >

 	fun! ExampleUserMapFunc(islocal)
 <
-where a:islocal is 1 if its a local-directory system call or 0 when
+where a:islocal is 1 if it's a local-directory system call or 0 when
 remote-directory system call.

-			        *netrw-call*  *netrw-expose*  *netrw-modify*
 Use netrw#Expose("varname")          to access netrw-internal (script-local)
 				     variables.
 Use netrw#Modify("varname",newvalue) to change netrw-internal variables.
@@ -3664,7 +3595,7 @@ Example: Clear netrw's marked file list via a mapping on gu >

 								*netrw-p16*
 	P16. When editing remote files (ex. :e ftp://hostname/path/file),
-	     under Windows I get an |E303| message complaining that its unable
+	     under Windows I get an |E303| message complaining that it's unable
 	     to open a swap file.

 	     (romainl) It looks like you are starting Vim from a protected
@@ -3718,7 +3649,7 @@ Example: Clear netrw's marked file list via a mapping on gu >
 	P21. I've made a directory (or file) with an accented character, but
 		netrw isn't letting me enter that directory/read that file:

-		Its likely that the shell or o/s is using a different encoding
+		It's likely that the shell or o/s is using a different encoding
 		than you have vim (netrw) using.  A patch to vim supporting
 		"systemencoding" may address this issue in the future; for
 		now, just have netrw use the proper encoding.  For example: >
@@ -3834,102 +3765,6 @@ netrw:
 ==============================================================================
 12. History						*netrw-history* {{{1

-	v162:	Sep 19, 2016	* (haya14busa) pointed out two syntax errors
-				  with a patch; these are now fixed.
-		Oct 26, 2016	* I started using mate-terminal and found that
-				  x and gx (|netrw-x| and |netrw-gx|) were no
-				  longer working.  Fixed (using atril when
-				  $DESKTOP_SESSION is "mate").
-		Nov 04, 2016	* (Martin Vuille) pointed out that @+ was
-				  being restored with keepregstar rather than
-				  keepregplus.
-		Nov 09, 2016	* Broke apart the command from the options,
-				  mostly for Windows.  Introduced new netrw
-				  settings: |g:netrw_localcopycmdopt|
-				  |g:netrw_localcopydircmdopt| |g:netrw_localmkdiropt|
-				  |g:netrw_localmovecmdopt| |g:netrw_localrmdiropt|
-		Nov 21, 2016	* (mattn) provided a patch for preview; swapped
-				  winwidth() with winheight()
-		Nov 22, 2016	* (glacambre) reported that files containing
-				  spaces weren't being obtained properly via
-				  scp.  Fix: apparently using single quotes
-				  such as with 'file name' wasn't enough; the
-				  spaces inside the quotes also had to be
-				  escaped (ie. 'file\ name').
-				* Also fixed obtain (|netrw-O|) to be able to
-				  obtain files with spaces in their names
-		Dec 20, 2016	* (xc1427) Reported that using "I" (|netrw-I|)
-				  when atop "Hiding" in the banner also caused
-				  the active-banner hiding control to occur
-		Jan 03, 2017	* (Enno Nagel) reported that attempting to
-				  apply netrw to a directory that was without
-				  read permission caused a syntax error.
-		Jan 13, 2017	* (Ingo Karkat) provided a patch which makes
-				  using netrw#Call() better.  Now returns
-				  value of internal routines return, for example.
-		Jan 13, 2017	* (Ingo Karkat) changed netrw#FileUrlRead to
-				  use |:edit| instead of |:read|.  I also
-				  changed the routine name to netrw#FileUrlEdit.
-		Jan 16, 2017	* (Sayem) reported a problem where :Lexplore
-				  could generate a new listing buffer and
-				  window instead of toggling the netrw display.
-				  Unfortunately, the directions for eliciting
-				  the problem weren't complete, so I may or
-				  may not have fixed that issue.
-		Feb 06, 2017	* Implemented cb and cB.  Changed "c" to "cd".
-				  (see |netrw-cb|, |netrw-cB|, and |netrw-cd|)
-		Mar 21, 2017	* previously, netrw would specify (safe) settings
-				  even when the setting was already safe for
-				  netrw.  Netrw now attempts to leave such
-				  already-netrw-safe settings alone.
-				  (affects s:NetrwOptionRestore() and
-				  s:NetrwSafeOptions(); also introduced
-				  s:NetrwRestoreSetting())
-		Jun 26, 2017	* (Christian Brabandt) provided a patch to
-				  allow curl to follow redirects (ie. -L
-				  option)
-		Jun 26, 2017	* (Callum Howard) reported a problem with
-				  :Lexpore not removing the Lexplore window
-				  after a change-directory
-		Aug 30, 2017	* (Ingo Karkat) one cannot switch to the
-				  previously edited file (e.g. with CTRL-^)
-				  after editing a file:// URL.  Patch to
-				  have a "keepalt" included.
-		Oct 17, 2017	* (Adam Faryna) reported that gn (|netrw-gn|)
-				  did not work on directories in the current
-				  tree
-	v157:	Apr 20, 2016	* (Nicola) had set up a "nmap <expr> ..." with
-				  a function that returned a 0 while silently
-				  invoking a shell command.  The shell command
-				  activated a ShellCmdPost event which in turn
-				  called s:LocalBrowseRefresh().  That looks
-				  over all netrw buffers for changes needing
-				  refreshes.  However, inside a |:map-<expr>|,
-				  tab and window changes are disallowed.  Fixed.
-				  (affects netrw's s:LocalBrowseRefresh())
-				* |g:netrw_localrmdir| not used any more, but
-				  the relevant patch that causes |delete()| to
-				  take over was #1107 (not #1109).
-				* |expand()| is now used on |g:netrw_home|;
-				  consequently, g:netrw_home may now use
-				  environment variables
-				* s:NetrwLeftmouse and s:NetrwCLeftmouse will
-				  return without doing anything if invoked
-				  when inside a non-netrw window
-		Jun 15, 2016	* gx now calls netrw#GX() which returns
-				  the word under the cursor.  The new
-				  wrinkle: if one is in a netrw buffer,
-				  then netrw's s:NetrwGetWord().
-		Jun 22, 2016	* Netrw was executing all its associated
-				  Filetype commands silently; I'm going
-				  to try doing that "noisily" and see if
-				  folks have a problem with that.
-		Aug 12, 2016	* Changed order of tool selection for
-				  handling http://... viewing.
-				  (Nikolay Aleksandrovich Pavlov)
-		Aug 21, 2016	* Included hiding/showing/all for tree
-				  listings
-				* Fixed refresh (^L) for tree listings
 	v156:	Feb 18, 2016	* Changed =~ to =~# where appropriate
 		Feb 23, 2016	* s:ComposePath(base,subdir) now uses
 				  fnameescape() on the base portion
@@ -3961,9 +3796,9 @@ netrw:
 				  tell me how they're useful and should be
 				  retained?
 		Nov 20, 2015	* Added |netrw-ma| and |netrw-mA| support
-		Nov 20, 2015	* gx (|netrw-gx|) on a URL downloaded the
+		Nov 20, 2015	* gx (|netrw-gx|) on an url downloaded the
 				  file in addition to simply bringing up the
-				  URL in a browser.  Fixed.
+				  url in a browser.  Fixed.
 		Nov 23, 2015	* Added |g:netrw_sizestyle| support
 		Nov 27, 2015	* Inserted a lot of <c-u>s into various netrw
 				  maps.
@@ -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
 print ASCII text using the national character set you may see some unexpected
 characters.  If you want true ASCII code printing then you need to configure
-Vim to output ASCII characters for the ASCII code range with 'printmbfont'.
+VIM to output ASCII characters for the ASCII code range with 'printmbfont'.

 It is possible to define your own multi-byte character set although this
 should not be attempted lightly.  A discussion on the process if beyond the
@@ -525,13 +525,13 @@ print job completing.
 There are a number of possible causes as to why the printing may have failed:

 - Wrong version of the prolog resource file.  The prolog resource file
-  contains some PostScript that Vim needs to be able to print.  Each version
-  of Vim needs one particular version.  Make sure you have correctly installed
+  contains some PostScript that VIM needs to be able to print.  Each version
+  of VIM needs one particular version.  Make sure you have correctly installed
  the runtime files, and don't have any old versions of a file called prolog
  in the print directory in your 'runtimepath' directory.

 - Paper size.  Some PostScript printers will abort printing a file if they do
-  not support the requested paper size.  By default Vim uses A4 paper.  Find
+  not support the requested paper size.  By default VIM uses A4 paper.  Find
  out what size paper your printer normally uses and set the appropriate paper
  size with 'printoptions'.  If you cannot find the name of the paper used,
  measure a sheet and compare it with the table of supported paper sizes listed
@@ -668,7 +668,7 @@ complex print document creation.

 N-UP PRINTING

-The psnup utility takes an existing PostScript file generated from Vim and
+The psnup utility takes an existing PostScript file generated from VIM and
 convert it to an n-up version.  The simplest way to create a 2-up printout is
 to first create a PostScript file with: >

@@ -724,16 +724,16 @@ There are a couple of points to bear in mind:
 ==============================================================================
 8. Formfeed Characters					*printing-formfeed*

-By default Vim does not do any special processing of |formfeed| control
-characters.  Setting the 'printoptions' formfeed item will make Vim recognize
+By default VIM does not do any special processing of |formfeed| control
+characters.  Setting the 'printoptions' formfeed item will make VIM recognize
 formfeed characters and continue printing the current line at the beginning
 of the first line on a new page.  The use of formfeed characters provides
 rudimentary print control but there are certain things to be aware of.

-Vim will always start printing a line (including a line number if enabled)
+VIM will always start printing a line (including a line number if enabled)
 containing a formfeed character, even if it is the first character on the
 line.  This means if a line starting with a formfeed character is the first
-line of a page then Vim will print a blank page.
+line of a page then VIM will print a blank page.

 Since the line number is printed at the start of printing the line containing
 the formfeed character, the remainder of the line printed on the new page
@@ -742,7 +742,7 @@ lines of a long line when wrap in 'printoptions' is enabled).

 If the formfeed character is the last character on a line, then printing will
 continue on the second line of the new page, not the first.  This is due to
-Vim processing the end of the line after the formfeed character and moving
+VIM processing the end of the line after the formfeed character and moving
 down a line to continue printing.

 Due to the points made above it is recommended that when formfeed character
@@ -1,4 +1,4 @@
-*quickfix.txt*  For Vim version 8.0.  Last change: 2018 Mar 04
+*quickfix.txt*  For Vim version 8.0.  Last change: 2016 Jul 17


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -44,34 +44,16 @@ From inside Vim an easy way to run a command and handle the output is with the
 The 'errorformat' option should be set to match the error messages from your
 compiler (see |errorformat| below).

-							*quickfix-ID*
-Each quickfix list has a unique identifier called the quickfix ID and this
-number will not change within a Vim session. The getqflist() function can be
-used to get the identifier assigned to a list. There is also a quickfix list
-number which may change whenever more than ten lists are added to a quickfix
-stack.
-
 						*location-list* *E776*
-A location list is a window-local quickfix list. You get one after commands
-like `:lvimgrep`, `:lgrep`, `:lhelpgrep`, `:lmake`, etc., which create a
-location list instead of a quickfix list as the corresponding `:vimgrep`,
-`:grep`, `:helpgrep`, `:make` do.
-A location list is associated with a window and each window can have a
-separate location list.  A location list can be associated with only one
-window.  The location list is independent of the quickfix list.
+A location list is similar to a quickfix list and contains a list of positions
+in files.  A location list is associated with a window and each window can
+have a separate location list.  A location list can be associated with only
+one window.  The location list is independent of the quickfix list.

 When a window with a location list is split, the new window gets a copy of the
 location list.  When there are no longer any references to a location list,
 the location list is destroyed.

-						*quickfix-changedtick*
-Every quickfix and location list has a read-only changedtick variable that
-tracks the total number of changes made to the list.  Every time the quickfix
-list is modified, this count is incremented. This can be used to perform an
-action only when the list has changed.  The getqflist() and getloclist()
-functions can be used to query the current value of changedtick.  You cannot
-change the changedtick variable.
-
 The following quickfix commands can be used.  The location list commands are
 similar to the quickfix commands, replacing the 'c' prefix in the quickfix
 command with 'l'.
@@ -182,9 +164,6 @@ processing a quickfix or location list command, it will be aborted.
 			keep Vim running while compiling.  If you give the
 			name of the errorfile, the 'errorfile' option will
 			be set to [errorfile].  See |:cc| for [!].
-			If the encoding of the error file differs from the
-			'encoding' option, you can use the 'makeencoding'
-			option to specify the encoding.

 							*:lf* *:lfile*
 :lf[ile][!] [errorfile]	Same as ":cfile", except the location list for the
@@ -196,9 +175,6 @@ processing a quickfix or location list command, it will be aborted.
 :cg[etfile] [errorfile]					*:cg* *:cgetfile*
 			Read the error file.  Just like ":cfile" but don't
 			jump to the first error.
-			If the encoding of the error file differs from the
-			'encoding' option, you can use the 'makeencoding'
-			option to specify the encoding.


 :lg[etfile] [errorfile]					*:lg* *:lgetfile*
@@ -209,9 +185,6 @@ processing a quickfix or location list command, it will be aborted.
 :caddf[ile] [errorfile]	Read the error file and add the errors from the
 			errorfile to the current quickfix list. If a quickfix
 			list is not present, then a new list is created.
-			If the encoding of the error file differs from the
-			'encoding' option, you can use the 'makeencoding'
-			option to specify the encoding.

 							*:laddf* *:laddfile*
 :laddf[ile] [errorfile]	Same as ":caddfile", except the location list for the
@@ -330,9 +303,9 @@ deleted for some reason, the message "line changed" is shown to warn you that
 the error location may not be correct.  If you quit Vim and start again the
 marks are lost and the error locations may not be correct anymore.

-Two autocommands are available for running commands before and after a
-quickfix command (':make', ':grep' and so on) is executed. See
-|QuickFixCmdPre| and |QuickFixCmdPost| for details.
+If vim is built with |+autocmd| support, two autocommands are available for
+running commands before and after a quickfix command (':make', ':grep' and so
+on) is executed. See |QuickFixCmdPre| and |QuickFixCmdPost| for details.

 						*QuickFixCmdPost-example*
 When 'encoding' differs from the locale, the error messages may have a
@@ -347,52 +320,7 @@ use this code: >
 	endfunction

 	au QuickfixCmdPost make call QfMakeConv()
-Another option is using 'makeencoding'.

-							*quickfix-title*
-Every quickfix and location list has a title. By default the title is set to
-the command that created the list. The |getqflist()| and |getloclist()|
-functions can be used to get the title of a quickfix and a location list
-respectively. The |setqflist()| and |setloclist()| functions can be used to
-modify the title of a quickfix and location list respectively. Examples: >
-	call setqflist([], 'a', {'title' : 'Cmd output'})
-	echo getqflist({'title' : 1})
-	call setloclist(3, [], 'a', {'title' : 'Cmd output'})
-	echo getloclist(3, {'title' : 1})
-<
-							*quickfix-size*
-You can get the number of entries (size) in a quickfix and a location list
-using the |getqflist()| and |getloclist()| functions respectively. Examples: >
-	echo getqflist({'size' : 1})
-	echo getloclist(5, {'size' : 1})
-<
-							*quickfix-context*
-Any Vim type can be associated as a context with a quickfix or location list.
-The |setqflist()| and the |setloclist()| functions can be used to associate a
-context with a quickfix and a location list respectively. The |getqflist()|
-and the |getloclist()| functions can be used to retrieve the context of a
-quickfix and a location list respectively. This is useful for a Vim plugin
-dealing with multiple quickfix/location lists.
-Examples: >
-
-	let somectx = {'name' : 'Vim', 'type' : 'Editor'}
-	call setqflist([], 'a', {'context' : somectx})
-	echo getqflist({'context' : 1})
-
-	let newctx = ['red', 'green', 'blue']
-	call setloclist(2, [], 'a', {'id' : qfid, 'context' : newctx})
-	echo getloclist(2, {'id' : qfid, 'context' : 1})
-<
-							*quickfix-parse*
-You can parse a list of lines using 'errorformat' without creating or
-modifying a quickfix list using the |getqflist()| function. Examples: >
-	echo getqflist({'lines' : ["F1:10:Line10", "F2:20:Line20"]})
-	echo getqflist({'lines' : systemlist('grep -Hn quickfix *')})
-This returns a dictionary where the 'items' key contains the list of quickfix
-entries parsed from lines. The following shows how to use a custom
-'errorformat' to parse the lines without modifying the 'errorformat' option: >
-	echo getqflist({'efm' : '%f#%l#%m', 'lines' : ['F1#10#Line']})
-<

 EXECUTE A COMMAND IN ALL THE BUFFERS IN QUICKFIX OR LOCATION LIST:
 							*:cdo*
@@ -484,9 +412,7 @@ EXECUTE A COMMAND IN ALL THE BUFFERS IN QUICKFIX OR LOCATION LIST:
 			which will indicate the command that produced the
 			quickfix list. This can be used to compose a custom
 			status line if the value of 'statusline' is adjusted
-			properly. Whenever this buffer is modified by a
-			quickfix command or function, the |b:changedtick|
-			variable is incremented.
+			properly.

 							*:lop* *:lopen*
 :lop[en] [height]	Open a window to show the location list for the
@@ -533,11 +459,7 @@ keep its height, ignoring 'winheight' and 'equalalways'.  You can change the
 height manually (e.g., by dragging the status line above it with the mouse).

 In the quickfix window, each line is one error.  The line number is equal to
-the error number.  The current entry is highlighted with the QuickFixLine
-highlighting.  You can change it to your liking, e.g.: >
-	:hi QuickFixLine ctermbg=Yellow guibg=Yellow
-
-You can use ":.cc" to jump to the error under the cursor.
+the error number.  You can use ":.cc" to jump to the error under the cursor.
 Hitting the <Enter> key or double-clicking the mouse on a line has the same
 effect.  The file containing the error is opened in the window above the
 quickfix window.  If there already is a window for that file, it is used
@@ -594,13 +516,6 @@ In all of the above cases, if the location list for the selected window is not
 yet set, then it is set to the location list displayed in the location list
 window.

-							*quickfix-window-ID*
-You can use the |getqflist()| and |getloclist()| functions to obtain the
-window ID of the quickfix window and location list window respectively (if
-present).  Examples: >
-	echo getqflist({'winid' : 1}).winid
-	echo getloclist(2, {'winid' : 1}).winid
-<
 =============================================================================
 3. Using more than one list of errors			*quickfix-error-lists*

@@ -645,20 +560,12 @@ list, one newer list is overwritten.  This is especially useful if you are
 browsing with ":grep" |grep|.  If you want to keep the more recent error
 lists, use ":cnewer 99" first.

-To get the number of lists in the quickfix and location list stack, you can
-use the |getqflist()| and |getloclist()| functions respectively with the list
-number set to the special value '$'. Examples: >
-	echo getqflist({'nr' : '$'}).nr
-	echo getloclist(3, {'nr' : '$'}).nr
-To get the number of the current list in the stack: >
-	echo getqflist({'nr' : 0}).nr
-<
 =============================================================================
 4. Using :make						*:make_makeprg*

 							*:mak* *:make*
-:mak[e][!] [arguments]	1. All relevant |QuickFixCmdPre| autocommands are
-			   executed.
+:mak[e][!] [arguments]	1. If vim was built with |+autocmd|, all relevant
+			   |QuickFixCmdPre| autocommands are executed.
 			2. If the 'autowrite' option is on, write any changed
 			   buffers
 			3. An errorfile name is made from 'makeef'.  If
@@ -670,17 +577,15 @@ To get the number of the current list in the stack: >
 			   errorfile (for Unix it is also echoed on the
 			   screen).
 			5. The errorfile is read using 'errorformat'.
-			6. All relevant |QuickFixCmdPost| autocommands are
-			   executed.  See example below.
+			6. If vim was built with |+autocmd|, all relevant
+			   |QuickFixCmdPost| autocommands are executed.
+			   See example below.
 			7. If [!] is not given the first error is jumped to.
 			8. The errorfile is deleted.
 			9. You can now move through the errors with commands
 			   like |:cnext| and |:cprevious|, see above.
 			This command does not accept a comment, any "
 			characters are considered part of the arguments.
-			If the encoding of the program output differs from the
-			'encoding' option, you can use the 'makeencoding'
-			option to specify the encoding.

 							*:lmak* *:lmake*
 :lmak[e][!] [arguments]
@@ -740,7 +645,6 @@ read the error messages: >
 	au QuickfixCmdPost make call QfMakeConv()

 (Example by Faque Cheng)
-Another option is using 'makeencoding'.

 ==============================================================================
 5. Using :vimgrep and :grep				*grep* *lid*
@@ -855,9 +759,6 @@ id-utils) in a similar way to its compiler integration (see |:make| above).
 			When 'grepprg' is "internal" this works like
 			|:vimgrep|.  Note that the pattern needs to be
 			enclosed in separator characters then.
-			If the encoding of the program output differs from the
-			'encoding' option, you can use the 'makeencoding'
-			option to specify the encoding.

 							    *:lgr* *:lgrep*
 :lgr[ep][!] [arguments]	Same as ":grep", except the location list for the
@@ -882,10 +783,6 @@ id-utils) in a similar way to its compiler integration (see |:make| above).
 				  \ | catch /E480:/
 				  \ | endtry"
 <
-			If the encoding of the program output differs from the
-			'encoding' option, you can use the 'makeencoding'
-			option to specify the encoding.
-
 							*:lgrepa* *:lgrepadd*
 :lgrepa[dd][!] [arguments]
 			Same as ":grepadd", except the location list for the
@@ -981,7 +878,7 @@ need to write down a "todo" list.


 The Vim plugins in the "compiler" directory will set options to use the
-selected compiler.  For `:compiler` local options are set, for `:compiler!`
+selected compiler.  For ":compiler" local options are set, for ":compiler!"
 global options.
 							*current_compiler*
 To support older Vim versions, the plugins always use "current_compiler" and
@@ -1502,7 +1399,7 @@ prints information about entering a directory in the form "Making all in dir".
   Making all in dir2		  ./dir1/dir2

   This can be solved by printing absolute directories in the "enter directory"
-   message or by printing "leave directory" messages.
+   message or by printing "leave directory" messages..

 To avoid this problem, ensure to print absolute directory names and "leave
 directory" messages.
@@ -1,4 +1,4 @@
-*quickref.txt*  For Vim version 8.0.  Last change: 2018 Feb 11
+*quickref.txt*  For Vim version 8.0.  Last change: 2016 Aug 21


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -618,8 +618,7 @@ Short explanation of each option:		*option-list*
 'backupext'	  'bex'     extension used for the backup file
 'backupskip'	  'bsk'     no backup for files that match these patterns
 'balloondelay'	  'bdlay'   delay in mS before a balloon may pop up
-'ballooneval'	  'beval'     switch on balloon evaluation in the GUI
-'balloonevalterm' 'bevalterm' switch on balloon evaluation in the terminal
+'ballooneval'	  'beval'   switch on balloon evaluation
 'balloonexpr'	  'bexpr'   expression to show in balloon
 'belloff'	  'bo'	    do not ring the bell for these reasons
 'binary'	  'bin'     read/write/edit file in binary mode
@@ -646,7 +645,6 @@ Short explanation of each option:		*option-list*
 'cmdwinheight'	  'cwh'     height of the command-line window
 'colorcolumn'	  'cc'	    columns to highlight
 'columns'	  'co'	    number of columns in the display
-'columnspace'	  'csp'     number of pixel columns to use between characters
 'comments'	  'com'     patterns that can start a comment line
 'commentstring'   'cms'     template for comments; used for fold marker
 'compatible'	  'cp'	    behave Vi-compatible as much as possible
@@ -754,7 +752,6 @@ Short explanation of each option:		*option-list*
 'iminsert'	  'imi'     use :lmap or IM in Insert mode
 'imsearch'	  'ims'     use :lmap or IM when typing a search pattern
 'imstatusfunc'    'imsf'    function to obtain X input method status
-'imstyle'	  'imst'    specifies the input style of the input method
 'include'	  'inc'     pattern to be used to find an include file
 'includeexpr'	  'inex'    expression used to process an include line
 'incsearch'	  'is'	    highlight match while typing search pattern
@@ -785,15 +782,12 @@ Short explanation of each option:		*option-list*
 'listchars'	  'lcs'     characters for displaying in list mode
 'loadplugins'	  'lpl'     load plugin scripts when starting up
 'luadll'		    name of the Lua dynamic library
-'mzschemedll'		    name of the MzScheme dynamic library
-'mzschemegcdll'		    name of the MzScheme dynamic library for GC
 'macatsui'		    Mac GUI: use ATSUI text drawing
 'macligatures'		    display ligatures (MacVim GUI only)
 'macmeta'	  'mmta'    use option as meta key (MacVim GUI only)
 'macthinstrokes'	    render the text lighter by using thin strokes (MacVim GUI only)
 'magic'			    changes special characters in search patterns
 'makeef'	  'mef'     name of the errorfile for ":make"
-'makeencoding'	  'menc'    encoding of external make/grep commands
 'makeprg'	  'mp'	    program to use for the ":make" command
 'matchpairs'	  'mps'     pairs of characters that "%" can match
 'matchtime'	  'mat'     tenths of a second to show matching paren
@@ -845,12 +839,8 @@ Short explanation of each option:		*option-list*
 'printoptions'	  'popt'    controls the format of :hardcopy output
 'prompt'	  'prompt'  enable prompt in Ex mode
 'pumheight'	  'ph'	    maximum height of the popup menu
-'pumwidth'	  'pw'	    minimum width of the popup menu
 'pythondll'		    name of the Python 2 dynamic library
-'pythonhome'		    name of the Python 2 home directory
 'pythonthreedll'	    name of the Python 3 dynamic library
-'pythonthreehome'	    name of the Python 3 home directory
-'pyxversion'	  'pyx'	    Python version used for pyx* commands
 'quoteescape'	  'qe'	    escape characters used in a string
 'readonly'	  'ro'	    disallow writing the buffer
 'redrawtime'	  'rdt'     timeout for 'hlsearch' and |:match| highlighting
@@ -934,8 +924,6 @@ Short explanation of each option:		*option-list*
 'termbidi'	  'tbidi'   terminal takes care of bi-directionality
 'termencoding'	  'tenc'    character encoding used by the terminal
 'termguicolors'	  'tgc'     use GUI colors for the terminal
-'termkey'	  'tk'	    key that precedes a Vim command in a terminal
-'termsize'	  'tms'	    size of a terminal window
 'terse'			    shorten some messages
 'textauto'	  'ta'	    obsolete, use 'fileformats'
 'textmode'	  'tx'	    obsolete, use 'fileformat'
@@ -969,7 +957,6 @@ Short explanation of each option:		*option-list*
 'viewdir'	  'vdir'    directory where to store files with :mkview
 'viewoptions'	  'vop'     specifies what to save for :mkview
 'viminfo'	  'vi'	    use .viminfo file upon startup and exiting
-'viminfofile'	  'vif'	    file name used for the viminfo file
 'virtualedit'	  've'	    when to use virtual editing
 'visualbell'	  'vb'	    use visual bell instead of beeping
 'warn'			    warn for shell command when buffer was changed
@@ -989,7 +976,6 @@ Short explanation of each option:		*option-list*
 'winfixwidth'	  'wfw'     keep window width when opening/closing windows
 'winminheight'	  'wmh'     minimum number of lines for any window
 'winminwidth'	  'wmw'     minimal number of columns for any window
-'winptydll'		    name of the winpty dynamic library
 'winwidth'	  'wiw'     minimal number of columns for current window
 'wrap'			    long lines wrap and continue on the next line
 'wrapmargin'	  'wm'	    chars from the right where wrapping starts
@@ -1088,8 +1074,6 @@ Short explanation of each option:		*option-list*
 |c_<Up>|	<Up>/<Down>	   recall older/newer command-line that starts
 				      with current command
 |c_<S-Up>|	<S-Up>/<S-Down>	   recall older/newer command-line from history
-|c_CTRL-G|	CTRL-G		   next match when 'incsearch' is active
-|c_CTRL-T|	CTRL-T		   previous match when 'incsearch' is active
 |:history|	:his[tory]	   show older command-lines

 Context-sensitive completion on the command-line:
@@ -1328,7 +1312,6 @@ Context-sensitive completion on the command-line:

 |:sfind|	:sf[ind] {file}		split window, find {file} in 'path'
 					   and edit it
-|:terminal|	:terminal {cmd}		open a terminal window
 |CTRL-W_]|	CTRL-W ]		split window and jump to tag under
 					   cursor
 |CTRL-W_f|	CTRL-W f		split window and edit file name under
@@ -63,53 +63,53 @@ 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, it's small, powerful and FAST! (Unknown)
-Vim is like a new model Ferrari, and sounds like one too - "VIIIIIIMMM!"
+VIM is like a new model Ferrari, and sounds like one too - "VIIIIIIMMM!"
 (Stephen Riehm, Germany)

-Schon bei Nutzung eines Bruchteils der Vim-Funktionen wird der Benutzer recht
+Schon bei Nutzung eines Bruchteils der VIM-Funktionen wird der Benutzer recht
 schnell die Vorzuege dieses Editors kennen- und schaetzenlernen.
-Translated: Even when only using a fraction of Vim-functions, the user will
+Translated: Even when only using a fraction of VIM-functions, the user will
 quickly get used to and appreciate the advantages of this editor.  (Garry
-Glendown, conclusion of an article on Vim in iX magazine 9/1998)
+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
+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
 Rankin)

-This guide was written using the Windows 9.x distribution of gvim, which is
+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)

-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
+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
 I didn't know before!  I must say the documentation is one the finest I've
 ever seen in a product -- even better than most commercial products.
 (Gautam Mudunuri)

-Vim 4.5 is really a fantastic editor.  It has sooooo many features and more
+VIM 4.5 is really a fantastic editor.  It has sooooo many features and more
 importantly, the defaults are so well thought out that you really don't have
 to change anything!!  Words cannot express my amazement and gratitude to the
-creators of Vim.  Keep it up.  (Vikas, USA)
+creators of VIM.  Keep it up.  (Vikas, USA)

 I wonder how long it will be before people will refer to other Vi editors as
-Vim clones?  (Darren Hiebert)
+VIM clones?  (Darren Hiebert)

 I read about [auto-positioning-in-file-based-on-the-errors-from-make] in one
 of those "Perfect Programmer's Editor" threads and was delighted to discover
-that Vim already supports it.  (Brendan Macmillan, Australia)
+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 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!
 (Matt F. Valentine)

 I think from now on "vi" should be called "Vim Imitation", not the other way
 around.  (Rungun Ramanathan)

-The Law of Vim:
+The Law of VIM:
 For each member b of the possible behaviour space B of program P, there exists
 a finite time t before which at least one user u in the total user space U of
 program P will request b becomes a member of the allowed behaviour space B'
@@ -118,42 +118,42 @@ In other words: Sooner or later everyone wants everything as an option.
 (Negri)

 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
+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 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
+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

-I just wanted to take this opportunity to let you know that Vim 5 ROCKS!
+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)

-I have used most of Vim's fancy features at least once, many frequently, and I
+I have used most of VIM's fancy features at least once, many frequently, and I
 can honestly say that I couldn't live with anything less anymore.  My
 productivity has easily doubled compared to what it was when I used vi.
 (Sitaram Chamarty)

-I luv Vim.  It is incredible.  I'm naming my first-born Vimberly.  (Jose
+I luv VIM.  It is incredible.  I'm naming my first-born Vimberly.  (Jose
 Unpingco, USA)

-Hint:  "Vim" is "vi improved" - much better! (Sven Guckes, Germany)
+Hint:  "VIM" is "vi improved" - much better! (Sven Guckes, Germany)

-I use Vim every day.  I spend more time in Vim than in any other program...
+I use VIM every day.  I spend more time in VIM than in any other program...
 It's the best vi clone there is.  I think it's great.  (Craig Sanders,
 Australia)

-I strongly advise using Vim--its infinite undo/redo saved me much grief.
+I strongly advise using VIM--its infinite undo/redo saved me much grief.
 (Terry Brown)

 Thanks very much for writing what in my opinion is the finest text editor on
@@ -163,98 +163,98 @@ the planet.  If I were to get another cat, I would name it "Vim".
 I typed :set all and the screen FILLED up with options.  A whole screen of
 things to be set and unset.  I saw some of my old friends like wrapmargin,
 modelines and showmode, but the screen was FILLED with new friends!   I love
-them all!   I love Vim!   I'm so happy that I've found this editor!  I feel
+them all!   I love VIM!   I'm so happy that I've found this editor!  I feel
 like how I once felt when I started using vi after a couple of years of using
 ed.  I never thought I'd forsake my beloved ed, but vi ... oh god, vi was
-great.  And now, Vim.  (Peter Jay Salzman, USA)
+great.  And now, VIM.  (Peter Jay Salzman, USA)

 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
+Whenever I reread the VIM documentation I'm overcome with excitement at the
 power of the editor.  (William Edward Webber, Australia)

-Hurrah for Vim!! It is "at your fingertips" like vi, and has the extensions
+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)

 The reason WHY I don't have this amazingly useful macro anymore, is that I
-now use Vim - and this is built in!! (Stephen Riehm, Germany)
+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,
+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
+I discovered VIM after years of struggling with the original vi, and I just
 can't live without it anymore.  (Emmanuel Mogenet, USA)

-Emacs has not a bit of chance to survive so long as Vim is around.  Besides,
+Emacs has not a bit of chance to survive so long as VIM is around.  Besides,
 it also has the most detailed software documentation I have ever seen---much
 better than most commercial software!  (Leiming Qian)

-This version of Vim will just blow people apart when they discover just how
+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
+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
 Colon, USA)

-Vim is a joy to use, it is so well thought and practical that I wonder why
-anybody would use visual development tools.  Vim is powerful and elegant, it
+VIM is a joy to use, it is so well thought and practical that I wonder why
+anybody would use visual development tools.  VIM is powerful and elegant, it
 looks deceptively simple but is almost as complex as a 747 (especially when I
-look at my growing .vimrc), keep up that wonderful job, Vim is a centerpiece
+look at my growing .vimrc), keep up that wonderful job, VIM is a centerpiece
 of the free software world.  (Louis-David Mitterand, USA)

-I cannot believe how great it is to use Vim.  I think the guys at work are
+I cannot believe how great it is to use VIM.  I think the guys at work are
 getting tired of hearing me bragging about it.  Others eyes are lighting up.
 (Rick Croote)

 Emacs takes way too much time to start up and run, it is too big and bulky for
-effective use and the interface is more confusing than it is of any help.  Vim
+effective use and the interface is more confusing than it is of any help.  VIM
 however is short, it is fast, it is powerful, it has a good interface and it
 is all purpose.  (Paal Ditlefsen Ekran)

-From the first time I got Vim3.0, I was very enthusiastic.  It has almost no
+From the first time I got VIM3.0, I was very enthusiastic.  It has almost no
 problems.  The swapfile handling and the backup possibilities are robust, also
 the protection against editing one file twice.  It is very compatible to the
 real VI (and that is a MUST, because my brain is trained over years in using
 it).  (Gert van Antwerpen, Holland)

-Visual mode in Vim is a very powerful thing! (Tony Nugent, Australia)
+Visual mode in VIM is a very powerful thing! (Tony Nugent, Australia)

-I have to say that Vim is =THE= single greatest piece of source code to ever
+I have to say that VIM is =THE= single greatest piece of source code to ever
 come across the net (Jim Battle, USA).

-In fact, if you do want to get a new vi I'd suggest Vim-3.0.  This is, by
+In fact, if you do want to get a new vi I'd suggest VIM-3.0.  This is, by
 far, the best version of vi I've ever seen (Albert W. Schueller).

-I should mention that Vim is a very good editor and can compete with anything
+I should mention that VIM is a very good editor and can compete with anything
 (Ilya Beloozerov).

 To tell the truth sometimes I used elvis, vile, xvi, calvin, etc.  And this is
-the reason that I can state that Vim is the best! (Ferenc Deak, Hungary)
+the reason that I can state that VIM is the best! (Ferenc Deak, Hungary)

-Vim is by far the best editor that I have used in a long time, and I have
+VIM is by far the best editor that I have used in a long time, and I have
 looked at just about every thing that is available for every platform that I
-use.  Vim is the best on all of them.  (Guy L. Oliver)
+use.  VIM is the best on all of them.  (Guy L. Oliver)

-Vim is the greatest editor since the stone chisel.  (Jose Unpingco, USA)
+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'
+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)

 In fact, now if I want to know what a particular setting does in vi, I fire up
-Vim and check out its help!  (Nikhil Patel, USA)
+VIM and check out its help!  (Nikhil Patel, USA)

-As a vi user, Vim has made working with text a far more pleasant task than
+As a vi user, VIM has made working with text a far more pleasant task than
 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
+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
 Eccettuato, Italy)

@@ -1,4 +1,4 @@
-*remote.txt*    For Vim version 8.0.  Last change: 2017 Nov 12
+*remote.txt*    For Vim version 8.0.  Last change: 2015 Mar 01


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -100,7 +100,7 @@ Tell the remote server "BLA" to write all files and exit: >
    vim --servername BLA --remote-send '<C-\><C-N>:wqa<CR>'


-SERVER NAME						*client-server-name*
+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
@@ -150,7 +150,6 @@ the description in |eval.txt| or use CTRL-] on the function name to jump to
 the full explanation.

    synopsis				     explanation ~
-    remote_startserver( name)		     run a server
    remote_expr( server, string, idvar)      send expression
    remote_send( server, string, idvar)      send key sequence
    serverlist()			     get a list of available servers
@@ -182,8 +181,7 @@ name on the 'VimRegistry' property on the root window.

 A non GUI Vim with access to the X11 display (|xterm-clipboard| enabled), can
 also act as a command server if a server name is explicitly given with the
--servername argument, or when Vim was build with the |+autoservername|
-feature.
+--servername argument.

 An empty --servername argument will cause the command server to be disabled.

@@ -1,4 +1,4 @@
-*repeat.txt*    For Vim version 8.0.  Last change: 2018 Mar 04
+*repeat.txt*    For Vim version 8.0.  Last change: 2016 Sep 11


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -46,7 +46,7 @@ of area is used, see |visual-repeat|.
 ==============================================================================
 2. Multiple repeats					*multi-repeat*

-						*:g* *:global* *E148*
+						*:g* *:global* *E147* *E148*
 :[range]g[lobal]/{pattern}/[cmd]
 			Execute the Ex command [cmd] (default ":p") on the
 			lines within [range] where {pattern} matches.
@@ -79,15 +79,8 @@ The default for [range] is the whole buffer (1,$).  Use "CTRL-C" to interrupt
 the command.  If an error message is given for a line, the command for that
 line is aborted and the global command continues with the next marked or
 unmarked line.
-								*E147* 
-When the command is used recursively, it only works on one line.  Giving a
-range is then not allowed. This is useful to find all lines that match a
-pattern and do not match another pattern: >
-	:g/found/v/notfound/{cmd}
-This first finds all lines containing "found", but only executes {cmd} when
-there is no match for "notfound".

-To execute a non-Ex command, you can use the `:normal` command: >
+To repeat a non-Ex command, you can use the ":normal" command: >
 	:g/pat/normal {commands}
 Make sure that {commands} ends with a whole command, otherwise Vim will wait
 for you to type the rest of the command for each match.  The screen will not
@@ -242,10 +235,6 @@ For writing a Vim script, see chapter 41 of the user manual |usr_41.txt|.
 			If the directory pack/*/opt/{name}/after exists it is
 			added at the end of 'runtimepath'.

-			If loading packages from "pack/*/start" was skipped,
-			then this directory is searched first:
-				pack/*/start/{name} ~
-
 			Note that {name} is the directory name, not the name
 			of the .vim file.  All the files matching the pattern
 				pack/*/opt/{name}/plugin/**/*.vim ~
@@ -265,7 +254,6 @@ For writing a Vim script, see chapter 41 of the user manual |usr_41.txt|.
 			loaded during initialization, see |load-plugins|.

 			Also see |pack-add|.
-			{only available when compiled with +eval}

 						*:packl* *:packloadall*
 :packl[oadall][!]	Load all packages in the "start" directory under each
@@ -289,7 +277,6 @@ For writing a Vim script, see chapter 41 of the user manual |usr_41.txt|.
 			An error only causes sourcing the script where it
 			happens to be aborted, further plugins will be loaded.
 			See |packages|.
-			{only available when compiled with +eval}

 :scripte[ncoding] [encoding]		*:scripte* *:scriptencoding* *E167*
 			Specify the character encoding used in the script.
@@ -318,11 +305,6 @@ For writing a Vim script, see chapter 41 of the user manual |usr_41.txt|.
 			Mark) in utf-8 format Vim will recognize it, no need
 			to use ":scriptencoding utf-8" then.

-			If you set the 'encoding' option in your |.vimrc|,
-			`:scriptencoding` must be placed after that. E.g.: >
-				set encoding=utf-8
-				scriptencoding utf-8
-<
 			When compiled without the |+multi_byte| feature this
 			command is ignored.
 			{not in Vi}
@@ -808,19 +790,6 @@ DEFINING BREAKPOINTS
 <		Note that this only works for commands that are executed when
 		sourcing the file, not for a function defined in that file.

-:breaka[dd] expr {expression}
-		Sets a breakpoint, that will break whenever the {expression}
-		evaluates to a different value. Example: >
-			:breakadd expr g:lnum
-
-<		Will break, whenever the global variable lnum changes.
-		Note if you watch a |script-variable| this will break
-		when switching scripts, since the script variable is only
-		valid in the script where it has been defined and if that
-		script is called from several other scripts, this will stop
-		whenever that particular variable will become visible or
-		unaccessible again.
-
 The [lnum] is the line number of the breakpoint.  Vim will stop at or after
 this line.  When omitted line 1 is used.

@@ -1,4 +1,4 @@
-*scroll.txt*    For Vim version 8.0.  Last change: 2016 Nov 10
+*scroll.txt*    For Vim version 8.0.  Last change: 2006 Aug 27


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -108,8 +108,7 @@ z^			Without [count]: Redraw with the line just above the
 3. Scrolling relative to cursor				*scroll-cursor*

 The following commands reposition the edit window (the part of the buffer that
-you see) while keeping the cursor on the same line.  Note that the 'scrolloff'
-option may cause context lines to show above and below the cursor.
+you see) while keeping the cursor on the same line:

 							*z<CR>*
 z<CR>			Redraw, line [count] at top of window (default
@@ -221,7 +220,7 @@ past its buffer's limits.
 However, if a 'scrollbind' window that has a relative offset that is past its
 buffer's limits is given the cursor focus, the other 'scrollbind' windows must
 jump to a location where the current window's relative offset is valid.  This
-behavior can be changed by clearing the "jump" flag from the 'scrollopt'
+behavior can be changed by clearing the 'jump' flag from the 'scrollopt'
 option.

 						*syncbind* *:syncbind* *:sync*
@@ -1,4 +1,4 @@
-*spell.txt*	For Vim version 8.0.  Last change: 2017 Oct 26
+*spell.txt*	For Vim version 8.0.  Last change: 2016 Jan 08


 		  VIM REFERENCE MANUAL	  by Bram Moolenaar
@@ -478,7 +478,7 @@ Vim uses a binary file format for spelling.  This greatly speeds up loading
 the word list and keeps it small.
 						    *.aff* *.dic* *Myspell*
 You can create a Vim spell file from the .aff and .dic files that Myspell
-uses.  Myspell is used by OpenOffice.org and Mozilla. The OpenOffice .oxt
+uses.  Myspell is used by OpenOffice.org and Mozilla. The OpenOffice .oxt 
 files are zip files which contain the .aff and .dic files. You should be able
 to find them here:
 	http://extensions.services.openoffice.org/dictionary
@@ -723,7 +723,7 @@ Additionally the following items are recognized:
    =		Case must match exactly.
    ?		Rare word.
    !		Bad (wrong) word.
-    1 to 9	A region in which the word is valid.  If no regions are
+    digit	A region in which the word is valid.  If no regions are
 		specified the word is valid in all regions.

 Example:
@@ -1614,7 +1614,7 @@ COMPOUNDSYLLABLE  (Hunspell)			*spell-COMPOUNDSYLLABLE*
 KEY		(Hunspell)				*spell-KEY*
 		Define characters that are close together on the keyboard.
 		Used to give better suggestions.  Not supported.
-
+		
 LANG		(Hunspell)				*spell-LANG*
 		This specifies language-specific behavior.  This actually
 		moves part of the language knowledge into the program,
@@ -1,4 +1,4 @@
-*starting.txt*  For Vim version 8.0.  Last change: 2018 Mar 14
+*starting.txt*  For Vim version 8.0.  Last change: 2016 Sep 09


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -58,9 +58,9 @@ filename	One or more file names.  The first one will be the current
 		that is read from stdin.  The commands that would normally be
 		read from stdin will now be read from stderr.  Example: >
 			find . -name "*.c" -print | vim -
-<		The buffer will not be marked as modified, so that it's easy
-		to exit.  Be careful to mark it as modified if you don't want
-		to accidentally lose it.  Example: >
+<		The buffer will be marked modified, because it contains text
+		that needs to be saved.  Except when in readonly mode, then
+		the buffer is not marked modified.  Example: >
 			ls | view -
 <
 		Starting in Ex mode: >
@@ -140,12 +140,11 @@ a slash.  Thus "-R" means recovery and "-/R" readonly.
 --noplugin	Skip loading plugins.  Resets the 'loadplugins' option.
 		{not in Vi}
 		Note that the |-u| argument may also disable loading plugins:
-			argument   load: vimrc files  plugins  defaults.vim ~
-			(nothing)	     yes	yes	  yes
-			-u NONE		     no		no	  no
-			-u DEFAULTS	     no		no	  yes
-			-u NORC		     no		yes	  no
-			--noplugin	     yes	no	  yes
+			argument	load vimrc files	load plugins ~
+			(nothing)		yes		    yes
+			-u NONE			no		    no
+			-u NORC			no		    yes
+			--noplugin		yes		    no

 --startuptime {fname}					*--startuptime*
 		During startup write timing messages to the file {fname}.
@@ -231,7 +230,6 @@ a slash.  Thus "-R" means recovery and "-/R" readonly.
 		the executable "view" has the same effect as the -R argument.
 		The 'updatecount' option will be set to 10000, meaning that
 		the swap file will not be updated automatically very often.
-		See |-M| for disallowing modifications.

 							*-m*
 -m		Modifications not allowed to be written.  The 'write' option
@@ -421,13 +419,7 @@ a slash.  Thus "-R" means recovery and "-/R" readonly.
 							*--not-a-term*
 --not-a-term	Tells Vim that the user knows that the input and/or output is
 		not connected to a terminal.  This will avoid the warning and
-		the two second delay that would happen.
-		Also avoids the "Reading from stdin..." message.
-		{not in Vi}
-
-							*--ttyfail*
--ttyfail	When the stdin or stdout is not a terminal (tty) then exit
-		right away.
+		the two second delay that would happen. {not in Vi}

 							*-d*
 -d		Start in diff mode, like |vimdiff|.
@@ -468,30 +460,21 @@ a slash.  Thus "-R" means recovery and "-/R" readonly.
 --nofork	GUI: Do not fork.  Same as |-f|.
 							*-u* *E282*
 -u {vimrc}	The file {vimrc} is read for initializations.  Most other
-		initializations are skipped; see |initialization|.
-
-		This can be used to start Vim in a special mode, with special
+		initializations are skipped; see |initialization|.  This can
+		be used to start Vim in a special mode, with special
 		mappings and settings.  A shell alias can be used to make
 		this easy to use.  For example: >
 			alias vimc vim -u ~/.c_vimrc !*
 <		Also consider using autocommands; see |autocommand|.
-
 		When {vimrc} is equal to "NONE" (all uppercase), all
 		initializations from files and environment variables are
 		skipped, including reading the |gvimrc| file when the GUI
 		starts.  Loading plugins is also skipped.
-
 		When {vimrc} is equal to "NORC" (all uppercase), this has the
 		same effect as "NONE", but loading plugins is not skipped.
-
-		When {vimrc} is equal to "DEFAULTS" (all uppercase), this has
-		the same effect as "NONE", but the |defaults.vim| script is
-		loaded, which will also set 'nocompatible'.
-
-		Using the "-u" argument with another argument than DEFAULTS
-		has the side effect that the 'compatible' option will be on by
-		default.  This can have unexpected effects.  See
-		|'compatible'|.
+		Using the "-u" argument has the side effect that the
+		'compatible' option will be on by default.  This can have
+		unexpected effects.  See |'compatible'|.
 		{not in Vi}

 							*-U* *E230*
@@ -509,15 +492,6 @@ a slash.  Thus "-R" means recovery and "-/R" readonly.
 		":rv" or ":wv" are used.  See also |viminfo-file|.
 		{not in Vi}

-							*--clean*
--clean		Equal to "-u DEFAULTS -U NONE -i NONE":
-		- initializations from files and environment variables is
-		  skipped
-		- the |defaults.vim| script is loaded, which implies
-		  'nocompatible': use Vim defaults
-		- no |gvimrc| script is loaded
-		- no viminfo file is read or written
-		- the home directory is excluded from 'runtimepath'
 							*-x*
 -x		Use encryption to read/write files.  Will prompt for a key,
 		which is then stored in the 'key' option.  All writes will
@@ -878,9 +852,6 @@ accordingly.  Vim proceeds in this order:
     (*) Using this file or environment variable will cause 'compatible' to be
 	 off by default.  See |compatible-default|.

-     Note: When using the |mzscheme| interface, it is initialized after loading
-     the vimrc file.  Changing 'mzschemedll' later has no effect.
-
 4. Load the plugin scripts.					*load-plugins*
 	This does the same as the command: >
 		:runtime! plugin/**/*.vim
@@ -893,7 +864,6 @@ accordingly.  Vim proceeds in this order:
 	Loading plugins won't be done when:
 	- The 'loadplugins' option was reset in a vimrc file.
 	- The |--noplugin| command line argument is used.
-	- The |--clean| command line argument is used.
 	- The "-u NONE" command line argument is used |-u|.
 	- When Vim was compiled without the |+eval| feature.
 	Note that using "-c 'set noloadplugins'" doesn't work, because the
@@ -1013,13 +983,13 @@ Vi compatible default value ~
 When Vim starts, the 'compatible' option is on.  This will be used when Vim
 starts its initializations.  But as soon as:
 - a user vimrc file is found, or
- a vimrc file in the current directory is found, or
+- a vimrc file in the current directory, or
 - the "VIMINIT" environment variable is set, or
 - the "-N" command line argument is given, or
- the "--clean" command line argument is given, or
+  even when no vimrc file exists.
 - the |defaults.vim| script is loaded, or
- a gvimrc file was found,
-then the option will be set to 'nocompatible'.
+- gvimrc file was found,
+then it will be set to 'nocompatible'.

 Note that this does NOT happen when a system-wide vimrc file was found.

@@ -1045,13 +1015,13 @@ giving the mapping.
 Defaults without a .vimrc file ~
 							*defaults.vim*
 If Vim is started normally and no user vimrc file is found, the
-$VIMRUNTIME/defaults.vim script is loaded.  This will set 'compatible' off,
+$VIMRUTIME/defaults.vim script is loaded.  This will set 'compatible' off,
 switch on syntax highlighting and a few more things.  See the script for
 details.  NOTE: this is done since Vim 8.0, not in Vim 7.4. (it was added in
 patch 7.4.2111 to be exact).

 This should work well for new Vim users.  If you create your own .vimrc, it is
-recommended to add these lines somewhere near the top: >
+recommended to add this line somewhere near the top: >
 	unlet! skip_defaults_vim
 	source $VIMRUNTIME/defaults.vim
 Then Vim works like before you had a .vimrc. Copying $VIMRUNTIME/vimrc_example
@@ -1246,7 +1216,7 @@ There are several ways to exit Vim:
 - Use `:cquit`.  Also when there are changes.

 When using `:cquit` or when there was an error message Vim exits with exit
-code 1.  Errors can be avoided by using `:silent!` or with `:catch`.
+code 1.  Errors can be avoided by using `:silent!`.

 ==============================================================================
 8. Saving settings					*save-settings*
@@ -1422,7 +1392,7 @@ The output of ":mkview" contains these items:
 5. The scroll position and the cursor position in the file.  Doesn't work very
   well when there are closed folds.
 6. The local current directory, if it is different from the global current
-   directory and 'viewoptions' contains "curdir".
+   directory.

 Note that Views and Sessions are not perfect:
 - They don't restore everything.  For example, defined functions, autocommands
@@ -1534,7 +1504,7 @@ Notes for Unix:
  you have worked with.
 - If you want to share the viminfo file with other users (e.g. when you "su"
  to another user), you can make the file writable for the group or everybody.
-  Vim will preserve this when replacing the viminfo file.  Be careful, don't
+  Vim will preserve this when writing new viminfo files.  Be careful, don't
  allow just anybody to read and write your viminfo file!
 - Vim will not overwrite a viminfo file that is not writable by the current
  "real" user.  This helps for when you did "su" to become root, but your
@@ -1,4 +1,4 @@
-*syntax.txt*	For Vim version 8.0.  Last change: 2018 Jan 31
+*syntax.txt*	For Vim version 8.0.  Last change: 2016 Sep 13


 		  VIM REFERENCE MANUAL	  by Bram Moolenaar
@@ -61,12 +61,10 @@ fine.  If it doesn't, try setting the VIM environment variable to the
 directory where the Vim stuff is located.  For example, if your syntax files
 are in the "/usr/vim/vim50/syntax" directory, set $VIMRUNTIME to
 "/usr/vim/vim50".  You must do this in the shell, before starting Vim.
-This command also sources the |menu.vim| script when the GUI is running or
-will start soon.  See |'go-M'| about avoiding that.

 							*:syn-on* *:syntax-on*
-The `:syntax enable` command will keep your current color settings.  This
-allows using `:highlight` commands to set your preferred colors before or
+The ":syntax enable" command will keep your current color settings.  This
+allows using ":highlight" commands to set your preferred colors before or
 after using this command.  If you want Vim to overrule your settings with the
 defaults, use: >
 	:syntax on
@@ -812,9 +810,12 @@ See |mysyntaxfile-add| for installing script languages permanently.

 APACHE						*apache.vim* *ft-apache-syntax*

-The apache syntax file provides syntax highlighting for Apache HTTP server
-version 2.2.3.
+The apache syntax file provides syntax highlighting depending on Apache HTTP
+server version, by default for 1.3.x.  Set "apache_version" to Apache version
+(as a string) to get highlighting for another version.	Example: >

+	:let apache_version = "2.0"
+<

 		*asm.vim* *asmh8300.vim* *nasm.vim* *masm.vim* *asm68k*
 ASSEMBLY	*ft-asm-syntax* *ft-asmh8300-syntax* *ft-nasm-syntax*
@@ -1475,7 +1476,7 @@ algorithm should work in the vast majority of cases.  In some cases, such as a
 file that begins with 500 or more full-line comments, the script may
 incorrectly decide that the fortran code is in fixed form.  If that happens,
 just add a non-comment statement beginning anywhere in the first five columns
-of the first twenty-five lines, save (:w) and then reload (:e!) the file.
+of the first twenty five lines, save (:w) and then reload (:e!) the file.

 Tabs in fortran files ~
 Tabs are not recognized by the Fortran standards.  Tabs are not a good idea in
@@ -2137,16 +2138,6 @@ set "msql_minlines" to the value you desire.  Example: >
 	:let msql_minlines = 200


-N1QL						*n1ql.vim* *ft-n1ql-syntax*
-
-N1QL is a SQL-like declarative language for manipulating JSON documents in
-Couchbase Server databases.
-
-Vim syntax highlights N1QL statements, keywords, operators, types, comments,
-and special values.  Vim ignores syntactical elements specific to SQL or its
-many dialects, like COLUMN or CHAR, that don't exist in N1QL.
-
-
 NCF						*ncf.vim* *ft-ncf-syntax*

 There is one option for NCF syntax highlighting.
@@ -2655,9 +2646,9 @@ later, and part earlier) adds.

 RESTRUCTURED TEXT			*rst.vim* *ft-rst-syntax*

-You may set what syntax definitions should be used for code blocks via >
+You may set what syntax definitions should be used for code blocks via
 	let rst_syntax_code_list = ['vim', 'lisp', ...]
-<
+

 REXX						*rexx.vim* *ft-rexx-syntax*

@@ -2779,10 +2770,13 @@ Ruby syntax will perform spellchecking of strings if you define

 SCHEME						*scheme.vim* *ft-scheme-syntax*

-By default only R7RS keywords are highlighted and properly indented.
+By default only R5RS keywords are highlighted and properly indented.

-scheme.vim also supports extensions of the CHICKEN Scheme->C compiler.
-Define b:is_chicken or g:is_chicken, if you need them.
+MzScheme-specific stuff will be used if b:is_mzscheme or g:is_mzscheme
+variables are defined.
+
+Also scheme.vim supports keywords of the Chicken Scheme->C compiler.  Define
+b:is_chicken or g:is_chicken, if you need them.


 SDL						*sdl.vim* *ft-sdl-syntax*
@@ -2869,11 +2863,9 @@ vimrc file: >
 (Adapted from the html.vim help text by Claudio Fleiner <claudio@fleiner.com>)


-		*ft-posix-synax* *ft-dash-syntax*
-SH		*sh.vim*  *ft-sh-syntax*  *ft-bash-syntax*  *ft-ksh-syntax*
+SH		*sh.vim* *ft-sh-syntax* *ft-bash-syntax* *ft-ksh-syntax*

-This covers syntax highlighting for the older Unix (Bourne) sh, and newer
-shells such as bash, dash, posix, and the Korn shells.
+This covers the "normal" Unix (Bourne) sh, bash and the Korn shell.

 Vim attempts to determine which shell type is in use by specifying that
 various filenames are of specific types: >
@@ -2882,31 +2874,28 @@ various filenames are of specific types: >
    bash: .bashrc* bashrc bash.bashrc .bash_profile* *.bash
 <
 If none of these cases pertain, then the first line of the file is examined
-(ex. looking for /bin/sh  /bin/ksh  /bin/bash).  If the first line specifies a
-shelltype, then that shelltype is used.  However some files (ex. .profile) are
-known to be shell files but the type is not apparent.  Furthermore, on many
-systems sh is symbolically linked to "bash" (Linux, Windows+cygwin) or "ksh"
-(Posix).
+(ex. /bin/sh  /bin/ksh	/bin/bash).  If the first line specifies a shelltype,
+then that shelltype is used.  However some files (ex. .profile) are known to
+be shell files but the type is not apparent.  Furthermore, on many systems
+sh is symbolically linked to "bash" (Linux, Windows+cygwin) or "ksh" (Posix).

-One may specify a global default by instantiating one of the following
+One may specify a global default by instantiating one of the following three
 variables in your <.vimrc>:

-   ksh: >
+    ksh: >
 	let g:is_kornshell = 1
-<   posix:  (using this is the nearly the same as setting g:is_kornshell to 1) >
+<   posix: (using this is the same as setting is_kornshell to 1) >
 	let g:is_posix     = 1
 <   bash: >
 	let g:is_bash	   = 1
 <   sh: (default) Bourne shell >
 	let g:is_sh	   = 1

-<   (dash users should use posix)
-
 If there's no "#! ..." line, and the user hasn't availed himself/herself of a
 default sh.vim syntax setting as just shown, then syntax/sh.vim will assume
 the Bourne shell syntax.  No need to quote RFCs or market penetration
 statistics in error reports, please -- just select the default version of the
-sh your system uses and install the associated "let..." in your <.vimrc>.
+sh your system uses in your <.vimrc>.

 The syntax/sh.vim file provides several levels of syntax-based folding: >

@@ -2915,7 +2904,7 @@ The syntax/sh.vim file provides several levels of syntax-based folding: >
 	let g:sh_fold_enabled= 2     (enable heredoc folding)
 	let g:sh_fold_enabled= 4     (enable if/do/for folding)
 >
-then various syntax items (ie. HereDocuments and function bodies) become
+then various syntax items (HereDocuments and function bodies) become
 syntax-foldable (see |:syn-fold|).  You also may add these together
 to get multiple types of folding: >

@@ -2939,14 +2928,14 @@ reduce this, the "sh_maxlines" internal variable can be set.  Example: >
 The default is to use the twice sh_minlines.  Set it to a smaller number to
 speed up displaying.  The disadvantage is that highlight errors may appear.

-syntax/sh.vim tries to flag certain problems as errors; usually things like
-extra ']'s, 'done's, 'fi's, etc.  If you find the error handling problematic
-for your purposes, you may suppress such error highlighting by putting
-the following line in your .vimrc: >
-
-	let g:sh_no_error= 1
+						*g:sh_isk* *g:sh_noisk*
+The shell languages appear to let "." be part of words, commands, etc;
+consequently it should be in the isk for sh.vim.  As of v116 of syntax/sh.vim,
+syntax/sh.vim will append the "." to |'iskeyword'| by default; you may control
+this behavior with: >
+	let g:sh_isk  = '..whatever characters you want as part of iskeyword'
+	let g:sh_noisk= 1  " otherwise, if this exists, the isk will NOT chg
 <
-
 						*sh-embed*  *sh-awk*
 Sh: EMBEDDING LANGUAGES~

@@ -3248,11 +3237,11 @@ syntax highlighting script handles this with the following logic:
 	* If g:tex_stylish exists and is 1
 		then the file will be treated as a "sty" file, so the "_"
 		will be allowed as part of keywords
-		(regardless of g:tex_isk)
+		(irregardless of g:tex_isk)
 	* Else if the file's suffix is sty, cls, clo, dtx, or ltx,
 		then the file will be treated as a "sty" file, so the "_"
 		will be allowed as part of keywords
-		(regardless of g:tex_isk)
+		(irregardless of g:tex_isk)

 	* If g:tex_isk exists, then it will be used for the local 'iskeyword'
 	* Else the local 'iskeyword' will be set to 48-57,a-z,A-Z,192-255
@@ -3333,8 +3322,8 @@ Some folding is now supported with syntax/vim.vim: >
   g:vimsyn_folding =~ 't' : fold tcl      script
 <
 							*g:vimsyn_noerror*
-Not all error highlighting that syntax/vim.vim does may be correct; Vim script
-is a difficult language to highlight correctly.  A way to suppress error
+Not all error highlighting that syntax/vim.vim does may be correct; VimL is a
+difficult language to highlight correctly.  A way to suppress error
 highlighting is to put the following line in your |vimrc|: >

 	let g:vimsyn_noerror = 1
@@ -3492,8 +3481,6 @@ DEFINING CASE						*:syn-case* *E390*
 	"ignore".  Note that any items before this are not affected, and all
 	items until the next ":syntax case" command are affected.

-:sy[ntax] case
-	Show either "syntax case match" or "syntax case ignore" (translated).

 SPELL CHECKING						*:syn-spell*

@@ -3511,11 +3498,6 @@ SPELL CHECKING						*:syn-spell*

 	To activate spell checking the 'spell' option must be set.

-:sy[ntax] spell
-	Show either "syntax spell toplevel", "syntax spell notoplevel" or
-	"syntax spell default" (translated).
-
-
 SYNTAX ISKEYWORD SETTING				*:syn-iskeyword*

 :sy[ntax] iskeyword [clear | {option}]
@@ -3598,11 +3580,7 @@ DEFINING KEYWORDS					*:syn-keyword*

 DEFINING MATCHES					*:syn-match*

-:sy[ntax] match {group-name} [{options}]
-		[excludenl]
-		[keepend]
-		{pattern}
-		[{options}]
+:sy[ntax] match {group-name} [{options}] [excludenl] {pattern} [{options}]

 	This defines one match.

@@ -3611,9 +3589,6 @@ DEFINING MATCHES					*:syn-match*
 	[excludenl]		Don't make a pattern with the end-of-line "$"
 				extend a containing match or region.  Must be
 				given before the pattern. |:syn-excludenl|
-	keepend			Don't allow contained matches to go past a
-				match with the end pattern.  See
-				|:syn-keepend|.
 	{pattern}		The search pattern that defines the match.
 				See |:syn-pattern| below.
 				Note that the pattern may match more than one
@@ -4109,9 +4084,6 @@ IMPLICIT CONCEAL					*:syn-conceal-implicit*
 	off" returns to the normal state where the "conceal" flag must be
 	given explicitly.

-:sy[ntax] conceal
-	Show either "syntax conceal on" or "syntax conceal off" (translated).
-
 ==============================================================================
 7. Syntax patterns				*:syn-pattern* *E401* *E402*

@@ -4620,14 +4592,7 @@ in their own color.

 			Doesn't work recursively, thus you can't use
 			":colorscheme" in a color scheme script.
-
-			To customize a colorscheme use another name, e.g.
-			"~/.vim/colors/mine.vim", and use `:runtime` to load
-			the original colorscheme: >
-				runtime colors/evening.vim
-				hi Statement ctermfg=Blue guifg=Blue
-
-<			After the color scheme has been loaded the
+			After the color scheme has been loaded the
 			|ColorScheme| autocommand event is triggered.
 			For info about writing a colorscheme file: >
 				:edit $VIMRUNTIME/colors/README.txt
@@ -4695,26 +4660,23 @@ the same syntax file on all terminals, and use the optimal highlighting.

 					*bold* *underline* *undercurl*
 					*inverse* *italic* *standout*
-					*nocombine* *strikethrough*
 term={attr-list}			*attr-list* *highlight-term* *E418*
 	attr-list is a comma separated list (without spaces) of the
 	following items (in any order):
 		bold
 		underline
 		undercurl	not always available
-		strikethrough	not always available
 		reverse
 		inverse		same as reverse
 		italic
 		standout
-		nocombine	override attributes instead of combining them
 		NONE		no attributes used (used to reset it)

 	Note that "bold" can be used here and by using a bold font.  They
 	have the same effect.
 	"undercurl" is a curly underline.  When "undercurl" is not possible
-	then "underline" is used.  In general "undercurl" and "strikethrough"
-	is only available in the GUI.  The color is set with |highlight-guisp|.
+	then "underline" is used.  In general "undercurl" is only available in
+	the GUI.  The color is set with |highlight-guisp|.

 start={term-list}				*highlight-start* *E422*
 stop={term-list}				*term-list* *highlight-stop*
@@ -4821,11 +4783,10 @@ ctermbg={color-nr}				*highlight-ctermbg*
 	Example: >
 		:highlight Normal ctermfg=grey ctermbg=darkblue
 <	When setting the "ctermbg" color for the Normal group, the
-	'background' option will be adjusted automatically, under the
-	condition that the color is recognized and 'background' was not set
-	explicitly.  This causes the highlight groups that depend on
-	'background' to change!  This means you should set the colors for
-	Normal first, before setting other colors.
+	'background' option will be adjusted automatically.  This causes the
+	highlight groups that depend on 'background' to change!  This means
+	you should set the colors for Normal first, before setting other
+	colors.
 	When a colorscheme is being used, changing 'background' causes it to
 	be reloaded, which may reset all colors (including Normal).  First
 	delete the "g:colors_name" variable when you don't want this.
@@ -4879,8 +4840,7 @@ guifg={color-name}					*highlight-guifg*
 guibg={color-name}					*highlight-guibg*
 guisp={color-name}					*highlight-guisp*
 	These give the foreground (guifg), background (guibg) and special
-	(guisp) color to use in the GUI.  "guisp" is used for undercurl and
-	strikethrough.
+	(guisp) color to use in the GUI.  "guisp" is used for undercurl.
 	There are a few special names:
 		NONE		no color (transparent)
 		bg		use normal background color
@@ -4992,11 +4952,10 @@ PmenuSbar	Popup menu: scrollbar.
 PmenuThumb	Popup menu: Thumb of the scrollbar.
 							*hl-Question*
 Question	|hit-enter| prompt and yes/no questions
-							*hl-QuickFixLine*
-QuickFixLine	Current |quickfix| item in the quickfix window.
 							*hl-Search*
 Search		Last search pattern highlighting (see 'hlsearch').
-		Also used for similar items that need to stand out.
+		Also used for highlighting the current line in the quickfix
+		window and similar items that need to stand out.
 							*hl-SpecialKey*
 SpecialKey	Meta and special keys listed with ":map", also for text used
 		to show unprintable characters in the text, 'listchars'.
@@ -5022,19 +4981,12 @@ StatusLine	status line of current window
 StatusLineNC	status lines of not-current windows
 		Note: if this is equal to "StatusLine" Vim will use "^^^" in
 		the status line of the current window.
-							*hl-StatusLineTerm*
-StatusLineTerm	status line of current window, if it is a |terminal| window.
-							*hl-StatusLineTermNC*
-StatusLineTermNC   status lines of not-current windows that is a |terminal|
-		window.
 							*hl-TabLine*
 TabLine		tab pages line, not active tab page label
 							*hl-TabLineFill*
 TabLineFill	tab pages line, where there are no labels
 							*hl-TabLineSel*
 TabLineSel	tab pages line, active tab page label
-							*hl-Terminal*
-Terminal	|terminal| window (see |terminal-size-color|)
 							*hl-Title*
 Title		titles for output from ":set all", ":autocmd" etc.
 							*hl-Visual*
@@ -1,4 +1,4 @@
-*tabpage.txt*   For Vim version 8.0.  Last change: 2016 Oct 20
+*tabpage.txt*   For Vim version 8.0.  Last change: 2016 Sep 09


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -58,8 +58,6 @@ clicking right of the labels.
 In the GUI tab pages line you can use the right mouse button to open menu.
 |tabline-menu|.

-For the related autocommands see |tabnew-autocmd|.
-
 :[count]tabe[dit]				*:tabe* *:tabedit* *:tabnew*
 :[count]tabnew
 		Open a new tab page with an empty window, after the current
@@ -139,10 +137,6 @@ something else.
 		    :+tabclose	    " close the next tab page
 		    :1tabclose	    " close the first tab page
 		    :$tabclose	    " close the last tab page
-		    :tabclose -2    " close the two previous tab page
-		    :tabclose +	    " close the next tab page
-		    :tabclose 3	    " close the third tab page
-		    :tabclose $	    " close the last tab page
 <
 							*:tabo* *:tabonly*
 :tabo[nly][!]	Close all other tab pages.
@@ -157,20 +151,13 @@ something else.
 				    " one

 :{count}tabo[nly][!]
-:tabo[nly][!] {count}
-		Close all tab pages except {count} one. >
+		Close all tab pages except the {count}th one. >
 		    :.tabonly	    " as above
 		    :-tabonly	    " close all tab pages except the previous
 				    " one
 		    :+tabonly	    " close all tab pages except the next one
 		    :1tabonly	    " close all tab pages except the first one
 		    :$tabonly	    " close all tab pages except the last one
-		    :tabonly -	    " close all tab pages except the previous
-				    " one
-		    :tabonly +2     " close all tab pages except the two next
-				    " one
-		    :tabonly 1	    " close all tab pages except the first one
-		    :tabonly $	    " close all tab pages except the last one


 SWITCHING TO ANOTHER TAB PAGE:
@@ -185,20 +172,7 @@ gt					*i_CTRL-<PageDown>* *i_<C-PageDown>*
 		Go to the next tab page.  Wraps around from the last to the
 		first one.

-:{count}tabn[ext]
 :tabn[ext] {count}
-		Go to tab page {count}.  The first tab page has number one. >
-		    :-tabnext	" go to the previous tab page
-		    :+tabnext	" go to the next tab page
-		    :+2tabnext	" go to the two next tab page
-		    :1tabnext	" go to the first tab page
-		    :$tabnext	" go to the last tab page
-		    :tabnext $	" as above
-		    :tabnext -	" go to the previous tab page
-		    :tabnext -1	" as above
-		    :tabnext +	" go to the next tab page
-		    :tabnext +1	" as above
-
 {count}<C-PageDown>
 {count}gt	Go to tab page {count}.  The first tab page has number one.

@@ -313,7 +287,6 @@ Variables local to a tab page start with "t:". |tabpage-variable|

 Currently there is only one option local to a tab page: 'cmdheight'.

-						*tabnew-autocmd*
 The TabLeave and TabEnter autocommand events can be used to do something when
 switching from one tab page to another.  The exact order depends on what you
 are doing.  When creating a new tab page this works as if you create a new
@@ -1,4 +1,4 @@
-*tagsrch.txt*   For Vim version 8.0.  Last change: 2017 Oct 20
+*tagsrch.txt*   For Vim version 8.0.  Last change: 2016 Sep 20


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -195,7 +195,6 @@ the same entry.
 			information in the tags file(s).
 			When [ident] is not given, the last tag name from the
 			tag stack is used.
-			See |tag-!| for [!].
 			With a '>' in the first column is indicated which is
 			the current position in the list (if there is one).
 			[ident] can be a regexp pattern, see |tag-regexp|.
@@ -1,4 +1,4 @@
-*term.txt*      For Vim version 8.0.  Last change: 2017 Oct 14
+*term.txt*      For Vim version 8.0.  Last change: 2016 Sep 02


 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -89,28 +89,6 @@ an external command (e.g., "!!"), the terminal will be put into Normal mode
 for a moment.  This means that you can stop the output to the screen by
 hitting a printing key.  Output resumes when you hit <BS>.

-						*xterm-bracketed-paste*
-When the 't_BE' option is set then 't_BE' will be sent to the
-terminal when entering "raw" mode and 't_BD' when leaving "raw" mode.  The
-terminal is then expected to put 't_PS' before pasted text and 't_PE' after
-pasted text.  This way Vim can separate text that is pasted from characters
-that are typed.  The pasted text is handled like when the middle mouse button
-is used, it is inserted literally and not interpreted as commands.
-
-When the cursor is in the first column, the pasted text will be inserted
-before it.  Otherwise the pasted text is appended after the cursor position.
-This means one cannot paste after the first column.  Unfortunately Vim does
-not have a way to tell where the mouse pointer was.
-
-Note that in some situations Vim will not recognize the bracketed paste and
-you will get the raw text.  In other situations Vim will only get the first
-pasted character and drop the rest, e.g. when using the "r" command.  If you
-have a problem with this, disable bracketed paste by putting this in your
-.vimrc: >
-	set t_BE=
-If this is done while Vim is running the 't_BD' will be sent to the terminal
-to disable bracketed paste.
-
 							*cs7-problem*
 Note: If the terminal settings are changed after running Vim, you might have
 an illegal combination of settings.  This has been reported on Solaris 2.5
@@ -252,7 +230,7 @@ But any non-empty string means that the flag is set.  An empty string means
 that the flag is not set.  't_CS' works like this too, but it isn't a termcap
 flag.

-OUTPUT CODES						*terminal-output-codes*
+OUTPUT CODES
 	option	meaning	~

 	t_AB	set background color (ANSI)			*t_AB* *'t_AB'*
@@ -295,11 +273,13 @@ OUTPUT CODES						*terminal-output-codes*
 	t_ts	set window title start (to status line)		*t_ts* *'t_ts'*
 	t_ue	underline end					*t_ue* *'t_ue'*
 	t_us	underline mode					*t_us* *'t_us'*
+	t_Ce	undercurl end					*t_Ce* *'t_Ce'*
+	t_Cs	undercurl mode					*t_Cs* *'t_Cs'*
 	t_ut	clearing uses the current background color	*t_ut* *'t_ut'*
 	t_vb	visual bell					*t_vb* *'t_vb'*
 	t_ve	cursor visible					*t_ve* *'t_ve'*
 	t_vi	cursor invisible				*t_vi* *'t_vi'*
-	t_vs	cursor very visible (blink)			*t_vs* *'t_vs'*
+	t_vs	cursor very visible				*t_vs* *'t_vs'*
 								*t_xs* *'t_xs'*
 	t_xs	if non-empty, standout not erased by overwriting (hpterm)
 								*t_xn* *'t_xn'*
@@ -309,16 +289,10 @@ OUTPUT CODES						*terminal-output-codes*
 	t_ZR	italics end					*t_ZR* *'t_ZR'*

 Added by Vim (there are no standard codes for these):
-	t_Ce	undercurl end					*t_Ce* *'t_Ce'*
-	t_Cs	undercurl mode					*t_Cs* *'t_Cs'*
-	t_Te	strikethrough end				*t_Te* *'t_Te'*
-	t_Ts	strikethrough mode				*t_Ts* *'t_Ts'*
 	t_IS	set icon text start				*t_IS* *'t_IS'*
 	t_IE	set icon text end				*t_IE* *'t_IE'*
 	t_WP	set window position (Y, X) in pixels		*t_WP* *'t_WP'*
-	t_GP	get window position (Y, X) in pixels		*t_GP* *'t_GP'*
-	t_WS	set window size (height, width in cells)	*t_WS* *'t_WS'*
-	t_VS	cursor normally visible (no blink)		*t_VS* *'t_VS'*
+	t_WS	set window size (height, width) in characters	*t_WS* *'t_WS'*
 	t_SI	start insert mode (bar cursor shape)		*t_SI* *'t_SI'*
 	t_SR	start replace mode (underline cursor shape)	*t_SR* *'t_SR'*
 	t_EI	end insert or replace mode (block cursor shape)	*t_EI* *'t_EI'*
@@ -327,41 +301,13 @@ Added by Vim (there are no standard codes for these):
 		|xterm-8bit| |v:termresponse| |'ttymouse'| |xterm-codes|
 	t_u7	request cursor position (for xterm)		*t_u7* *'t_u7'*
 		see |'ambiwidth'|
-	t_RF	request terminal foreground color		*t_RF* *'t_RF'*
 	t_RB	request terminal background color		*t_RB* *'t_RB'*
 	t_8f	set foreground color (R, G, B)			*t_8f* *'t_8f'*
 		|xterm-true-color|
 	t_8b	set background color (R, G, B)			*t_8b* *'t_8b'*
 		|xterm-true-color|
-	t_BE	enable bracketed paste mode			*t_BE* *'t_BE'*
-		|xterm-bracketed-paste|
-	t_BD	disable bracketed paste mode			*t_BD* *'t_BD'*
-		|xterm-bracketed-paste|
-	t_SC	set cursor color start				*t_SC* *'t_SC'*
-	t_EC	set cursor color end				*t_EC* *'t_EC'*
-	t_SH	set cursor shape				*t_SH* *'t_SH'*
-	t_RC	request terminal cursor blinking		*t_RC* *'t_RC'*
-	t_RS	request terminal cursor style			*t_RS* *'t_RS'*

-Some codes have a start, middle and end part.  The start and end are defined
-by the termcap option, the middle part is text.
-	set title text:     t_ts {title text} t_fs
-	set icon text:      t_IS {icon text} t_IE
-	set cursor color:   t_SC  {color name}  t_EC
-
-t_SH must take one argument:
-	0, 1 or none  	blinking block cursor
-	2	      	block cursor
-	3		blinking underline cursor
-	4		underline cursor
-	5		blinking vertical bar cursor
-	6		vertical bar cursor
-
-t_RS is sent only if the response to t_RV has been received.  It is not used
-on Mac OS when Terminal.app could be recognized from the termresponse.
-
-
-KEY CODES						*terminal-key-codes*
+KEY CODES
 Note: Use the <> form if possible

 	option	name		meaning	~
@@ -452,9 +398,6 @@ Note: Use the <> form if possible
 	t_KK	<k8>		keypad 8		 *<k8>*	*t_KK* *'t_KK'*
 	t_KL	<k9>		keypad 9		 *<k9>*	*t_KL* *'t_KL'*
 		<Mouse>		leader of mouse code		*<Mouse>*
-								*t_PS* *'t_PS'*
-	t_PS	start of bracketed paste |xterm-bracketed-paste|
-	t_PE	end of bracketed paste |xterm-bracketed-paste|  *t_PE* *'t_PE'*

 Note about t_so and t_mr: When the termcap entry "so" is not present the
 entry for "mr" is used.  And vice versa.  The same is done for "se" and "me".
@@ -1,713 +0,0 @@
-*terminal.txt*	For Vim version 8.0.  Last change: 2018 Mar 16
-
-
-		  VIM REFERENCE MANUAL	  by Bram Moolenaar
-
-
-Terminal window support					*terminal*
-
-
-The terminal feature is optional, use this to check if your Vim has it: >
-	echo has('terminal')
-If the result is "1" you have it.
-
-
-1. Basic use			|terminal-use|
-      Typing				|terminal-typing|
-      Size and color			|terminal-size-color|
-      Syntax				|:terminal|
-      Resizing				|terminal-resizing|
-      Terminal Modes			|Terminal-mode|
-      Cursor style			|terminal-cursor-style|
-      Special keys			|terminal-special-keys|
-      Session				|terminal-session|
-      Unix				|terminal-unix|
-      MS-Windows			|terminal-ms-windows|
-2. Remote testing		|terminal-testing|
-3. Diffing screen dumps		|terminal-diff|
-      Writing a screen dump test for Vim  |terminal-dumptest|
-      Creating a screen dump		  |terminal-screendump|
-      Comparing screen dumps		  |terminal-diffscreendump|
-4. Debugging			|terminal-debug|
-      Starting				|termdebug-starting|
-      Example session			|termdebug-example|
-      Stepping through code		|termdebug-stepping|
-      Inspecting variables		|termdebug-variables|
-      Other commands			|termdebug-commands|
-      Communication			|termdebug-communication|
-      Customizing			|termdebug-customizing|
-
-{Vi does not have any of these commands}
-{only available when compiled with the |+terminal| feature}
-The terminal feature requires the |+multi_byte|, |+job| and |+channel| features.
-
-==============================================================================
-1. Basic use						*terminal-use*
-
-This feature is for running a terminal emulator in a Vim window.  A job can be
-started connected to the terminal emulator. For example, to run a shell: >
-     :term bash
-
-Or to run build command: >
-     :term make myprogram
-
-The job runs asynchronously from Vim, the window will be updated to show
-output from the job, also while editing in another window.
-
-
-Typing ~
-							*terminal-typing*
-When the keyboard focus is in the terminal window, typed keys will be sent to
-the job.  This uses a pty when possible.  You can click outside of the
-terminal window to move keyboard focus elsewhere.
-
-CTRL-W can be used to navigate between windows and other CTRL-W commands, e.g.:
-	CTRL-W CTRL-W	move focus to the next window
-	CTRL-W :	enter an Ex command
-See |CTRL-W| for more commands.
-
-Special in the terminal window:			*CTRL-W_.*  *CTRL-W_N* 
-	CTRL-W .	send a CTRL-W to the job in the terminal
-	CTRL-W N	go to Terminal-Normal mode, see |Terminal-mode|
-	CTRL-\ CTRL-N   go to Terminal-Normal mode, see |Terminal-mode|
-	CTRL-W " {reg}  paste register {reg}		*CTRL-W_quote*
-			Also works with the = register to insert the result of
-			evaluating an expression.
-	CTRL-W CTRL-C	ends the job, see below |t_CTRL-W_CTRL-C|
-
-See option 'termkey' for specifying another key instead of CTRL-W that
-will work like CTRL-W.  However, typing 'termkey' twice sends 'termkey' to
-the job.  For example:
-	'termkey' CTRL-W    move focus to the next window
-	'termkey' :	    enter an Ex command
-	'termkey' 'termkey' send 'termkey' to the job in the terminal
-	'termkey' .	    send a CTRL-W to the job in the terminal
-	'termkey' N	    go to terminal Normal mode, see below
-	'termkey' CTRL-N    same as CTRL-W N
-	'termkey' CTRL-C    same as |t_CTRL-W_CTRL-C|
-							*t_CTRL-\_CTRL-N*
-The special key combination CTRL-\ CTRL-N can be used to switch to Normal
-mode, just like this works in any other mode.
-							*t_CTRL-W_CTRL-C*
-CTRL-W CTRL-C can be typed to forcefully end the job.  On MS-Windows a
-CTRL-BREAK will also kill the job.
-
-If you type CTRL-C the effect depends on what the pty has been configured to
-do.  For simple commands this causes a SIGINT to be sent to the job, which
-would end it.  Other commands may ignore the SIGINT or handle the CTRL-C
-themselves (like Vim does).
-
-To change the keys you type use terminal mode mappings, see |:tmap|.
-These are defined like any mapping, but apply only when typing keys that are
-sent to the job running in the terminal.  For example, to make F1 switch
-to Terminal-Normal mode: >
-   tnoremap <F1> <C-W>N
-You can use Esc, but you need to make sure it won't cause other keys to
-break: >
-   tnoremap <Esc> <C-W>N
-   set notimeout ttimeout timeoutlen=100
-
-<							*options-in-terminal*
-After opening the terminal window and setting 'buftype' to "terminal" the
-BufWinEnter autocommand event is triggered.  This makes it possible to set
-options specifically for the window and buffer.  Example: >
-   au BufWinEnter * if &buftype == 'terminal' | setlocal bufhidden=hide | endif
-
-Mouse events (click and drag) are passed to the terminal.  Mouse move events
-are only passed when Vim itself is receiving them.  For a terminal that is
-when 'balloonevalterm' is enabled.
-
-
-Size and color ~
-							*terminal-size-color*
-See option 'termsize' for controlling the size of the terminal window.
-(TODO: scrolling when the terminal is larger than the window)
-
-The job running in the terminal can change the colors.  The default foreground
-and background colors are taken from Vim, the Normal highlight group.
-
-For a color terminal the 'background' option is used to decide whether the
-terminal window will start with a white or black background.
-
-To use a different color the Terminal highlight group can be used, for
-example: >
-    hi Terminal ctermbg=lightgrey ctermfg=blue guibg=lightgrey guifg=blue
-
-
-Syntax ~
-
-:[range]ter[minal] [options] [command]			*:ter* *:terminal*
-			Open a new terminal window.
-
-			If [command] is provided run it as a job and connect
-			the input and output to the terminal.
-			If [command] is not given the 'shell' option is used.
-			if [command] is NONE no job is started, the pty of the
-			terminal can be used by a command like gdb.
-
-			If [command] is missing the default behavior is to
-			close the terminal when the shell exits.  This can be
-			changed with the ++noclose argument.
-			If [command] is present the default behavior is to
-			keep the terminal open in Terminal-Normal mode.  This
-			can be changed with the ++close argument.
-
-			A new buffer will be created, using [command] or
-			'shell' as the name, prefixed with a "!".  If a buffer
-			by this name already exists a number is added in
-			parentheses.  E.g. if "gdb" exists the second terminal
-			buffer will use "!gdb (1)".
-
-			If [range] is given the specified lines are used as
-			input for the job.  It will not be possible to type
-			keys in the terminal window.  For MS-Windows see the
-			++eof argument below.
-
-						*term++close* *term++open*
-			Supported [options] are:
-			++close		The terminal window will close
-					automatically when the job terminates.
-			++noclose	The terminal window will NOT close
-					automatically when the job terminates.
-			++open		When the job terminates and no window
-					shows it, a window will be opened.
-					Note that this can be interruptive.
-				The last of ++close, ++noclose and ++open
-				matters and rules out earlier arguments.
-
-			++curwin	Open the terminal in the current
-					window, do not split the current
-					window.  Fails if the current buffer
-					cannot be |abandon|ed.
-			++hidden	Open the terminal in a hidden buffer,
-					no window will be used.
-			++norestore	Do not include this terminal window
-					in a session file.
-			++kill={how}	When trying to close the terminal
-					window kill the job with {how}.  See
-					|term_setkill()| for the values.
-			++rows={height} Use {height} for the terminal window
-					height.  If the terminal uses the full
-					Vim height (no window above or below
-					th terminal window) the command line
-					height will be reduced as needed.
-			++cols={width}  Use {width} for the terminal window
-					width. If the terminal uses the full
-					Vim width (no window left or right of
-					the terminal window) this value is
-					ignored.
-			++eof={text}	when using [range]: text to send after
-					the last line was written. Cannot
-					contain white space.  A CR is
-					appended.  For MS-Windows the default
-					is to send CTRL-D.
-					E.g. for a shell use "++eof=exit" and
-					for Python "++eof=exit()".  Special
-					codes can be used like with `:map`,
-					e.g. "<C-Z>" for CTRL-Z.
-
-			If you want to use more options use the |term_start()|
-			function.
-
-When the buffer associated with the terminal is forcibly unloaded or wiped out
-the job is killed, similar to calling `job_stop(job, "kill")` .
-Closing the window normally results in |E947|.  When a kill method was set
-with "++kill={how}" or |term_setkill()| then closing the window will use that
-way to kill or interrupt the job.  For example: >
-	:term ++kill=term tail -f /tmp/log
-
-So long as the job is running the window behaves like it contains a modified
-buffer.  Trying to close the window with `CTRL-W :quit` fails.  When using
-`CTRL-W :quit!` the job is ended.  The text in the window is lost.  The buffer
-still exists, but getting it in a window with `:buffer` will show an empty
-buffer.
-
-Trying to close the window with `CTRL-W :close` also fails.   Using
-`CTRL-W :close!` will close the window and make the buffer hidden.
-
-You can use `CTRL-W :hide` to close the terminal window and make the buffer
-hidden, the job keeps running.  The `:buffer` command can be used to turn the
-current window into a terminal window.  If there are unsaved changes this
-fails, use !  to force, as usual.
-
-To have a background job run without a window, and open the window when it's
-done, use options like this: >
-	:term ++hidden ++open make
-Note that the window will open at an unexpected moment, this will interrupt
-what you are doing.
-
-							*E947* *E948*
-So long as the job is running, the buffer is considered modified and Vim
-cannot be quit easily, see |abandon|.
-
-When the job has finished and no changes were made to the buffer: closing the
-window will wipe out the buffer.
-
-Before changes can be made to a terminal buffer, the 'modifiable' option must
-be set.  This is only possible when the job has finished.  At the first change
-the buffer will become a normal buffer and the highlighting is removed.
-You may want to change the buffer name with |:file| to be able to write, since
-the buffer name will still be set to the command.
-
-
-Resizing ~
-							*terminal-resizing*
-The size of the terminal can be in one of three modes:
-
-1. The 'termsize' option is empty: The terminal size follows the window size.
-   The minimal size is 2 screen lines with 10 cells.
-
-2. The 'termsize' option is "rows*cols", where "rows" is the minimal number of
-   screen rows and "cols" is the minimal number of cells.
-
-3. The 'termsize' option is "rowsXcols" (where the x is upper or lower case).
-   The terminal size is fixed to the specified number of screen lines and
-   cells.  If the window is bigger there will be unused empty space.
-
-If the window is smaller than the terminal size, only part of the terminal can
-be seen (the lower-left part).
-
-The |term_getsize()| function can be used to get the current size of the
-terminal.  |term_setsize()| can be used only when in the first or second mode,
-not when 'termsize' is "rowsXcols".
-
-
-Terminal-Job and Terminal-Normal mode ~
-							*Terminal-mode*
-When the job is running the contents of the terminal is under control of the
-job.  That includes the cursor position.  Typed keys are sent to the job.
-The terminal contents can change at any time.  This is called Terminal-Job
-mode.
-
-Use CTRL-W N (or 'termkey' N) to switch to Terminal-Normal mode.  Now the
-contents of the terminal window is under control of Vim, the job output is
-suspended.  CTRL-\ CTRL-N does the same.
-
-Terminal-Job mode is where |:tmap| mappings are applied. Keys sent by
-|term_sendkeys()| are not subject to tmap, but keys from |feedkeys()| are.
-
-							*E946*
-In Terminal-Normal mode you can move the cursor around with the usual Vim
-commands, Visually mark text, yank text, etc.  But you cannot change the
-contents of the buffer.  The commands that would start insert mode, such as
-'i' and 'a', return to Terminal-Job mode.  The window will be updated to show
-the contents of the terminal. |:startinsert| is ineffective.
-
-In Terminal-Normal mode the statusline and window title show "(Terminal)".  If
-the job ends while in Terminal-Normal mode this changes to
-"(Terminal-finished)".
-
-It is not possible to enter Insert mode from Terminal-Job mode.
-
-
-Cursor style ~
-							*terminal-cursor-style*
-By default the cursor in the terminal window uses a not blinking block.  The
-normal xterm escape sequences can be used to change the blinking state and the
-shape.  Once focus leaves the terminal window Vim will restore the original
-cursor.
-
-An exception is when xterm is started with the "-bc" argument, or another way
-that causes the cursor to blink.  This actually means that the blinking flag
-is inverted.  Since Vim cannot detect this, the terminal window cursor
-blinking will also be inverted.
-
-
-Session ~
-							*terminal-session*
-A terminal window will be restored when using a session file, if possible and
-wanted.
-
-If "terminal" was removed from 'sessionoptions' then no terminal windows will
-be restored.
-
-If the job in the terminal was finished the window will not be restored.
-
-If the terminal can be restored, the command that was used to open it will be
-used again.  To change this use the |term_setrestore()| function.  This can
-also be used to not restore a specific terminal by setting the command to
-"NONE".
-
-
-Special keys ~
-							*terminal-special-keys*
-Since the terminal emulator simulates an xterm, only escape sequences that
-both Vim and xterm recognize will be available in the terminal window.  If you
-want to pass on other escape sequences to the job running in the terminal you
-need to set up forwarding.  Example: >
-	tmap <expr> <Esc>]b SendToTerm("\<Esc>]b")
-	func SendToTerm(what)
-	  call term_sendkeys('', a:what)
-	  return ''
-	endfunc
-
-
-Unix ~
-							*terminal-unix*
-On Unix a pty is used to make it possible to run all kinds of commands.  You
-can even run Vim in the terminal!  That's used for debugging, see below.
-
-Environment variables are used to pass information to the running job:
-    TERM		name of the terminal, 'term'
-    ROWS		number of rows in the terminal initially
-    LINES		same as ROWS
-    COLUMNS		number of columns in the terminal initially
-    COLORS		number of colors, 't_Co' (256*256*256 in the GUI)
-    VIM_SERVERNAME	v:servername
-
-The |client-server| feature can be used to communicate with the Vim instance
-where the job was started.  This only works when v:servername is not empty.
-If needed you can set it with: >
-	call remote_startserver('vim-server')
-
-In the job you can then do something like: >
-	vim --servername $VIM_SERVERNAME --remote +123 some_file.c
-This will open the file "some_file.c" and put the cursor on line 123.
-
-
-MS-Windows ~
-							*terminal-ms-windows*
-On MS-Windows winpty is used to make it possible to run all kind of commands.
-Obviously, they must be commands that run in a terminal, not open their own
-window.
-
-You need the following two files from winpty:
-
-    winpty.dll
-    winpty-agent.exe
-
-You can download them from the following page:
-
-    https://github.com/rprichard/winpty
-
-Just put the files somewhere in your PATH.  You can set the 'winptydll' option
-to point to the right file, if needed.  If you have both the 32-bit and 64-bit
-version, rename to winpty32.dll and winpty64.dll to match the way Vim was
-build.
-
-Environment variables are used to pass information to the running job:
-    VIM_SERVERNAME	v:servername
-
-==============================================================================
-2. Remote testing					*terminal-testing*
-
-Most Vim tests execute a script inside Vim.  For some tests this does not
-work, running the test interferes with the code being tested.  To avoid this
-Vim is executed in a terminal window.  The test sends keystrokes to it and
-inspects the resulting screen state.
-
-Functions ~
-
-term_sendkeys()		send keystrokes to a terminal (not subject to tmap)
-term_wait()		wait for screen to be updated
-term_scrape()		inspect terminal screen
-
-
-==============================================================================
-3. Diffing screen dumps					*terminal-diff*
-
-In some cases it can be bothersome to test that Vim displays the right
-characters on the screen.  E.g. with syntax highlighting.  To make this
-simpler it is possible to take a screen dump of a terminal and compare it to
-an expected screen dump.
-
-Vim uses the window size, text, color and other attributes as displayed.  The
-Vim screen size, font and other properties do not matter.  Therefore this
-mechanism is portable across systems.  A conventional screenshot would reflect
-all differences, including font size and family.
-
-
-Writing a screen dump test for Vim ~
-							*terminal-dumptest*
-For an example see the Test_syntax_c() function in
-src/testdir/test_syntax.vim.  The main parts are:
- Write a file you want to test with. This is useful for testing syntax
-  highlighting.  You can also start Vim with en empty buffer.
- Run Vim in a terminal with a specific size.  The default is 20 lines of 75
-  characters.  This makes sure the dump is always this size.  The function
-  RunVimInTerminal() takes care of this.  Pass it the arguments for the Vim
-  command.
- Send any commands to Vim using term_sendkeys().  For example: >
-	call term_sendkeys(buf, ":echo &lines &columns\<CR>")
- Check that the screen is now in the expected state, using
-  VerifyScreenDump().  This expects the reference screen dump to be in the
-  src/testdir/dumps/ directory.  Pass the name without ".dump".  It is
-  recommended to use the name of the test function and a sequence number, so
-  that we know what test is using the file.
- Repeat sending commands and checking the state.
- Finally stop Vim by calling StopVimInTerminal().
-
-The first time you do this you won't have a screen dump yet.  Create an empty
-file for now, e.g.: >
-	touch src/testdir/dumps/Test_function_name_01.dump
-
-The test will then fail, giving you the command to compare the reference dump
-and the failed dump, e.g.: >
-	call term_dumpdiff("Test_func.dump.failed", "dumps/Test_func.dump")
-
-Use this command in Vim, with the current directory set to src/testdir.
-Once you are satisfied with the test, move the failed dump in place of the
-reference: >
-	:!mv Test_func.dump.failed dumps/Test_func.dump
-
-
-Creating a screen dump ~
-							*terminal-screendump*
-
-To create the screen dump, run Vim (or any other program) in a terminal and
-make it show the desired state.  Then use the term_dumpwrite() function to
-create a screen dump file.  For example: >
-	:call term_dumpwrite(77, "mysyntax.dump")
-
-Here "77" is the buffer number of the terminal.  Use `:ls!` to see it.
-
-You can view the screen dump with term_dumpload(): >
-	:call term_dumpload("mysyntax.dump")
-
-To verify that Vim still shows exactly the same screen, run Vim again with
-exactly the same way to show the desired state.  Then create a screen dump
-again, using a different file name: >
-	:call term_dumpwrite(88, "test.dump")
-
-To assert that the files are exactly the same use assert_equalfile(): >
-	call assert_equalfile("mysyntax.dump", "test.dump")
-
-If there are differences then v:errors will contain the error message.
-
-
-Comparing screen dumps ~
-						*terminal-diffscreendump*
-
-assert_equalfile() does not make it easy to see what is different.
-To spot the problem use term_dumpdiff(): >
-	call term_dumpdiff("mysyntax.dump", "test.dump")
-
-This will open a window consisting of three parts:
-1.  The contents of the first dump
-2.  The difference between the first and second dump
-3.  The contents of the second dump
-
-You can usually see what differs in the second part.  Use the 'ruler' to
-relate it to the position in the first or second dump.
-
-Alternatively, press "s" to swap the first and second dump. Do this several
-times so that you can spot the difference in the context of the text.
-
-==============================================================================
-4. Debugging						*terminal-debug*
-
-The Terminal debugging plugin can be used to debug a program with gdb and view
-the source code in a Vim window.  Since this is completely contained inside
-Vim this also works remotely over an ssh connection.
-
-
-Starting ~
-							*termdebug-starting*
-Load the plugin with this command: >
-	packadd termdebug
-<							*:Termdebug*
-To start debugging use `:Termdebug` followed by the command name, for example: >
-	:Termdebug vim
-
-This opens two windows:
-
-gdb window	A terminal window in which "gdb vim" is executed.  Here you
-		can directly interact with gdb.  The buffer name is "!gdb".
-
-program window	A terminal window for the executed program.  When "run" is
-		used in gdb the program I/O will happen in this window, so
-		that it does not interfere with controlling gdb.  The buffer
-		name is "gdb program".
-
-The current window is used to show the source code.  When gdb pauses the
-source file location will be displayed, if possible.  A sign is used to
-highlight the current position, using highlight group debugPC.	 
-
-If the buffer in the current window is modified, another window will be opened
-to display the current gdb position.
-
-Focus the terminal of the executed program to interact with it.  This works
-the same as any command running in a terminal window.
-
-When the debugger ends, typically by typing "quit" in the gdb window, the two
-opened windows are closed.
-
-
-Example session ~
-							*termdebug-example*
-Start in the Vim "src" directory and build Vim: >
-	% make
-Start Vim: >
-	% ./vim
-Load the termdebug plugin and start debugging Vim: >
-	:packadd termdebug
-	:Termdebug vim
-You should now have three windows:
-    source  - where you started, has a window toolbar with buttons
-    gdb	    - you can type gdb commands here
-    program - the executed program will use this window
-
-You can use CTRL-W CTRL-W or the mouse to move focus between windows.
-Put focus on the gdb window and type: >
-	break ex_help
-	run
-Vim will start running in the program window. Put focus there and type: >
-	:help gui
-Gdb will run into the ex_help breakpoint.  The source window now shows the 
-ex_cmds.c file.  A ">>" marker will appear where the breakpoint was set.  The
-line where the debugger stopped is highlighted.  You can now step through the
-program.  Let's use the mouse: click on the "Next" button in the window
-toolbar.  You will see the highlighting move as the debugger executes a line
-of source code.
-
-Click "Next" a few times until the for loop is highlighted.  Put the cursor on
-the end of "eap->arg", then click "Eval" in the toolbar.  You will see this
-displayed:
-	"eap->arg": 0x555555e68855 "gui" ~
-This way you can inspect the value of local variables.  You can also focus the
-gdb window and use a "print" command, e.g.: >
-	print *eap
-If mouse pointer movements are working, Vim will also show a balloon when the
-mouse rests on text that can be evaluated by gdb.
-
-Now go back to the source window and put the cursor on the first line after
-the for loop, then type: >
-	:Break
-You will see a ">>" marker appear, this indicates the new breakpoint.  Now
-click "Cont" in the toolbar and the code until the breakpoint will be
-executed.
-
-You can type more advanced commands in the gdb window.  For example, type: >
-	watch curbuf
-Now click "Cont" in the toolbar (or type "cont" in the gdb window). Execution
-will now continue until the value of "curbuf" changes, which is in do_ecmd().
-To remove this watchpoint again type in the gdb window: >
-	delete 3
-
-You can see the stack by typing in the gdb window: >
-	where
-Move through the stack frames, e.g. with: >
-	frame 3
-The source window will show the code, at the point where the call was made to
-a deeper level.
-
-
-Stepping through code ~
-							*termdebug-stepping*
-Put focus on the gdb window to type commands there.  Some common ones are:
- CTRL-C	interrupt the program
- next		execute the current line and stop at the next line
- step		execute the current line and stop at the next statement,
-		entering functions
- finish	execute until leaving the current function
- where		show the stack
- frame N	go to the Nth stack frame
- continue	continue execution
-
-In the window showing the source code these commands can be used to control gdb:
- `:Run` [args]	    run the program with [args] or the previous arguments
- `:Arguments` {args}  set arguments for the next `:Run`
-
- `:Break`	set a breakpoint at the current line; a sign will be displayed
- `:Clear`	delete the breakpoint at the current line
-
- `:Step`	execute the gdb "step" command
- `:Over`	execute the gdb "next" command (`:Next` is a Vim command)
- `:Finish`	execute the gdb "finish" command
- `:Continue`	execute the gdb "continue" command
- `:Stop`	interrupt the program
-
-If 'mouse' is set the plugin adds a window toolbar with these entries:
-  Step		`:Step`
-  Next		`:Over`
-  Finish	`:Finish`
-  Cont		`:Continue`
-  Stop		`:Stop`
-  Eval		`:Evaluate`
-This way you can use the mouse to perform the most common commands.  You need
-to have the 'mouse' option set to enable mouse clicks.
-
-You can add the window toolbar in other windows you open with: >
-  :Winbar
-
-
-Inspecting variables ~
-							*termdebug-variables*
- `:Evaluate`	    evaluate the expression under the cursor
- `K`		    same
- `:Evaluate` {expr}   evaluate {expr}
- `:'<,'>Evaluate`     evaluate the Visually selected text
-
-This is similar to using "print" in the gdb window.
-You can usually shorten `:Evaluate` to `:Ev`.
-
-
-Other commands ~
-							*termdebug-commands*
- :Gdb	       jump to the gdb window
- :Program      jump to the window with the running program
-
-
-Communication ~
-						*termdebug-communication*
-There is another, hidden, buffer, which is used for Vim to communicate with
-gdb.  The buffer name is "gdb communication".  Do not delete this buffer, it
-will break the debugger.
-
-
-Customizing ~
-
-GDB command						 *termdebug-customizing*
-
-To change the name of the gdb command, set the "termdebugger" variable before
-invoking `:Termdebug`: >
-	let termdebugger = "mygdb"
-<							*gdb-version*
-Only debuggers fully compatible with gdb will work.  Vim uses the GDB/MI
-interface.  The "new-ui" command  requires gdb version 7.12 or later.  if you
-get this error:
-	Undefined command: "new-ui". Try "help".~
-Then your gdb is too old.
-
-
-Colors						*hl-debugPC* *hl-debugBreakpoint*
-
-The color of the signs can be adjusted with these highlight groups:
- debugPC		the current position
- debugBreakpoint	a breakpoint
-
-The defaults are, when 'background' is "light":
-  hi debugPC term=reverse ctermbg=lightblue guibg=lightblue
-  hi debugBreakpoint term=reverse ctermbg=red guibg=red
-
-When 'background' is "dark":
-  hi debugPC term=reverse ctermbg=darkblue guibg=darkblue
-  hi debugBreakpoint term=reverse ctermbg=red guibg=red
-
-
-Popup menu						*termdebug_popup*
-
-By default the Termdebug plugin sets 'mousemodel' to "popup_setpos" and adds
-these entries to the popup menu:
-	Set breakpoint		`:Break`
-	Clear breakpoint	`:Clear`
-	Evaluate		`:Evaluate`
-If you don't want this then disable it with: >
-	let g:termdebug_popup = 0
-
-
-Vim window width						*termdebug_wide*
-
-To change the width of the Vim window when debugging starts, and use a
-vertical split: >
-  let g:termdebug_wide = 163
-This will set &columns to 163 when :Termdebug is used.  The value is restored
-when quitting the debugger.
-If g:termdebug_wide is set and &Columns is already  larger than
-g:termdebug_wide then a vertical split will be used without changing &columns.
-Set it to 1 to get a vertical split without every changing &columns (useful
-for when the terminal can't be resized by Vim).
-
-
-
- vim:tw=78:ts=8:ft=help:norl:
--- a/Show More
+++ b/Show More