aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
| * | | 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
* | | | 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
* | | screen: add missing status redraw when redraw_later(CLEAR) was usedBjörn Linse2018-12-05
| | |
* | | 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
* | | 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().
* | | Merge #9291 'vim-patch:8.1.{550,551}'Justin M. Keyes2018-12-02
|\ \ \
| * | | 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
* | | | VimL/confirm(): Show dialog even if :silentJustin M. Keyes2018-12-01
| | | | | | | | | | | | | | | | | | | | closes #8788 related #9034
* | | | insert: make <cmd> mapping work in completion (CTRL-X) modeBjörn Linse2018-12-01
|/ / /
* | | vim-patch:8.1.0553: it is not easy to edit a script that was sourced (#9298)Jan Edmund Lazo2018-12-01
| | | | | | | | | | | | | | | | | | Problem: It is not easy to edit a script that was sourced. Solution: Add a count to ":scriptnames", so that ":script 40" edits the script with script ID 40. https://github.com/vim/vim/commit/07dc18ffa4e7ed202f219fe2fd3d6f58246f71f9
* | | test/macOS: adjust time-sensitive testsJustin M. Keyes2018-11-30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From test_timers.vim: Found errors in Test_paused(): First run: function RunTheTest[35]..Test_paused line 20: Expected range 0 - 100, but got 123 Second run: function RunTheTest[35]..Test_paused line 20: Expected range 0 - 100, but got 106 previously: #9220 - Timer tests are less reliable on Travis CI macOS 10.12/10.13. ref #6829 ref e39dade80b02 ref de13113dc16e ref https://github.com/neovim/neovim/pull/9095#issuecomment-429603452 > We don't guarantee that a X ms timer is triggered during Y ms sleep > for any X<Y, though I would expect the load to be really bad for this > to happen with X=10ms, Y=40ms.
* | | highlight: Fix missing .rgb_sp_color in initializers (#9287)Justin M. Keyes2018-11-30
| | | | | | | | | | | | | | | | | | | | | terminal_get_line_attributes() had this bug for a long time, though it likely had no effect visible to users. ref #9028 ref 60f845ca55a1
* | | test: adjust time-sensitive testsJustin M. Keyes2018-11-30
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | From test_alot.vim: Found errors in Test_lambda_with_timer(): First run: function RunTheTest[35]..Test_lambda_with_timer line 19: Expected True but got 0 Second run: function RunTheTest[35]..Test_lambda_with_timer line 19: Expected True but got 0 previously: #9220 - Timer tests are less reliable on Travis CI macOS 10.12/10.13. ref #6829 ref e39dade80b02 ref de13113dc16e ref https://github.com/neovim/neovim/pull/9095#issuecomment-429603452 > We don't guarantee that a X ms timer is triggered during Y ms sleep > for any X<Y, though I would expect the load to be really bad for this > to happen with X=10ms, Y=40ms. - Call test_garbagecollect_now(), as Vim does.
* | | API: rename nvim_buf_clear_highlight to nvim_buf_clear_namespaceBjörn Linse2018-11-29
| | | | | | | | | | | | | | | We want a single function to clear all namespaced buffer objects. This will later include extmarks.
* | | vim-patch:8.1.0098: segfault when pattern with \z() is very slow (#9283)Justin M. Keyes2018-11-29
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Segfault when pattern with \z() is very slow. Solution: Check for NULL regprog. Add "nfa_fail" to test_override() to be able to test this. Fix that 'searchhl' resets called_emsg. https://github.com/vim/vim/commit/bcf9442307075bac40d44328c8bf7ea21857b138 closes #8788
* | | TUI: set_underline_color: only support colon form #9279Daniel Hahler2018-11-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes https://github.com/neovim/neovim/issues/9270 --- Background info per egmontkob: https://github.com/neovim/neovim/issues/9270#issuecomment-441979176 For undercurl, the newly invented escape sequence is `4:3` strictly with a colon, as with a semicolon it means single underlined and italic. For colored underline, the newly invented escape sequence `58:...` is meant to follow the pattern of `38` and `48`. [ITU T.416](https://www.itu.int/rec/T-REC-T.416-199303-I/en) § 13.1.8 clearly specifies the colon only as the separator (and the well-known ECMA-48 § 8.3.117 just points to this standard). Using semicolon instead was/is a frequent misinterpretation of this standard, and is commonly used in the wild – for 38 and 48. More and more emulators are catching up and beginning to support colon, in addition to semicolon. Semicolon is pretty fragile; in case an emulator doesn't recognize a sequence (let's say doesn't recognize the new extension of `58`), subsequent numbers are interpreted as other attributes. E.g. if 256-color mode is chosen then the next numeric parameter is `5` which turns on blinking. So, luckily, the standard is the technically better solution, the frequent practice of using semicolons is technically the worse. Therefore the direction we should be going is clear. I believe it's a fair requirement for anyone adopting colored underline to support colons too, and it's a reasonable move from applications to slightly push the world forward, force developers to catch up with the recent changes, that is: 1) recognize and at least ignore colon-delimited parameters even if they aren't supported, 2) recognize and support colon wherever they support the nonstandard semicolon instead. Should you come across any terminal emulator that supports 58 with semicolons but not with colons, I think the cleanest you can do is report a bug against them and ignore the problem; they should fix it. It's yet another common misunderstanding that the truecolor syntax is `38`/`48`/`58` followed by `:2:rrr:ggg:bbb`. The wording of T.416 is terrible, but if you read carefully, there's another parameter of color-space-id preceding the three color channels. Assuming you don't care about color-space-id, the syntax is `38`/`48`/`58` followed by `:2::rrr:ggg:bbb` and of course the trailing `m`. This is only for true-color, the 256-color format doesn't have such a parameter, it's `38`/`48`/`58` followed by `:5:index` and the final `m`.
* | | Merge #9221 from justinmk/docJustin M. Keyes2018-11-28
|\ \ \
| * | | lint: src/.clang-formatJustin M. Keyes2018-11-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Move to top level so that clang-format -style=file can find it regardless of current directory.
| * | | docJustin M. Keyes2018-11-28
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | - develop.txt is for design/guidelines; architecture/concepts should live elsewhere (currently src/nvim/README.md) - move dev-jargon to intro.txt - replace https://neovim.io/community (deprecated) with https://neovim.io/#chat - <Cmd> avoids CmdlineEnter/Leave https://github.com/vim/vim/issues/2889
* | | | diff/highlight: Fix GUI highlight for low-priority CursorLine (#9281)Justin M. Keyes2018-11-28
|/ / / | | | | | | | | | ref #9028 ref 0653ed63a508
* | | fix wrong winnr in getwininfoSha Liu2018-11-27
| | |
* | | preserve_exit: Ignore SIGHUPJustin M. Keyes2018-11-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | closes #9274 ref #9028 If stdin closed then read_error_exit calls preserve_exit. Handling SIGHUP during preserve_exit would cause a premature teardown, and conflicts with e.g. ui_bridge_stop which waits for TUI to teardown. Vim ignores SIGHUP in its prepare_to_exit and getout_preserve_modified routines: /* Ignore SIGHUP, because a dropped connection causes a read error, which * makes Vim exit and then handling SIGHUP causes various reentrance * problems. */ signal(SIGHUP, SIG_IGN);
* | | diff/highlight: Show underline for low-priority CursorLineJustin M. Keyes2018-11-27
| | |
* | | diff/highlight: do not overlay low-priority CursorLineJustin M. Keyes2018-11-27
| | | | | | | | | | | | ref #6380
* | | refactor: Rename get_term_attr_entryJustin M. Keyes2018-11-27
| | | | | | | | | | | | | | | Rename get_term_attr_entry to hl_get_term_attr, similar to hl_get_syn_attr, hl_get_ui_attr.
* | | version.c: update [ci skip] (#9171)Marvim the Paranoid Android2018-11-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | vim-patch:8.0.0350: not enough test coverage for Perl vim-patch:8.0.1135: W_WINCOL() is always the same vim-patch:8.0.1280: Python None cannot be converted to a Vim type vim-patch:8.0.1308: the "Reading from stdin" message may be undesired vim-patch:8.0.1338: USE_IM_CONTROL is confusing and incomplete vim-patch:8.0.1343: MS-Windows: does not show colored emojis vim-patch:8.0.1350: cannot build with +eval and -multi_byte vim-patch:8.0.1829: MS-Windows: script for vimdiff can't handle ! chars vim-patch:8.0.1849: compiler warning for unused arguments, missing prototype vim-patch:8.1.0001: the netrw plugin does not work vim-patch:8.1.0006: syn_id2cterm_bg() may be undefined vim-patch:8.1.0012: misplaced #endif vim-patch:8.1.0021: clang warns for undefined behavior vim-patch:8.1.0041: attribute "width" missing from python window attribute list vim-patch:8.1.0051: MS-Windows: missing #endif vim-patch:8.1.0063: Mac: NSStringPboardType is deprecated vim-patch:8.1.0075: no Vim logo in README file vim-patch:8.1.0077: header of README file is not nice vim-patch:8.1.0079: superfluous space in messages vim-patch:8.1.0102: cannot build without syntax highlighting vim-patch:8.1.0104: can't build without the +eval feature vim-patch:8.1.0109: new po makefile missing from distribution vim-patch:8.1.0117: URL in install program still points to SourceForge vim-patch:8.1.0122: translators don't always understand the maintainer message vim-patch:8.1.0123: MS-Windows: colors are wrong after setting 'notgc' vim-patch:8.1.0124: has('vcon') returns true even for non-win32 terminal vim-patch:8.1.0127: build failure when disabling the session feature vim-patch:8.1.0128: building with MinGW does not work out-of-the-box vim-patch:8.1.0129: still some xterm-like terminals get a stray "p" vim-patch:8.1.0137: CI does not run with TCL vim-patch:8.1.0142: xterm and vt320 builtin termcap missing keypad keys vim-patch:8.1.0147: compiler warning when building with Python 3.7 vim-patch:8.1.0148: memory leak when using :tcl expr command vim-patch:8.1.0150: insufficient test coverage for Tcl vim-patch:8.1.0152: cannot easily run individual tests on MS-Windows vim-patch:8.1.0153: build with SHADOWDIR fails vim-patch:8.1.0155: evim.man missing from the distribution vim-patch:8.1.0157: old iTerm2 is not recognized, resulting in stray output vim-patch:8.1.0160: no Danish manual translations vim-patch:8.1.0162: Danish and German man pages are not installed vim-patch:8.1.0163: insufficient testing for Tcl vim-patch:8.1.0173: compiler warning on MS-Windows vim-patch:8.1.0176: overlapping string argument for strcpy() vim-patch:8.1.0178: warning for passing pointer to non-pointer argument vim-patch:8.1.0179: redundant condition for boundary check vim-patch:8.1.0180: static analysis errors in Lua interface vim-patch:8.1.0183: Lua API changed, breaking the build vim-patch:8.1.0185: running tests writes lua.vim even though it is not used vim-patch:8.1.0190: Perl refcounts are wrong vim-patch:8.1.0191: Perl test fails in 24 line terminal vim-patch:8.1.0197: Windows GUI: title for search/replace is wrong vim-patch:8.1.0201: newer Python uses "importlib" instead of "imp" vim-patch:8.1.0202: :version always shows +packages vim-patch:8.1.0203: building with Perl 5.28 fails on Windows vim-patch:8.1.0207: need many menu translation files to cover regions vim-patch:8.1.0209: stderr output from Ruby messes up display vim-patch:8.1.0215: no error if configure --with-x cannot configure X vim-patch:8.1.0217: compiler warning for variable set but not used vim-patch:8.1.0222: errors are reported for "make install" vim-patch:8.1.0232: Ruby error does not include backtrace vim-patch:8.1.0234: incorrect reference counting in Perl interface vim-patch:8.1.0236: Ruby build fails when ruby_intern is missing vim-patch:8.1.0237: Ruby on Cygwin doesn't always work vim-patch:8.1.0239: now Ruby build fails on other systems vim-patch:8.1.0246: build failure without the +eval feature vim-patch:8.1.0247: Python: error message for failing import is incorrect vim-patch:8.1.0249: GTK: when screen DPI changes Vim does not handle it vim-patch:8.1.0250: MS-Windows using VTP: windows size change incorrect vim-patch:8.1.0254: cannot build on MS-Windows; unused macro HAVE_HANDLE_DROP vim-patch:8.1.0260: no LGTM logo in README file vim-patch:8.1.0287: MAX is not defined everywhere vim-patch:8.1.0292: MS-Windows: the text "self-installing" confuses some users vim-patch:8.1.0301: GTK: input method popup displayed on wrong screen. vim-patch:8.1.0305: missing support for Lua 5.4 32 bits on Unix vim-patch:8.1.0319: bzero() function prototype doesn't work for Android vim-patch:8.1.0332: get Gdk-Critical error on first balloon show vim-patch:8.1.0346: building with Aap is outdated and unused vim-patch:8.1.0348: on Travis the slowest build is run last vim-patch:8.1.0357: instructions for tests are outdated vim-patch:8.1.0368: GTK code has too many #ifdefs and GTK 2.10 building fails vim-patch:8.1.0379: build dependencies are incomplete vim-patch:8.1.0380: "make proto" doesn't work well vim-patch:8.1.0383: missing source file rename vim-patch:8.1.0385: Coveralls badge doesn't update vim-patch:8.1.0386: cannot test with non-default option value vim-patch:8.1.0388: Coverity complains about possible NULL pointer use vim-patch:8.1.0390: scrollbars are not tested vim-patch:8.1.0391: building in a shadow directory fails vim-patch:8.1.0403: header file missing from distribution vim-patch:8.1.0405: too many #ifdefs for GTK vim-patch:8.1.0408: MSVC: cannot use the "x64" native compiler option vim-patch:8.1.0411: renamed file missing from distribution vim-patch:8.1.0412: cannot build with GTK 2.4 vim-patch:8.1.0413: test output is duplicated or missing vim-patch:8.1.0415: not actually using 16 colors with vtp vim-patch:8.1.0418: MS-Windows: cannot separate Lua include and library dirs vim-patch:8.1.0419: Cygwin: running cproto fails with -O2 vim-patch:8.1.0420: generating vim.lib when using ActivePerl 5.20.3 or later vim-patch:8.1.0421: MS-Windows: Ruby path is wrong for Ruby 1.9 and later vim-patch:8.1.0422: cannot create map file with MinGW vim-patch:8.1.0427: MS-Windows GUI: using invalid encoded file name vim-patch:8.1.0441: build failure without command line history vim-patch:8.1.0467: cannot build with Mac OS X 10.5 vim-patch:8.1.0472: dosinst command has a few flaws vim-patch:8.1.0474: directory where if_perl.c is written is inconsistent vim-patch:8.1.0477: tiny build fails vim-patch:8.1.0478: cannot build with perl using MinGW vim-patch:8.1.0480: MinGW build file uses different -I flags than MVC vim-patch:8.1.0482: MinGW "make clean" deletes all .exe files vim-patch:8.1.0483: MinGW does not build tee.exe vim-patch:8.1.0490: MS-Windows: doesn't handle missing glibwinpthread-1.dll vim-patch:8.1.0492: "Edit with existing Vim" list can get long vim-patch:8.1.0500: cleaning up in src/tee may not always work vim-patch:8.1.0521: cannot build with +eval but without +quickfix vim-patch:8.1.0534: MS-Windows installer uses different $HOME than Vim vim-patch:8.1.0541: help message in dosinst.c is outdated vim-patch:8.1.0485: term_start() does not check if directory is accessible #9204
* | | API: Implement nvim_win_set_buf() #9100Justin M. Keyes2018-11-25
| | | | | | | | | | | | closes #9100
* | | Remove extraneous parens to silence -Wparentheses-equalityJames McCoy2018-11-24
| | | | | | | | | | | | | | | | | | | | | In file included from ../src/nvim/eval/encode.c:974: ../src/nvim/eval/typval_encode.c.h:390:40: error: equality comparison with extraneous parentheses [-Werror,-Wparentheses-equality] do { if ((tv->vval.v_special == kSpecialVarTrue)) { msgpack_pack_true(packer); } else { msgpack_pack_false(packer); } } while (0); ~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
* | | xenial: fix clang error messagesMarco Hinz2018-11-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | * Remove FUNC_ATTR_NONNULL_ALL from function without pointer arguments. Otherwise the ASAN build would complain: error: 'nonnull' attribute applied to function with no pointer arguments [-Werror,-Wignored-attributes] static void do_autocmd_focusgained(_Bool gained) __attribute__((nonnull));
* | | api: implement object namespacesBjörn Linse2018-11-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | Namespaces is a lightweight concept that should be used to group objects for purposes of bulk operations and introspection. This is initially used for highlights and virtual text in buffers, and is planned to also be used for extended marks. There is no plan use them for privileges or isolation, neither to introduce nanespace-level options.
generated by cgit (git 2.34.1) at 2025-07-12 16:22:58 +0000