aboutsummaryrefslogtreecommitdiff
path: root/runtime
Commit message (Collapse)AuthorAge
* Merge #8797 from janlazo/vim-8.0.0687Justin M. Keyes2018-08-09
|\
| * vim-patch:8.0.0735: no indication that the quickfix window/buffer changedJan Edmund Lazo2018-07-28
| | | | | | | | | | | | | | | | Problem: There is no way to notice that the quickfix window contents has changed. Solution: Increment b:changedtick when updating the quickfix window. (Yegappan Lakshmanan) https://github.com/vim/vim/commit/a8788f4d0b991f466b607c2c5bc6fd600bc78a97
| * vim-patch:8.0.0687: minor issues related to quickfixJan Edmund Lazo2018-07-28
| | | | | | | | | | | | | | | | | | Problem: Minor issues related to quickfix. Solution: Set the proper return status for all cases in setqflist() and at test cases for this. Move the "adding" flag outside of FEAT_WINDOWS. Minor update to the setqflist() help text. (Yegappan Lakshmanan) https://github.com/vim/vim/commit/86f100dc0922e83bead7bcd5fd2bb2abbf153f46
* | ruby: detect rbenv shims for other versions (#8733)Marco Hinz2018-08-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When rbenv is used for managing Ruby installations, just checking for an executable called "neovim-ruby-host" is not enough. It has to be run as well. If it does not return 0, then neovim-ruby-host is merely a shim for another Ruby installation. $ rbenv versions 2.5.0 * 2.5.1 (set by /Users/mhi/.rbenv/version) $ rbenv whence neovim-ruby-host 2.5.0 $ which neovim-ruby-host /Users/mhi/.rbenv/shims/neovim-ruby-host $ neovim-ruby-host rbenv: neovim-ruby-host: command not found The `neovim-ruby-host' command exists in these Ruby versions: 2.5.0 $ echo $? 127 Additionally, the detection logic was moved from provider#ruby#Detect() to s:detect(), because the former is run in the sandbox which forbids calling system().
* | Merge pull request #8660 from ↵Björn Linse2018-08-02
|\ \ | |/ |/| | | | | phodge/7688-nvim-buf-lines-should-return-empty-list-for-unloaded-buffer handle unloaded buffers in nvim_buf_*() functions
| * DOC: regenerate api docsPeter Hodge2018-07-25
| |
* | Merge pull request #8770 from janlazo/vim-8.0.0726Justin M. Keyes2018-07-29
|\ \
| * | vim-patch:8.0.0794: checking translations fails with multiple NLJan Edmund Lazo2018-07-23
| |/ | | | | | | | | | | | | Problem: The script to check translations fails if there is more than one NL in one line. Solution: Count the number of NL characters. Make count() accept a string. https://github.com/vim/vim/commit/9966b21a57277986217aa28237d6c247ebd060d7
* | checkhealth: always report stderr with errors (#8783)Daniel Hahler2018-07-29
| | | | | | This also reports the exit code (e.g. 127 for when pyenv-which fails).
* | checkhealth: do not use exepath with host_prog (#8784)Daniel Hahler2018-07-29
|/ | | | | | | | | | This would need to get `expand`ed to not become empty, and is being handled by s:check_bin already. `s:check_bin` will also complain about e.g. "~/.pyenv/versions/3.6.6/bin/python" not being executable, but that reflects that the host will fail to start with it. Fixes #8778
* Merge #8589 'VimL: Remove legacy v:xx aliases'Justin M. Keyes2018-07-23
|\
| * Make "v:errmsg", "v:shell_error" and "v:this_session" distinctShougo Matsushita2018-07-23
|/
* man.vim: improve manSentence regex (#8764)Synray2018-07-22
| | | ref https://github.com/neovim/neovim/pull/8709#issuecomment-406319186
* ui: docs for ext_newgrid and ext_hlstateBjörn Linse2018-07-21
|
* docJustin M. Keyes2018-07-18
|
* vim-patch:8.0.0630: it is not easy to work on lines without a match (#8734)Jan Edmund Lazo2018-07-13
| | | | | | | Problem: The :global command does not work recursively, which makes it difficult to execute a command on a line where one pattern matches and another does not match. (Miles Cranmer) Solution: Allow for recursion if it is for only one line. (closes vim/vim#1760) https://github.com/vim/vim/commit/f84b122a99da75741ae686fabb6f81b8b4755998
* vim-patch:8.0.0{474,475,492,633,1251} (#8725)Jan Edmund Lazo2018-07-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * vim-patch:8.0.0474: the client-server feature is not tested Problem: The client-server feature is not tested. Solution: Add a test. https://github.com/vim/vim/commit/15bf76d40be1f1622ff5cc16596c308e76e2ca94 * vim-patch:8.0.0475: not enough testing for the client-server feature Problem: Not enough testing for the client-server feature. Solution: Add more tests. Add the remote_startserver() function. Fix that a locally evaluated expression uses function-local variables. https://github.com/vim/vim/commit/7416f3e73ab2c4e7ae3adc2ff6e70234f7d40d2e * vim-patch:8.0.0492: a failing client-server request can make Vim hang Problem: A failing client-server request can make Vim hang. Solution: Add a timeout argument to functions that wait. https://github.com/vim/vim/commit/81b9d0bd5c705815e903e671e81b0b05828efd9c Include src/nvim/testdir/test_clientserver.vim changes from patches 8.0.0477, 8.0.0479. * vim-patch:8.0.0633: the client-server test is still a bit flaky Problem: The client-server test is still a bit flaky. Solution: Wait a bit for the GUI to start. Check that the version number can be obtained. https://github.com/vim/vim/commit/60964f68740b8abcbb2d3f0f3aeade21d1bacb22 Include src/nvim/testdir/test_clientserver.vim changes from patches 8.0.0507, 8.0.0511. * vim-patch:8.0.1251: invalid expressin passed to WaitFor() Problem: Invalid expressin passed to WaitFor(). Solution: Check if the variable exists. https://github.com/vim/vim/commit/d97fbf171ec0e63117813da045d2a1c51a9b6f62
* man.vim: C highlighting for EXAMPLES section #8709Synray2018-07-12
|
* man.vim: fix for mandoc (#8698)Brayden Banks2018-07-08
| | | | | When giving a section, the first candidate selection was not performed. followup/fixup #8341
* vim-patch:8.0.0663: unexpected error with 'verbose' (#8692)Jan Edmund Lazo2018-07-06
| | | | | Problem: Giving an error message only when 'verbose' set is unexpected. Solution: Give a warning message instead. https://github.com/vim/vim/commit/f8be461d0284110b321be748fea206d4169b98bb
* provider/node: npm --loglevel silent (#8682)Takuya Matsuyama2018-07-04
| | | | closes #8674 npm log level may cause unexpected output.
* highlight: high-priority CursorLine if fg is set. #8578Yichao Zhou2018-06-28
| | | | | | | | | | | | closes #7383 closes #7715 This implements the compromise described in #7383: * low-priority CursorLine if foreground is not set * high-priority ("same as Vim" priority) CursorLine if foreground is set ref d1874ab2821d076397290cc154d87ec2dc352c79 ref 56eda2aa17c80ba380b606f9466f288fb8162dd3
* doc (#8652)Justin M. Keyes2018-06-28
|
* checkhealth: Python: fix VIRTUAL_ENV check (#8628)Daniel Hahler2018-06-24
| | | | | Compare `$VIRTUAL_ENV` to `python_bin`. This is necessary when `g:python_host_prog` is set to an absolute path, and looking up `pyname` in `$PATH` yields another result.
* defaults: shortmess+=F (#8619)Justin M. Keyes2018-06-22
| | | | | | Because we default to laststatus=2 (statusline is always visible), the :edit message is not useful. ref #6289
* vim-patch:8.0.0542: getpos() can return a negative line number (#8580)Jan Edmund Lazo2018-06-19
| | | | | Problem: getpos() can return a negative line number. (haya14busa) Solution: Handle a zero topline and botline. (closes vim/vim#1613) https://github.com/vim/vim/commit/a1d5fa65bc7e8a548858e9c295a192b63dcd011b
* cmake: Comply with new CMP0054 policyJames McCoy2018-06-18
|
* Ex mode: use getexline() instead of getexmodeline()Justin M. Keyes2018-06-17
| | | | | | | | | | | | | | | | | | | | | This changes Ex mode (Q, -e) to work like Vim's "improved Ex mode" (gQ, -E). That brings some small behavior differences, but should not impact most Ex scripts (unless, for example, they depend on mappings being disabled--but that can be solved for -e by skipping user config). Before this change: * the screen test hangs. After this change: * Q acts like gQ. * -e/-es differs from -E/-Es only in its treatment of stdin. This moves towards potentially removing getexmodeline(). (HINT: That does NOT mean "removing Ex mode", it means removing the Vi-compatible Ex mode, which differs from Vim's "improved Ex mode" only in some minor details (e.g. mappings are disabled).) ref #1089 :-)~
* checkhealth: node.js: also search yarn #8528Ahmed El Gabri2018-06-17
| | | | | - "neovim" package may be installed with yarn. Check yarn if npm fails. - Use filereadable() instead of glob(). closes #8552
* fillchars: make checks more strict and improve testsBjörn Linse2018-06-14
|
* Add ‘eob’ option to fillcharsJack Bracewell2018-06-13
| | | | | This option allows configuring what character is shown on the empty lines at the end of a buffer, previously hardcoded to ‘~’
* options: remove 'maxcombine` option (always use 6)Björn Linse2018-06-13
|
* docJustin M. Keyes2018-06-12
|
* doc: APIJustin M. Keyes2018-06-11
|
* doc: job/channel, misc #7783Justin M. Keyes2018-06-11
| | | | | | | | | | | doc: termios defaults. ref #6992 doc: :help shell-powershell doc: provider: Python minimum version is 2.7, 3.4 doc: remove :!start special-case. #5844 doc: mention #7917 change which accepts empty Array for Dictionary parameter doc: <Cmd> pseudokey doc: lmap change #5658 doc: -s, -es
* checkhealth: fix nodejs provider advice (#8522)Colin Yates2018-06-10
| | | closes #8515
* Merge #7679 'startup: treat stdin as text instead of commands'Justin M. Keyes2018-06-10
|\
| * win/startup: remove --literalJustin M. Keyes2018-06-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes 2 failing tests in startup_spec.lua. The Windows-only `--literal` option complicates support of "stdin-as-text + file-args" (#7679). Could work around it, but it's not worth the trouble: - users have a reasonable (and englightening) alternative: nvim +"n *" - "always literal" is more consistent/predictable - avoids platform-specific special-case Unrelated changes: - Replace fileno(stdxx) with STDXX_FILENO for consistency (not motivated by any observed technical reason).
* | doc: API: api-buffer-updatesJustin M. Keyes2018-06-08
| | | | | | | | | | - move to api.txt - rewrite
* | Merge #7917 'API: buffer updates'Justin M. Keyes2018-06-08
|\ \
| * | Rename some more, fixe borked renamingKillTheMule2018-05-23
| | |
| * | Unify updates_start and updates to lines_eventKillTheMule2018-05-23
| | | | | | | | | | | | Also rename changedtick -> changedtick_event
| * | Some renamings and doc changesKillTheMule2018-05-23
| | |
| * | Try fixing that test on travisKillTheMule2018-05-23
| | |
| * | The grand renamingKillTheMule2018-05-23
| | |
| * | DocKillTheMule2018-05-23
| | |
| * | Make LiveUpdate return lastline instead of numreplacedKillTheMule2018-05-23
| | | | | | | | | | | | In analogy to `nvim_buf_set_lines`.
| * | Make separate functions to start/stop live updatesKillTheMule2018-05-23
| | |
| * | API: Document buffer updatesPeter Hodge2018-05-23
| | | | | | | | | | | | | | | Originally written by @phodge in https://github.com/neovim/neovim/pull/5269.
* | | vim-patch:8.0.0255: setpos() does not use the buffer argument for all marksJan Edmund Lazo2018-06-06
| |/ |/| | | | | | | | | | | | | Problem: When calling setpos() with a buffer argument it often is ignored. (Matthew Malcomson) Solution: Make the buffer argument work for all marks local to a buffer. (neovim vim/vim#5713) Add more tests. https://github.com/vim/vim/commit/f13e00b2cf381e13fd327b5387a5bd6f004ac2a3
generated by cgit (git 2.34.1) at 2025-06-24 14:07:08 +0000