aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* | | CI/AppVeyor: install "pynvim" python package #9371Justin M. Keyes2018-12-16
|/ /
* | Merge #9367 'vim-patch:8.1.{585,588}'Justin M. Keyes2018-12-15
|\ \
| * | vim-patch:8.1.0588: cannot define a sign with space in the textJan Edmund Lazo2018-12-14
| | | | | | | | | | | | | | | | | | Problem: Cannot define a sign with space in the text. Solution: Allow for escaping characters. (Ben Jackson, closes vim/vim#2967) https://github.com/vim/vim/commit/06b056e110005ce0dd97b8c6333405afd06c36fc
| * | vim-patch:8.1.0585: undo test may fail on MS-WindowsJan Edmund Lazo2018-12-14
| | | | | | | | | | | | | | | | | | Problem: Undo test may fail on MS-Windows. Solution: Also handle lower case drive letters. https://github.com/vim/vim/commit/56242f2b08737677812513c447955579a19aa620
* | | Merge pull request #9368 from bfredl/doublewrapBjörn Linse2018-12-15
|\ \ \ | |/ / |/| | TUI: handle wrap of doublewidth chars correctly
| * | TUI: handle wrap of doublewidth chars correctlyBjörn Linse2018-12-15
| | |
* | | TUI: Konsole 18.07.70 supports DECSCUSR (#9364)Justin M. Keyes2018-12-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ref https://github.com/KDE/konsole/commit/b0d3d83eca4f523a9e4acd3989da6be96033536a KONSOLE_VERSION is exported as a numeric string (after removing the dots from the version string). ref #8300 closes #6778 closes #6798
* | | Merge pull request #9362 from bfredl/macnumlocaleBjörn Linse2018-12-13
|\ \ \ | |/ / |/| | os/lang: use the correct LC_NUMERIC also for OS X
| * | os/lang: use the correct LC_NUMERIC also for OS XBjörn Linse2018-12-13
|/ /
* | Merge #9348 from janlazo/vim-8.0.1748Justin M. Keyes2018-12-13
|\ \ | | | | | | vim-patch:8.0.1748
| * | ex_docmd: '/' is not a path for Cmdline* eventsJan Edmund Lazo2018-12-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | Code from https://github.com/neovim/neovim/pull/9348#issuecomment-446416118 autocmd_fname_full was removed in https://github.com/neovim/neovim/commit/82cd0be2eaf71c0476e15c66ba3e83c76896d407 but Vim uses this hack for <afile> on CmdlineEnter and related events in vim-patch:8.0.1748. Port the hack by not treating "/" as a path for <afile> on these events.
| * | vim-patch:8.0.1748: CmdlineEnter command uses backslash instead of slashJan Edmund Lazo2018-12-12
| | | | | | | | | | | | | | | | | | Problem: CmdlineEnter command uses backslash instead of slash. Solution: Don't treat the character as a file name. (closes vim/vim#2837) https://github.com/vim/vim/commit/a4baf5b32519855bb176a7aa0e9397c137ca890a
* | | Merge #9355 from mhinz/ruby-provider-pathJustin M. Keyes2018-12-13
|\ \ \ | |/ / |/| | provider: make :ruby provider check use same code path as :python
| * | test: :ruby reports E319 if provider is missingMarco Hinz2018-12-12
| | |
| * | provider: make :ruby provider check use same code path as :pythonMarco Hinz2018-12-12
|/ / | | | | | | | | | | | | Prior to this change, the provider check for ruby was special-cased and now it returns E319, like :python etc. References #9354
* | Merge pull request #7946 from bfredl/vim-8.0.1445Björn Linse2018-12-12
|\ \ | | | | | | implement CmdlineChanged: vim-patch:8.0.1445 + nvim specific v:event stuff
| * | cmdline: support v:event in CmdlineChangedBjörn Linse2018-12-12
| | |
| * | vim-patch:8.0.1445: cannot act on edits in the command lineBjörn Linse2018-12-12
|/ / | | | | | | | | | | | | | | Problem: Cannot act on edits in the command line. Solution: Add the CmdlineChanged autocommand event. (xtal8, closes vim/vim#2603, closes vim/vim#2524) https://github.com/vim/vim/commit/153b704e20f9c269450a7d3ea8cafcf942579ab7
* | Merge #9354 from justinmk/provider-E319Justin M. Keyes2018-12-12
|\ \ | | | | | | provider: repurpose E319
| * | provider: repurpose E319Justin M. Keyes2018-12-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | In Vim (and some vestigial parts of Nvim) E319 was a placeholder for ex_ni commands, i.e. commands that are only available in certain builds of Vim. That is obviously counter to Nvim's goals: all Nvim commands are available on all platforms and build types (the remaining ex_ni commands are actually just missing providers). We need an error id for "missing provider", so it makes sense to use E319 for that purpose. ref #9344 ref #3577
| * | ex_cmds: Remove various "not implemented" commandsJustin M. Keyes2018-12-11
|/ / | | | | | | | | Commands related to Netbeans, Sun Workshop, and GUI shims, were intentionally removed and will not be implemented.
* | provider: improve error message (#9344)Marco Hinz2018-12-11
| | | | | | | | | | | | | | | | | | | | | | Executing `:python`, and similar commands that rely on `eval_call_provider()`, while the accompanying provider it not available, leads to this error message: E117: Unknown function: provider#python#Call This doesn't say much to a user. Since we introduced `:checkhealth` for this very reason, we now point to it for further diagnosis. Fixes #3577
* | TUI: alacritty supports set_cursor_color #9353Patrice Peterson2018-12-11
| | | | | | | | | | | | | | Feature was added in: https://github.com/jwilm/alacritty/pull/757 closes #9353
* | 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
generated by cgit (git 2.34.1) at 2025-06-25 23:22:58 +0000