Update for November 23

bundle/.neobundle/doc/commentary.txt

@@ -26,6 +26,9 @@ gc                      Text object for a comment (operator pending mode
 gcgc                    Uncomment the current and adjacent commented lines.
 gcu
 
+                                                *:Commentary*
+:[range]Commentary      Comment or uncomment [range] lines
+
 The |User| CommentaryPost autocommand fires after a successful operation and
 can be used for advanced customization.
 

bundle/.neobundle/doc/exchange.txt

@@ -9,9 +9,9 @@ INTRODUCTION                                    *exchange*
 
 This plugin provides |operators| for exchanging text in two places. The main
 operator is |cx|, which is used in pairs. Each time it is used, it defines a
-region of text to to be exchanged; on the second use, the two defined regions
-are exchanged. If one region is fully contained within the other, it replaces
-the containing region.
+region of text to be exchanged; on the second use, the two defined regions are
+exchanged. If one region is fully contained within the other, it replaces the
+containing region.
 
 MAPPINGS                                        *exchange-mappings*
 
@@ -32,7 +32,7 @@ cxc                     Clear any defined region of text (previously defined
                         by a |cx| command)
 
                                                 *v_X* *exchange-visual*
-{visal}X                Can be used in |visual-mode|.
+{Visual}X               Can be used in |visual-mode|.
 
 EXAMPLES                                        *exchange-examples*
 
@@ -55,7 +55,7 @@ To change the default mappings, simply provide your own mappings to the
 commands below. The default mappings are as follows:
 
     nmap cx <Plug>(Exchange)
-    vmap cx <Plug>(Exchange)
+    xmap X <Plug>(Exchange)
     nmap cxc <Plug>(ExchangeClear)
     nmap cxx <Plug>(ExchangeLine)
 

bundle/.neobundle/doc/extradite.txt

@@ -22,6 +22,9 @@ COMMANDS                                        *extradite-commands*
                         To show abbreviated commit hashes in the buffer, set
                         *g:extradite_showhash*
                         to 1 in your .vimrc
+                        To use vertical split instead of horizontal one, set
+                        *g:extradite_diff_split*
+                        to 'belowright vertical split'.
 
 MAPPINGS                                        *extradite-mappings*
 

bundle/.neobundle/doc/fugitive.txt

@@ -55,20 +55,40 @@ that are part of Git repositories).
                         p     |:Git| add --patch
                         p     |:Git| reset --patch (staged files)
                         q     close status
-                        R     reload status
+                        r     reload status
                         S     |:Gvsplit|
 
                                                 *fugitive-:Gcommit*
 :Gcommit [args]         A wrapper around git-commit.  If there is nothing
                         to commit, |:Gstatus| is called instead.  Unless the
                         arguments given would skip the invocation of an editor
                         (e.g., -m), a split window will be used to obtain a
-                        commit message.  Write and close that window (:wq or
-                        |:Gwrite|) to finish the commit.  Unlike when running
-                        the actual git-commit command, it is possible (but
-                        unadvisable) to muck with the index with commands like
-                        git-add and git-reset while a commit message is
-                        pending.
+                        commit message, or a new tab if -v is given.  Write
+                        and close that window (:wq or |:Gwrite|) to finish the
+                        commit.  Unlike when running the actual git-commit
+                        command, it is possible (but unadvisable) to alter the
+                        index with commands like git-add and git-reset while a
+                        commit message is pending.
+
+                                                *fugitive-:Gmerge*
+:Gmerge [args]          Calls git-merge and loads errors and conflicted files
+                        into the quickfix list.  Opens a |:Gcommit| style
+                        split window for the commit message if the merge
+                        succeeds.  If called during a merge conflict, the
+                        conflicted files from the current index are loaded
+                        into the quickfix list.
+
+                                                *fugitive-:Gpull*
+:Gpull [args]           Like |:Gmerge|, but for git-pull.
+
+                                                *fugitive-:Gpush*
+:Gpush [args]           Invoke git-push, load the results into the quickfix
+                        list, and invoke |:cwindow| to reveal any errors.
+                        |:Dispatch| is used if available for asynchronous
+                        invocation.
+
+                                                *fugitive-:Gfetch*
+:Gfetch [args]          Like |:Gpush|, but for git-fetch.
 
                                                 *fugitive-:Ggrep*
 :Ggrep [args]           |:grep| with git-grep as 'grepprg'.
@@ -84,6 +104,11 @@ that are part of Git repositories).
                         previous commits rather than previous file revisions
                         are loaded.
 
+:{range}Glog [args]     Use git-log -L to load previous revisions of the given
+                        range of the current file into the quickfix list.  The
+                        cursor is positioned on the first line of the first
+                        diff hunk for each commit.
+
                                                 *fugitive-:Gllog*
 :Gllog [args]           Like |:Glog|, but use the location list instead of the
                         quickfix list.
@@ -149,14 +174,16 @@ that are part of Git repositories).
                         index is used (which means a three-way diff during a
                         merge conflict, making it a git-mergetool
                         alternative).  The newer of the two files is placed
-                        to the right.  Use |do| and |dp| and write to the
-                        index file to simulate "git add --patch".
+                        to the right or bottom, depending on 'diffopt' and
+                        the width of the window relative to 'textwidth'.  Use
+                        |do| and |dp| and write to the index file to simulate
+                        "git add --patch".
 
                                                 *fugitive-:Gsdiff*
-:Gsdiff [revision]      Like |:Gdiff|, but split horizontally.
+:Gsdiff [revision]      Like |:Gdiff|, but always split horizontally.
 
                                                 *fugitive-:Gvdiff*
-:Gvdiff [revision]      Identical to |:Gdiff|.  For symmetry with |:Gsdiff|.
+:Gvdiff [revision]      Like |:Gdiff|, but always split vertically.
 
                                                 *fugitive-:Gmove*
 :Gmove {destination}    Wrapper around git-mv that renames the buffer
@@ -172,11 +199,10 @@ that are part of Git repositories).
 
                                                 *fugitive-:Gblame*
 :Gblame [flags]         Run git-blame on the file and open the results in a
-                        scroll bound vertical split.  Press enter on a line to
-                        reblame the file as it was in that commit.  You can
-                        give any of ltfnsewMC as flags and they will be passed
-                        along to git-blame.  The following maps, which work on
-                        the cursor line commit where sensible, are provided:
+                        scroll bound vertical split.  You can give any of
+                        ltfnsewMC as flags and they will be passed along to
+                        git-blame.  The following maps, which work on the
+                        cursor line commit where sensible, are provided:
 
                         g?    show this help
                         A     resize to end of author column

bundle/.neobundle/doc/gist-vim.txt

@@ -106,6 +106,10 @@ USAGE                                                 *:Gist* *gist-vim-usage*
 >
     :Gist -ls
 <
+- Open the gist on browser after you post or update it.
+>
+    :Gist -b
+<
 ==============================================================================
 TIPS                                                           *gist-vim-tips*
 
@@ -146,7 +150,10 @@ If you want to show your private gists with ":Gist -l": >
 If you want your gist to be private by default: >
 
     let g:gist_post_private = 1
+<
+If you want your gist to be anonymous by default: >
 
+    let g:gist_post_anonymous = 1
 <
 If you want to edit all files for gists containing more than one: >
 
@@ -266,6 +273,8 @@ Then, add following into your ~/.vimrc
 <
 This is not secure at all, so strongly discouraged.
 
+NOTE: the username is optional if you only send anonymous gists.
+
 ==============================================================================
 FAQ                                                           *gist-vim-faq*
 

bundle/.neobundle/doc/gitgutter.txt

@@ -237,6 +237,9 @@ Add to your |vimrc|
   let g:gitgutter_signs = 0
 <
 
+Note that the sign column will still be present if you have line highlighting
+switched on.
+
 TO TURN ON LINE HIGHLIGHTING BY DEFAULT
 
 Add to your |vimrc|
@@ -267,12 +270,7 @@ a. Why are the colours in the sign column weird?
   Your colorscheme is configuring the |hl-SignColumn| highlight group weirdly.
   Please see |GitGutterCustomisation| on customising the sign column.
 
-b. Why is no sign shown if I delete the first line(s) in a file?
-
-  vim-gitgutter shows removed lines with a sign on the line above.  In this
-  case there isn't a line above so vim-gitgutter can't show the sign.
-
-c. What happens if I also use another plugin which uses signs (e.g. Syntastic)?
+b. What happens if I also use another plugin which uses signs (e.g. Syntastic)?
 
   Vim only allows one sign per line. Before adding a sign to a line,
   vim-gitgutter checks whether a sign has already been added by somebody else.

bundle/.neobundle/doc/incsearch.txt

@@ -1,7 +1,7 @@
 *incsearch.txt*	Incrementally highlight all pattern matches
 
 Author  : haya14busa <hayabusa1419@gmail.com>
-Version : 0.9.8
+Version : 0.9.9
 License : MIT license {{{
 
 	Copyright (c) 2014 haya14busa
@@ -177,6 +177,19 @@ Improved 'magic' option~
 <
 	default: ''
 
+Smart backward word~
+					*g:incsearch#smart_backward_word*
+	If this option is set to 1, the backward word detection which is used
+	when |c_Ctrl-w| and |c_CTRL-R_CTRL-W| become smart. Smart backward
+	word doesn't include unexpected reglular expression and treats regular
+	expression flag as one word. For example, when the command line is
+	`/\vword` and type <C-w>, the vim default command line will become
+	`/\`, but since |\v| is not the part of word but just a regular
+	expression flag, it's useful not to include 'v' as a backward word.
+	This option fix this problem.
+
+	default: 1
+
 ------------------------------------------------------------------------------
 Command line interface~
 					*incsearch-commandline-interface*
@@ -220,6 +233,10 @@ Command line interface~
 		    IncSearchNoreMap <Up>    <Over>(incsearch-scroll-b)
 		endfunction
 <
+						*g:incsearch#vim_cmdline_keymap*
+	Apply vim default |:cnoremap| and |:cmap| mappings to custom command line
+	interface of |incsearch.vim|. default: 1
+
 						*g:incsearch#emacs_like_keymap*
 	It enables Emacs-like keymappings if you set
 	|g:incsearch#emacs_like_keymap| to 1. default: 0
@@ -334,16 +351,31 @@ KNOWN ISSUES						*incsearch-issues*
 ==============================================================================
 CHANGELOG						*incsearch-changelog*
 
-Version 1.0 Roadmap~
-
-1.0.0	1. Pattern converter feature
+Version 2.0(?) Roadmap~
+2.0.0	1. Pattern converter feature
 	    - https://github.com/haya14busa/incsearch.vim/tree/converter
 	    - Implement fuzzy-search, migemo, spellcheck and other feature
 	    - Make public pattern converter API for customization
 	    - Write test for converer feature
+
+Version 1.0 Roadmap~
+1.0.0	1. More stable, compatible with default |/| behavior
 	2. More configurable options
 	    - e.g. option for prompt format including right prompt feature
 
+0.9.9	2014-11-17
+	1. Smart backward word feature. See: |g:incsearch#smart_backward_word|
+	2. Implement |g:incsearch#vim_cmdline_keymap| option which apply
+	   mappings defined with |:cmap| and |:cnoremap| to custome command line
+	   interface of incsearch.vim
+	3. Do not highlight annoying patterns which matches everything like
+	   `\v`, `vim\|`, etc..
+	4. Interactive module management (e.g. |g:incsearch#emacs_like_keymap|)
+	6. Fix |c_<C-r>_<C-w>| behavoir to be compatible with default one
+	7. Fix cancel behavior
+	8. Fix & improve {rhs} handling (after exit mappings, <C-r>=, etc...)
+	9. Fix minor problems
+
 0.9.8	2014-10-25
 	1. Handle |last-pattern| incrementally. See: |<Over>(incsearch-next)|
 	2. Now |c_Ctrl-p| and |c_Ctrl-n| works by default and fix history