aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* | macOS: infer primary language if $LANG is empty #9345Marco Hinz2018-12-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | The macOS preferences have a section called `Language & Region`. There is always at least one language defined, the primary language. CFLocaleCopyPreferredLanguages() returns the languages defined in that section, the first element being the primary language. Use the primary language in case CFLocaleCopyCurrent() returns NULL. In the case that the above fallback does not work either, which is very unlikely, log the error and continue with an empty $LANG. References #9134
* | Merge pull request #9351 from bfredl/clear_attrBjörn Linse2018-12-11
|\ \ | | | | | | TUI: don't use BCE with attributes affecting background
| * | TUI: don't use BCE with attributes affecting backgroundBjörn Linse2018-12-11
| | |
* | | vim-patch:8.1.0574: 'commentstring', fold marker in C (#9339)Jan Edmund Lazo2018-12-10
| | | | | | | | | | | | | | | | | | Problem: 'commentstring' not used when adding fold marker in C. Solution: Require white space before middle comment part. (mostly by Hirohito Higashi) https://github.com/vim/vim/commit/4af7259b2b35e85c590d54908fcd248d2c733be8
* | | Merge #9306 'vim-patch: integrate xdiff library'Justin M. Keyes2018-12-09
|\ \ \ | |/ / |/| | | | | | | | | | | closes #1466 closes #1007 closes #1391
| * | vim-patch:8.1.0562: parsing of 'diffopt' is slightly wrongAnatolii Sakhnik2018-12-09
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Parsing of 'diffopt' is slightly wrong. Solution: Fix the parsing and add a test. (Jason Franklin, Christian Brabandt) https://github.com/vim/vim/commit/b6fc72851c45a36a370f9516c68508e47b41c4c1
| * | vim-patch:8.1.0513: no error for set diffopt+=algorithm:Anatolii Sakhnik2018-12-09
| | | | | | | | | | | | | | | | | | | | | Problem: No error for set diffopt+=algorithm:. Solution: Check for missing argument. (Hirohito Higashi, closes #3598) https://github.com/vim/vim/commit/d0721058f494143186f66a60151c9634031a8c96
| * | vim-patch:8.1.0502: internal diff fails when diffing a context diffAnatolii Sakhnik2018-12-09
| | | | | | | | | | | | | | | | | | | | | Problem: Internal diff fails when diffing a context diff. (Hirohito Higashi) Solution: Only use callback calls with one line. (closes #3581) https://github.com/vim/vim/commit/f080d70a82f3a4477f346d9efcdfaec1bc1e1d58
| * | vim-patch:8.1.0497: :%diffput changes order of linesAnatolii Sakhnik2018-12-09
| | | | | | | | | | | | | | | | | | | | | Problem: :%diffput changes order of lines. (Markus Braun) Solution: Do adjust marks when using internal diff. https://github.com/vim/vim/commit/5f57bdcab77bc417ae0357fe8ad6c7259b6d25df
| * | vim-patch:8.1.0458: ml_get error and crash when using "do"Anatolii Sakhnik2018-12-09
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Ml_get error and crash when using "do". Solution: Adjust cursor position also when diffupdate is not needed. (Hirohito Higashi) https://github.com/vim/vim/commit/df77cef92ec034796723ffa3adb12e8b46daa98e
| * | vim-patch:8.1.0402: the DiffUpdate event isn't triggered for :diffputAnatolii Sakhnik2018-12-09
| | | | | | | | | | | | | | | | | | | | | Problem: The DiffUpdate event isn't triggered for :diffput. Solution: Also trigger DiffUpdate for :diffget and :diffput. https://github.com/vim/vim/commit/198fa066b2ec011e91012c1a3d85a73df7b93f31
| * | vim-patch:8.1.0400: using freed memory with :diffgetAnatolii Sakhnik2018-12-09
| | | | | | | | | | | | | | | | | | | | | Problem: Using freed memory with :diffget. Solution: Skip ex_diffupdate() while updating diffs. (closes #3442) https://github.com/vim/vim/commit/d2b58c0a2c665075a8cfef57db6e1b37d4523e02
| * | vim-patch:8.1.0397: no event triggered after updating diffsAnatolii Sakhnik2018-12-09
| | | | | | | | | | | | | | | | | | | | | Problem: No event triggered after updating diffs. Solution: Add the DiffUpdated event. https://github.com/vim/vim/commit/e8fa05b5bc2d6d76bf5af50176a63655d00d1110
| * | vim-patch:8.1.0395: compiler warning on 64-bit MS-WindowsAnatolii Sakhnik2018-12-09
| | | | | | | | | | | | | | | | | | | | | Problem: Compiler warning on 64-bit MS-Windows. Solution: Add type cast. (Mike Williams) https://github.com/vim/vim/commit/6e272acc82af900318017061f923e7f66dc7ee7a
| * | vim-patch:8.1.0394: diffs are not always updated correctlyAnatolii Sakhnik2018-12-09
| | | | | | | | | | | | | | | | | | | | | Problem: Diffs are not always updated correctly. Solution: When using internal diff update for any changes properly. https://github.com/vim/vim/commit/e3521d9cbb786806eaff106707851d37d2c0ecef
| * | vim-patch:8.1.0393: not all white space difference options availableAnatolii Sakhnik2018-12-09
| | | | | | | | | | | | | | | | | | | | | Problem: Not all white space difference options available. Solution: Add "iblank", "iwhiteall" and "iwhiteeol" to 'diffopt'. https://github.com/vim/vim/commit/785fc6567f572b8caefbc89ec29bbd8b801464ae
| * | vim-patch:8.1.0375: cannot use diff mode with Cygwin diff.exeAnatolii Sakhnik2018-12-09
| | | | | | | | | | | | | | | | | | | | | Problem: Cannot use diff mode with Cygwin diff.exe. (Igor Forca) Solution: Skip over unrecognized lines in the diff output. https://github.com/vim/vim/commit/3b8defd0a52fc1276816608e7bb24b628ab14c2e
| * | vim-patch:8.1.0360: using an external diff program is slow and inflexibleAnatolii Sakhnik2018-12-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Using an external diff program is slow and inflexible. Solution: Include the xdiff library. (Christian Brabandt) Use it by default. https://github.com/vim/vim/commit/e828b7621cf9065a3582be0c4dd1e0e846e335bf vim-patch:8.1.0360 vim-patch:8.1.0364 vim-patch:8.1.0366 vim-patch:8.1.0370 vim-patch:8.1.0377 vim-patch:8.1.0378 vim-patch:8.1.0381 vim-patch:8.1.0396 vim-patch:8.1.0432
| * | Calm down the clinterAnatolii Sakhnik2018-12-09
|/ /
* | doc (#9288)Justin M. Keyes2018-12-09
| | | | | | | | | | - misc - doc: `:help config`. closes #9329 - cleanup test/README.md
* | vim-patch:8.1.0570: 'commentstring' not used when adding fold marker (#9331)Jan Edmund Lazo2018-12-08
| | | | | | | | | | | | Problem: 'commentstring' not used when adding fold marker. (Maxim Kim) Solution: Only use empty 'comments' middle when leader is empty. (Christian Brabandt, closes vim/vim#3670) https://github.com/vim/vim/commit/539328197c51c1586cbbb6b6be3db3c412249b49
* | Merge #9322 from janlazo/vim-8.1.0563Justin M. Keyes2018-12-08
|\ \ | | | | | | vim-patch:8.1.{563,564}
| * | vim-patch:8.1.0564: setting v:errors to wrong type still possibleJan Edmund Lazo2018-12-06
| | | | | | | | | | | | | | | | | | Problem: Setting v:errors to wrong type still possible. Solution: Return after giving an error message. (Christian Brabandt) https://github.com/vim/vim/commit/88b53fd0521d1e62df17a8a1f2181425e9d4854c
| * | vim-patch:8.1.0563: setting v:errors to a string give confusing errorJan Edmund Lazo2018-12-06
| | | | | | | | | | | | | | | | | | | | | Problem: Setting v:errors to a string give confusing error. (Christian Brabandt) Solution: Change internal error into normal error message. https://github.com/vim/vim/commit/74ea88c170f65afa50b2b97e37806d13b4e24cd7
* | | runtime/syntax: Fix highlighting of augroup contents (#9328)Justin M. Keyes2018-12-08
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Comparing `vimCommand` from Vim's runtime/syntax/vim.vim, one can see that "augroup" and similar commands are conspicuously missing. They are handled specially (`vimAugroupKey`, `vimAutoCmd`). Excluding them from the generated `vimCommand` keyword list, fixes their highlighting. closes #9327
* | | CI/Travis: install gperf using package manager (#9325)Justin M. Keyes2018-12-07
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Install gperf using package manager instead of building it from source. When building/installing gperf from source, its install step requires `texi2pdf` which randomly goes missing on Travis: cd doc; /usr/bin/make install make[1]: Entering directory '/home/travis/nvim-deps/build/src/gperf/doc' cd . && rm -f gperf.aux gperf.toc gperf.cp gperf.fn gperf.ky gperf.pg gperf.tp gperf.vr gperf.log gperf.cps cd . && texi2pdf gperf.texi /bin/sh: 1: texi2pdf: not found It's nice to test the "bundled" deps on Travis, but that gets enough exercise on Windows and macOS, which are the platforms that actually need "bundled" gperf.
* | | Merge pull request #9324 from bfredl/virtfixBjörn Linse2018-12-07
|\ \ \ | |/ / |/| | api: make nvim_set_virtual_text use correct namespace counter
| * | api: make nvim_buf_set_virtual_text use correct namespace counterBjörn Linse2018-12-07
|/ /
* | vim-patch:8.0.1425: execute() does not work in completion of user command ↵Jan Edmund Lazo2018-12-06
| | | | | | | | | | | | | | (#9317) Problem: execute() does not work in completion of user command. (thinca) Solution: Switch off redir_off and restore it. (Ozaki Kiichi, closes vim/vim#2492) https://github.com/vim/vim/commit/2095148277cf1c4e7b3bbaf4e34812b7cfe3011b
* | Merge pull request #9315 from bfredl/clear_statusBjörn Linse2018-12-05
|\ \ | | | | | | screen: add missing status redraw when <c-l> was used
| * | screen: add missing status redraw when redraw_later(CLEAR) was usedBjörn Linse2018-12-05
|/ /
* | provider/lang: expand() g:foo_host_prog (#9312)Justin M. Keyes2018-12-05
| | | | | | | | | | | | | | | | | | | | Before this commit, if user does this: let g:node_host_prog = '~/.nvm/versions/node/v11.3.0/bin/neovim-node-host' the "~/" is not expanded to user's home directory. `:help g:ruby_host_prog` suggests a path with "~/" so technically we already claimed to support this. closes https://github.com/neovim/node-client/issues/102
* | vim-patch:8.1.0559: command line completion not sufficiently tested (#9310)Justin M. Keyes2018-12-04
|\ \ | | | | | | | | | | | | Problem: Command line completion not sufficiently tested. Solution: Add more tests. (Dominique Pelle, closes vim/vim#3622) https://github.com/vim/vim/commit/b513d3079bbe3f59a1f1a3d6931939a76cd7e54a
| * | vim-patch:8.1.0559: command line completion not sufficiently testedJan Edmund Lazo2018-12-03
| | | | | | | | | | | | | | | | | | Problem: Command line completion not sufficiently tested. Solution: Add more tests. (Dominique Pelle, closes vim/vim#3622) https://github.com/vim/vim/commit/b513d3079bbe3f59a1f1a3d6931939a76cd7e54a
* | | clipboard: Revert unused check #9309@equalsraf2018-12-04
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | PR #9304 added support for functions in clipboard providers. As part of the PR I meant to move two checks in the provider code out of an if statement into separate statements and adding additional checks for g:clipboard attributes - as it turns out the code is wrong and it does not implement additional checks while it adds two conditions that make very little sense type(g:clipboard['copy']) #isnot# v:t_func what would make sense would be something along the lines of type(g:clipboard['copy']['+']) #isnot# v:t_func but might not be what we want either, so I'm reverting this.
* | Merge pull request #9307 from jamessan/codecov-thresholdJames McCoy2018-12-03
|\ \ | | | | | | codecov: Tolerate a 1% drop in coverage for a PR
| * | codecov: Tolerate a 1% drop in coverage for a PRJames McCoy2018-12-02
| | |
* | | Merge pull request #9300 from bfredl/asyncerrBjörn Linse2018-12-03
|\ \ \ | |/ / |/| | rpc: fix invalid responses, turn errors from async calls into notifications
| * | RPC: turn errors from async calls into notificationsBjörn Linse2018-12-03
|/ / | | | | | | | | Previously, nvim sent a response with invalid request id (UINT64_MAX). In functionaltests, catch unexpected error notifications in after_each().
* | clipboard: Support custom VimL functions #9304Rui Abreu Ferreira2018-12-03
| | | | | | | | | | | | | | | | | | | | | | | | Up to now g:clipboard["copy"] only supported string values invoked as system commands. This commit enables the use of VimL functions instead. The function signatures are the same as in provider/clipboard.vim. A clipboard provider is expected to store and return a list of lines (i.e. the text) and a register type (as seen in setreg()). cache_enabled is ignored if "copy" is provided by a VimL function.
* | Merge #9291 'vim-patch:8.1.{550,551}'Justin M. Keyes2018-12-02
|\ \
| * | fixup: 30 col resize to scroll debugJan Edmund Lazo2018-12-01
| | |
| * | fixup: 35 col resize to scroll screenJan Edmund Lazo2018-12-01
| | |
| * | functionaltests: vim-patch:8.1.{550,551} fixJan Edmund Lazo2018-11-30
| | |
| * | vim-patch:8.1.0551: expression evaluation may repeat an error messageJan Edmund Lazo2018-11-30
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Expression evaluation may repeat an error message. (Jason Franklin) Solution: Check for the value of did_emsg when giving an error for the :execute command. https://github.com/vim/vim/commit/8ff5af9544a2abc3d344bba017ef96682e098d9d
| * | vim-patch:8.1.0550: expression evaluation may repeat an error messageJan Edmund Lazo2018-11-30
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Expression evaluation may repeat an error message. (Jason Franklin) Solution: Increment did_emsg and check for the value when giving an error for the echo command. https://github.com/vim/vim/commit/76a6345433bc2a600689397fb28165a2e5793720
* | | Merge pull request #9303 from jamessan/cmp-0075James McCoy2018-12-01
|\ \ \ | | | | | | | | Unset CMAKE_REQUIRED_* after they're done being used
| * | | cmake: Update comment on why CMP0059 is still set to OLDJames McCoy2018-12-01
| | | |
| * | | Unset CMAKE_REQUIRED_* after they're done being usedJames McCoy2018-12-01
|/ / / | | | | | | | | | | | | | | | | | | As of CMake 3.12, check_include_files() also link the check executable against the libraries listed in CMAKE_REQUIRED_LIBRARIES. Therefore we should unset the CMAKE_REQUIRED_* variables after each respective use to avoid them unnecessarily bleeding into other checks.
* | | clipboard: Prefer xclip (#9302)Justin M. Keyes2018-12-01
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The order was swapped in #4150 to prefer `xsel` but there wasn't a clear explanation. Meanwhile, `xsel` has been neglected upstream. Let's trying preferring `xclip` again, we've had a few reports of problems with `xsel`. closes #7237 ref #5853 ref #7449