diff --git a/runtime/doc/editing.txt b/runtime/doc/editing.txt
index 1d104bc..a1d0e14 100644
--- a/runtime/doc/editing.txt
+++ b/runtime/doc/editing.txt
@@ -1,4 +1,4 @@
-*editing.txt*   For Vim version 7.4.  Last change: 2016 Jan 03
+*editing.txt*   For Vim version 7.4.  Last change: 2016 Jan 17
 
 
 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -639,6 +639,7 @@
 				:0argadd x	x a b c
 				:1argadd x	a x b c
 				:$argadd x	a b c x
+			And after the last one:
 				:+2argadd y	a b c x y
 			There is no check for duplicates, it is possible to
 			add a file to the argument list twice.
@@ -1458,6 +1459,16 @@
 When writing an undo file, the same key and method will be used for the text
 in the undo file. |persistent-undo|.
 
+To test for blowfish support you can use these conditions: >
+	has('crypt-blowfish')
+	has('crypt-blowfish2')
+This works since Vim 7.4.1099 while blowfish support was added earlier.
+Thus the condition failing doesn't mean blowfish is not supported. You can
+test for blowfish with: >
+	v:version >= 703
+And for blowfish2 with: >
+	v:version > 704 || (v:version == 704 && has('patch401'))
+<
 						*E817* *E818* *E819* *E820*
 When encryption does not work properly, you would be able to write your text
 to a file and never be able to read it back.  Therefore a test is performed to
diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt
index 866a7d9..5e0be58 100644
--- a/runtime/doc/eval.txt
+++ b/runtime/doc/eval.txt
@@ -873,7 +873,7 @@
 	:let c = getline(".")[col(".") - 1]
 
 If the length of the String is less than the index, the result is an empty
-String.  A negative index always results in an empty string (reason: backwards
+String.  A negative index always results in an empty string (reason: backward
 compatibility).  Use [-1:] to get the last byte.
 
 If expr8 is a |List| then it results the item at index expr1.  See |list-index|
@@ -4563,8 +4563,8 @@
 		respectively.  If the {id} argument is not specified or -1,
 		|matchadd()| automatically chooses a free ID.
 
-		The optional {dict} argmument allows for further custom
-		values. Currently this is used to specify a match specifc
+		The optional {dict} argument allows for further custom
+		values. Currently this is used to specify a match specific
 		conceal character that will be shown for |hl-Conceal|
 		highlighted matches. The dict can have the following members:
 
@@ -4797,9 +4797,9 @@
 perleval({expr})					*perleval()*
 		Evaluate Perl expression {expr} in scalar context and return
 		its result converted to Vim data structures. If value can't be
-		converted, it returned as string Perl representation.
-		Note: If you want a array or hash, {expr} must returns an
-		reference of it.
+		converted, it is returned as a string Perl representation.
+		Note: If you want an array or hash, {expr} must return a
+		reference to it.
 		Example: >
 			:echo perleval('[1 .. 4]')
 <			[1, 2, 3, 4]
@@ -5319,7 +5319,7 @@
 
 		'ignorecase', 'smartcase' and 'magic' are used.
 		
-		When the 'z' flag is not given seaching always starts in
+		When the 'z' flag is not given, searching always starts in
 		column zero and then matches before the cursor are skipped.
 		When the 'c' flag is present in 'cpo' the next search starts
 		after the match.  Without the 'c' flag the next search starts
@@ -7681,7 +7681,7 @@
 			From Vim version 4.5 until 5.0, every Ex command in
 			between the ":if" and ":endif" is ignored.  These two
 			commands were just to allow for future expansions in a
-			backwards compatible way.  Nesting was allowed.  Note
+			backward compatible way.  Nesting was allowed.  Note
 			that any ":else" or ":elseif" was ignored, the "else"
 			part was not executed either.
 
diff --git a/runtime/doc/if_mzsch.txt b/runtime/doc/if_mzsch.txt
index f1a0bd7..388a1ee 100644
--- a/runtime/doc/if_mzsch.txt
+++ b/runtime/doc/if_mzsch.txt
@@ -1,4 +1,4 @@
-*if_mzsch.txt*  For Vim version 7.4.  Last change: 2012 Dec 17
+*if_mzsch.txt*  For Vim version 7.4.  Last change: 2016 Jan 16
 
 
 		  VIM REFERENCE MANUAL    by Sergey Khorev
diff --git a/runtime/doc/mlang.txt b/runtime/doc/mlang.txt
index eb95660..808bc61 100644
--- a/runtime/doc/mlang.txt
+++ b/runtime/doc/mlang.txt
@@ -1,4 +1,4 @@
-*mlang.txt*     For Vim version 7.4.  Last change: 2012 Jan 15
+*mlang.txt*     For Vim version 7.4.  Last change: 2016 Jan 16
 
 
 		  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -97,13 +97,15 @@
 already.  Otherwise get the libintl.dll file if you don't have it yet:
 
 	http://sourceforge.net/projects/gettext
+Or:
+	https://mlocati.github.io/gettext-iconv-windows/
 
 This also contains tools xgettext, msgformat and others.
 
 libintl.dll should be placed in same directory with (g)vim.exe, or some
-place where PATH environment value describe.  Message files (vim.mo)
-have to be placed in "$VIMRUNTIME/lang/xx/LC_MESSAGES", where "xx" is the
-abbreviation of the language (mostly two letters).
+place where PATH environment value describe.  Vim also finds libintl-8.dll.
+Message files (vim.mo) have to be placed in "$VIMRUNTIME/lang/xx/LC_MESSAGES",
+where "xx" is the abbreviation of the language (mostly two letters).
 
 If you write your own translations you need to generate the .po file and
 convert it to a .mo file.  You need to get the source distribution and read
diff --git a/runtime/doc/tags b/runtime/doc/tags
index b3d67ba..4945072 100644
--- a/runtime/doc/tags
+++ b/runtime/doc/tags
@@ -3367,12 +3367,18 @@
 ==	change.txt	/*==*
 >	change.txt	/*>*
 >>	change.txt	/*>>*
+>backtrace	repeat.txt	/*>backtrace*
+>bt	repeat.txt	/*>bt*
 >cont	repeat.txt	/*>cont*
+>down	repeat.txt	/*>down*
 >finish	repeat.txt	/*>finish*
+>frame	repeat.txt	/*>frame*
 >interrupt	repeat.txt	/*>interrupt*
 >next	repeat.txt	/*>next*
 >quit	repeat.txt	/*>quit*
 >step	repeat.txt	/*>step*
+>up	repeat.txt	/*>up*
+>where	repeat.txt	/*>where*
 ?	pattern.txt	/*?*
 ?<CR>	pattern.txt	/*?<CR>*
 @	repeat.txt	/*@*
@@ -7086,6 +7092,7 @@
 mzscheme-funcref	if_mzsch.txt	/*mzscheme-funcref*
 mzscheme-mzeval	if_mzsch.txt	/*mzscheme-mzeval*
 mzscheme-sandbox	if_mzsch.txt	/*mzscheme-sandbox*
+mzscheme-setup	if_mzsch.txt	/*mzscheme-setup*
 mzscheme-threads	if_mzsch.txt	/*mzscheme-threads*
 mzscheme-vim	if_mzsch.txt	/*mzscheme-vim*
 mzscheme-vimext	if_mzsch.txt	/*mzscheme-vimext*
@@ -7531,6 +7538,7 @@
 perl-patterns	pattern.txt	/*perl-patterns*
 perl-using	if_perl.txt	/*perl-using*
 perl.vim	syntax.txt	/*perl.vim*
+perleval()	eval.txt	/*perleval()*
 persistent-undo	undo.txt	/*persistent-undo*
 pexpr-option	print.txt	/*pexpr-option*
 pfn-option	print.txt	/*pfn-option*
diff --git a/runtime/doc/todo.txt b/runtime/doc/todo.txt
index a2fc617..bc7b962 100644
--- a/runtime/doc/todo.txt
+++ b/runtime/doc/todo.txt
@@ -1,4 +1,4 @@
-*todo.txt*      For Vim version 7.4.  Last change: 2016 Jan 15
+*todo.txt*      For Vim version 7.4.  Last change: 2016 Jan 17
 
 
 		  VIM REFERENCE MANUAL	  by Bram Moolenaar
@@ -97,8 +97,6 @@
 Or use $XDG_DATA_DIRS.
 Also need to run update-desktop-database (Kuriyama Kazunobu, 2015 Nov 4)
 
-Add has('crypt-blowfish') and has('crypt-blowfish2') (Smu Johnson)
-
 Access to uninitialized memory in match_backref() regexp_nda.c:4882
 (Dominique Pelle, 2015 Nov 6)
 
@@ -125,42 +123,16 @@
    https://github.com/vim/vim/compare/v7.4.920%5E...v7.4.920.diff
 Diff for version.c contains more context, can't skip a patch.
 >
-Can src/GvimExt/Make_cyg.mak be removed?
-Same for src/xxd/Make_cyg.mak
-
 When t_Co is changed from termresponse, the OptionSet autocmmand event isn't
 triggered.  Use the code from the end of set_num_option() in
 set_color_count().
 
 Python: ":py raw_input('prompt')" doesn't work. (Manu Hack)
 
-Patch to fix cursor position in right-left mode with concealing.
-(Hirohito Higashi, 2016 Jan 13)
-
 Plugin to use Vim in MANPAGER.  Konfekt, PR #491
 
 Using uninitialized memory. (Dominique Pelle, 2015 Nov 4)
 
-Patch for explaining the help. (Christian Brabandt, 2015 Jan 8)
-Should be in the user manual?
-
-Patch to recognize string slice for variable followed by colon.
-(Hirohito Higashi, 2015 Nov 24)
-
-Patch to add debug backtrace. (Alberto Fanjul, 2015 Sep 27)
-Update 2016 Jan 2.  Issue #433
-
-Patch to gvim.nsi for appveyor build. (Ken Takata, 2016 Jan 12)
-
-Patch to improve behavior of dead keys on MS-Windows. (John Wellesz, 2015 Aug
-25)  https://github.com/vim/vim/pull/399.diff
-
-Patch to make mzscheme (racket) interface work. (Yukihiro Nakadaira, 2015 Jan
-10)  Doesn't work for me, need to build from source. Include anyway?
-Additional patch by Ken Takata, 2016 Jan 13.
-Merged patch by Yasuhiro Nakadaira,, 2016 Jan 14.
-Update for INSSTALLpc.txt by Ken Takata, Jan 14.
-
 MS-Windows: When editing a file with a leading space, writing it uses the
 wrong name. (Aram, 2014 Nov 7)  Vim 7.4.
 
@@ -171,19 +143,12 @@
 replacement includes hit. Reported by John Beckett, fix by Christian Brabandt,
 2016 Jan 11.
 
-Patch to fix pointer cast warning in VS2015. (Mike Williams, 2015 Dec 13)
-Patch to make building GVimExt with VS2015. (Mike Williams, 2015 Dec 13)
-
 Value returned by virtcol() changes depending on how lines wrap.  This is
 inconsistent with the documentation.
 
-Patch to add perleval(). (Damien, 2015 Dec 8, update 2016 Jan 4)
-
 Can we cache the syntax attributes, so that updates for 'relativenumber' and
 'cursorline'/'cursorcolumn' are a lot faster?
 
-Patch to add window and tab arguments to getcwd(). (Thinca, 2015 Nov 15)
-
 Build with Python on Mac does not always use the right library.
 (Kazunobu Kuriyama, 2015 Mar 28)
 
@@ -286,7 +251,7 @@
 - Remove LANGMAP_ADJUST() in other parts of the code.  Make sure the mode is
   covered by the above change.
 So that replaying the register doesn't use keymap/langmap and still does the
-same thing.  Remarks on issue 543.
+same thing.  Remarks on issue 543 (Roland Puntaier).
 
 Patch to add grepfile(). (Scott Prager, 2015 May 26)
 Work in progress.
diff --git a/runtime/doc/usr_02.txt b/runtime/doc/usr_02.txt
index ba29dc0..a3e9bf3 100644
--- a/runtime/doc/usr_02.txt
+++ b/runtime/doc/usr_02.txt
@@ -1,4 +1,4 @@
-*usr_02.txt*	For Vim version 7.4.  Last change: 2016 Jan 15
+*usr_02.txt*	For Vim version 7.4.  Last change: 2016 Jan 16
 
 		     VIM USER MANUAL - by Bram Moolenaar
 
@@ -554,38 +554,42 @@
 8) Ex-commands always start with ":", so to go to the :s command help: >
 	:help :s
 
-9) Key combinations.  They usually start with a single letter indicating
-   the mode for which they can be used.  E.g.: >
-   	:help i_CTRL-X
-<   takes you to the family of Ctrl-X commands for insert mode which can be
-   used to auto complete different things.  Note, that certain keys will
-   always be written the same, e.g. Control will always be CTRL.
-   For normal mode commands there is no prefix and the topic is available at
-   :h CTRL-<Letter>. E.g.  >
-   	:help CTRL-W
-<   In contrast >
-	:help c_CTRL-R
-<   will describe what the Ctrl-R does when entering commands in the Command
-   line and >
-   	:help v_Ctrl-A
-<   talks about incrementing numbers in visual mode and >
-	:help g_CTRL-A
-<   talks about the g<C-A> command (e.g. you have to press "g" then <Ctrl-A>).
-   Here the "g" stand for the normal command "g" which always expects a second
-   key before doing something similar to the commands starting with "z"
+9) Commands specifically for debugging start with ">".  To go to to the help
+   for the "cont" debug command: >
+	:help >cont
 
-10) Regexp items always start with /.  So to get help for the "\+" quantifier
+10) Key combinations.  They usually start with a single letter indicating
+    the mode for which they can be used.  E.g.: >
+   	:help i_CTRL-X
+<    takes you to the family of Ctrl-X commands for insert mode which can be
+    used to auto complete different things.  Note, that certain keys will
+    always be written the same, e.g. Control will always be CTRL.
+    For normal mode commands there is no prefix and the topic is available at
+    :h CTRL-<Letter>. E.g.  >
+   	:help CTRL-W
+<    In contrast >
+	:help c_CTRL-R
+<    will describe what the Ctrl-R does when entering commands in the Command
+    line and >
+   	:help v_Ctrl-A
+<    talks about incrementing numbers in visual mode and >
+	:help g_CTRL-A
+<    talks about the g<C-A> command (e.g. you have to press "g" then <Ctrl-A>).
+    Here the "g" stand for the normal command "g" which always expects a second
+    key before doing something similar to the commands starting with "z"
+
+11) Regexp items always start with /.  So to get help for the "\+" quantifier
     in Vim regexes: >
    	:help /\+
-<   If you need to know everything about regular expressions, start reading
-   at: >
+<    If you need to know everything about regular expressions, start reading
+    at: >
    	:help pattern.txt
 
-11) Registers always start with "quote". To find out about the special ":"
+12) Registers always start with "quote". To find out about the special ":"
     register: >
    	:help quote:
 
-12) Vim Script (VimL) is available at >
+13) Vim Script (VimL) is available at >
 	:help eval.txt
 <   Certain aspects of the language are available at :h expr-X where "X" is a
    single letter. E.g.  >
@@ -600,7 +604,7 @@
 <   talks about the append VimL function rather than how to append text in the
    current buffer.
 
-13) Mappings are talked about in the help page :h |map.txt|. Use >
+14) Mappings are talked about in the help page :h |map.txt|. Use >
     	:help mapmode-i
 <    to find out about the |:imap| command.  Also use :map-topic
     to find out about certain subtopics particular for mappings.  e.g: >
@@ -609,19 +613,19 @@
 	:help map-bar
 <    for how the '|' is handled in mappings.
 
-14) Command definitions are talked about :h command-topic, so use >
+15) Command definitions are talked about :h command-topic, so use >
 	:help command-bar
 <    to find out about the '!' argument for custom commands.
 
-15) Window management commands always start with CTRL-W, so you find the
+16) Window management commands always start with CTRL-W, so you find the
     corresponding help at :h CTRL-W_letter.  E.g. >
    	:help CTRL-W_p
-<    for moving the previous accessed window).  You can also access >
+<    for moving the previous accessed window.  You can also access >
 	:help windows.txt
 <    and read your way through if you are looking for window handling
     commands.
 
-16) Use |:helpgrep| to search in all help pages (and also of any installed
+17) Use |:helpgrep| to search in all help pages (and also of any installed
     plugins).  See |:helpgrep| for how to use it.
     To search for a topic: >
     	:helpgrep topic
@@ -632,7 +636,7 @@
     	:copen
 <    Move around to the match you like and press Enter to jump to that help.
 
-17) The user manual.  This describes help topics for beginners in a rather
+18) The user manual.  This describes help topics for beginners in a rather
     friendly way.  Start at |usr_toc.txt| to find the table of content (as you
     might have guessed): >
     	:help usr_toc.txt
@@ -645,31 +649,31 @@
     	:help 10.1
 <    goes to chapter 10.1 in |usr_10.txt| and talks about recording macros.
 
-18) Highlighting groups.  Always start with hl-groupname.  E.g. >
+19) Highlighting groups.  Always start with hl-groupname.  E.g. >
     	:help hl-WarningMsg
 <    talks about the WarningMsg highlighting group.
 
-19) Syntax highlighting is namespaced to :syn-topic e.g. >
+20) Syntax highlighting is namespaced to :syn-topic e.g. >
 	:help :syn-conceal
 <    talks about the conceal argument for the :syn command.
 
-20) Quickfix commands usually start with :c while location list commands
+21) Quickfix commands usually start with :c while location list commands
     usually start with :l
 
-21) Autocommand events can be found by their name: >
+22) Autocommand events can be found by their name: >
      	:help BufWinLeave
 <    To see all possible events: >
 	:help autocommands-events
 
-22) Command-line switches always start with "-".  So for the help of the -f
+23) Command-line switches always start with "-".  So for the help of the -f
     command switch of Vim use: >
     	:help -f
 
-23) Optional features always start with "+".  To find out about the
+24) Optional features always start with "+".  To find out about the
     conceal feature use: >
     	:help +conceal
 
-24) Documentation for included filetype specific functionality is usually
+25) Documentation for included filetype specific functionality is usually
     available  in the form ft-<filetype>-<functionality>.  So >
     	:help ft-c-syntax
 <    talks about the C syntax file and the option it provides.  Sometimes,
@@ -679,7 +683,7 @@
 	:help ft-tex-plugin
 <    are available.
 
-25) Error and Warning codes can be looked up directly in the help.  So >
+26) Error and Warning codes can be looked up directly in the help.  So >
 	:help E297
 <    takes you exactly to the description of the swap error message and >
 	:help W10