| Commit message (Collapse) | Author | Age |
| |
|
| |
|
|\
| |
| | |
Fix plugin which opens ShaDa files
|
| |
| |
| | |
Fixes #5482
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| | |
Old versions of `xsel` do not support some required features.
Fall back to `xclip` then.
Closes #5853
|
|/
|
| |
Closes #5806
|
|\ |
|
| |
| |
| |
| | |
vim-patch:7.4.1838
|
| |
| |
| |
| |
| |
| |
| | |
- Eliminate global test_autochdir.
- Eliminate VimL function test_autochdir()
- Use a lua test instead. Fails correctly after reverting
0c4347997954 / vim-patch:7.4.2015.
|
| |
| |
| |
| |
| |
| | |
Updated runtime files.
https://github.com/vim/vim/commit/6f1d9a096bf22d50c727dca73abbfb8e3ff55176
|
| | |
|
| | |
|
|/
|
|
|
| |
runtime: Add underscore to {} helpSpecial syntax pattern
docs: Added generated api-funcs.txt
|
|\
| |
| | |
vim-patch:7.4.2183,7.4.2194,7.4.2201,7.4.2204,0952131,7.4.2215,7.4.2225,7.4.2226,7.4.2272,7.4.2273,7.4.2277,7.4.2294
|
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: getwininfo() and getbufinfo() are inefficient.
Solution: Do not make a copy of all window/buffer-local options. Make it
possible to get them with gettabwinvar() or getbufvar().
https://github.com/vim/vim/commit/3056735ae8a366aa7fcb51872520895251858637
|
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: The field names used by getbufinfo(), gettabinfo() and
getwininfo() are not consistent.
Solution: Use bufnr, winnr and tabnr. (Yegappan Lakshmanan)
https://github.com/vim/vim/commit/339288377072f66ec88e21903e75a82d23ffbf4f
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: It's not easy to find out if a window is a quickfix or location
list window.
Solution: Add "loclist" and "quickfix" entries to the dict returnec by
getwininfo(). (Yegappan Lakshmanan)
https://github.com/vim/vim/commit/386600f0cbcb8add099c723cf84634f46df2f788
|
| |
| |
| |
| |
| |
| | |
Updated runtime files.
https://github.com/vim/vim/commit/0952131376a517fc12dc5ae908a97018b4ee23f0
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: It is not easy to get information about buffers, windows and
tabpages.
Solution: Add getbufinfo(), getwininfo() and gettabinfo(). (Yegappan
Lakshmanan)
https://github.com/vim/vim/commit/b5ae48e9ffd3b8eb6ca4057de11f1bddcde8ce6f
|
| |
| |
| |
| |
| |
| |
| | |
Problem: The sign column disappears when the last sign is deleted.
Solution: Add the 'signcolumn' option. (Christian Brabandt)
https://github.com/vim/vim/commit/95ec9d6a6ab3117d60ff638670a803d43974ba51
|
|/ |
|
|
|
|
| |
Instead, a note was added to `:h man.vim` on how 'fileignorecase'
controls the case sensitivity of completion.
|
|
|
|
|
|
| |
- Improves compatibility with shell=tcsh.
- man.vim: split read_page into get_page, put_page. Do not split the
window until we know there is going to be output.
|
|\ |
|
| | |
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Problem: There is a :cbottom command but no :lbottom command.
Solution: Add :lbottom. (Yegappan Lakshmanan)
https://github.com/vim/vim/commit/537ef08408c50e0c4104d57f74993b3b0ed9560d
|
|/
|
|
|
|
|
| |
Problem: Cannot easily scroll the quickfix window.
Solution: Add ":cbottom".
https://github.com/vim/vim/commit/dcb170018642ec144cd87d9d9fe076575b8d1263
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is a regression introduced by:
https://github.com/neovim/neovim/pull/5290/files#diff-8691c83194ea5f1342ecc9f17b4c51d8R46
When the <plug> mappings were changed to using :Man, they should have changed to
use `nnoremap` as well.
Fixes #5776.
|
|
|
|
| |
References #5529
|
|
|
| |
Closes #5763.
|
| |
|
| |
|
|
|
|
| |
Leave a note in vim_diff.txt about it.
|
|
|
|
|
|
|
| |
Problem: get() works for Partial but not for Funcref.
Solution: Accept Funcref. Also return the function itself. (Nikolai Pavlov)
https://github.com/vim/vim/commit/03e19a04ac2ca55643663b97b6ab94043233dcbd
|
|
|
|
|
|
|
| |
Problem: Cannot get the items stored in a partial.
Solution: Support using get() on a partial.
https://github.com/vim/vim/commit/2bbf8eff6fab16d86e7bcfc0da1962d31bec7891
|
|
|
|
|
|
|
|
|
| |
Problem: When using a partial on a dictionary it always gets bound to that
dictionary.
Solution: Make a difference between binding a function to a dictionary
explicitly or automatically.
https://github.com/vim/vim/commit/1d429610bf9e99a6252be8abbc910d6667e4d1da
|
|
|
|
|
|
|
| |
Problem: Passing cookie to a callback is clumsy.
Solution: Change function() to take arguments and return a partial.
https://github.com/vim/vim/commit/1735bc988c546cc962c5f94792815b4d7cb79710
|
|\
| |
| | |
doc: api_info(), typval_encode.h
|
| | |
|
| |
| |
| |
| | |
Closes #5751
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This ameliorates use-cases like:
:!cat foo.txt
:make
where the user is interested in the last few lines of output.
Try these shell-based ex-commands before/after this commit:
:grep -r '' *
:make
:!yes
:!grep -r '' *
:!git grep ''
:!cat foo
:!echo foo
:!while true; do date; done
:!for i in `seq 1 20000`; do echo XXXXXXXXXX $i; done
In all cases the last few lines of the command should always be shown,
regardless of where throttling was triggered.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Periodically skip :! spam. This is a "cheat" that works for all UIs and greatly
improves responsiveness when :! spams MB or GB of output:
:!yes
:!while true; do date; done
:!git grep ''
:grep -r '' *
After ~10KB of data is seen from a single :! invocation, output will be skipped
for ~1s and three dots "..." will pulse in the bottom-left. Thereafter the
behavior alternates at every:
* 10KB received
* ~1s throttled
This also avoids out-of-memory which could happen with large :! outputs.
Note: This commit does not change the behavior of execute(':!foo').
execute(':!foo') returns the string ':!foo^M', it captures *only* Vim
messages, *not* shell command output. Vim behaves the same way.
Use system('foo') for capturing shell command output.
Closes #1234
Helped-by: oni-link <knil.ino@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- By re-enabling code blocks (every line that doesn't begin with a "-" and is
indented by at least 4 spaces), we prevent the Markdown syntax to evaluate "_"
as beginning for italic text.
That's the case for `:CheckHealth deoplete` for instance. It would output:
$ cat /tmp/log_{PID}
Since the deoplete check gets run first, almost all of the following
`:CheckHealth` output would be italic.
- Since we re-enable code blocks, we now have to tell our custom syntax that it
can be part of markdownCodeBlock as well. Otherwise there would be no
highlithing for our keywords ERROR, INFO, etc. after 4 spaces of indent.
- Since we do the above anyway, we make it work for mkdListItemLine as well.
That's a highlight group from `plasticboy/vim-markdown` opposed to the shipped
markdown syntax (which essentially is `tpope/vim-markdown`). Before this patch
there was no highlighting at all in the `:CheckHealth` output.
|
| |
| |
| |
| | |
This prevents the string "error" within error messages to be highlighted as
healthError.
|