aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* vim-patch:8.0.0579: duplicate test case for quickfixJames McCoy2017-12-18
| | | | | | | Problem: Duplicate test case for quickfix. Solution: Remove the function. (Yegappan Lakshmanan) https://github.com/vim/vim/commit/9b77016545d5ef1a1f4a90c9bb4b7a6693af8918
* vim-patch:8.0.0574: get only one quickfix list after :caddbufJames McCoy2017-12-18
| | | | | | | Problem: Get only one quickfix list after :caddbuf. Solution: Reset qf_multiline. (Yegappan Lakshmanan) https://github.com/vim/vim/commit/99895eac1cf71be43ece7e14b50e206e041fbe9f
* vim-patch:8.0.0565: using freed memory in :caddbufJames McCoy2017-12-18
| | | | | | | | Problem: Using freed memory in :caddbuf after clearing quickfix list. (Dominique Pelle) Solution: Set qf_last to NULL. https://github.com/vim/vim/commit/31bdd13c335533c749993b57dcd980a87373139e
* Merge pull request #7744 from jamessan/vim-8.0.0517James McCoy2017-12-18
|\ | | | | [RFC] vim-patch:8.0.0517,8.0.0536,8.0.0584
| * vim-patch:8.0.0584: memory leak when executing quickfix testsJames McCoy2017-12-18
| | | | | | | | | | | | | | Problem: Memory leak when executing quickfix tests. Solution: Free the list reference. (Yegappan Lakshmanan) https://github.com/vim/vim/commit/d788f6fe89c77262c474de323f5dab6d1c814e27
| * vim-patch:8.0.0536: quickfix window not updated when freeing quickfix stackJames McCoy2017-12-18
| | | | | | | | | | | | | | Problem: Quickfix window not updated when freeing quickfix stack. Solution: Update the quickfix window. (Yegappan Lakshmanan) https://github.com/vim/vim/commit/69f40be64555d50f603c6f22722cf762aaa6bbc1
| * vim-patch:8.0.0517: there is no way to remove quickfix listsJames McCoy2017-12-18
| | | | | | | | | | | | | | | | Problem: There is no way to remove quickfix lists (for testing). Solution: Add the 'f' action to setqflist(). Add tests. (Yegappan Lakshmanan) https://github.com/vim/vim/commit/b6fa30ccc39cdb7f1d07b99fe2f4c6b61671dac2
* | Updating to latest UNIBILIUM (#7745)Issam Maghni2017-12-18
|/ | | Update to unibilium 1.2.1
* Merge pull request #7740 from jamessan/vim-8.0.0404James McCoy2017-12-18
|\ | | | | [RFC] vim-patch:8.0.0404,8.0.0484
| * vim-patch:8.0.0484: :lhelpgrep does not fail after a successful oneJames McCoy2017-12-17
| | | | | | | | | | | | | | | | | | Problem: Using :lhelpgrep with an argument that should fail does not produce an error if the previous :helpgrep worked. Solution: Use another way to detect that autocommands made the quickfix info invalid. (Yegappan Lakshmanan) https://github.com/vim/vim/commit/ee85df37634dfb0c40ae5de0b4f246aef460b392
| * vim-patch:8.0.0404: not enough testing for quickfixJames McCoy2017-12-17
|/ | | | | | | Problem: Not enough testing for quickfix. Solution: Add some more tests. (Yegappan Lakshmanan) https://github.com/vim/vim/commit/391b1dd040af204b150d43c5a1c97477ee450a28
* Merge pull request #7736 from jamessan/vim-8.0.0420James McCoy2017-12-17
|\ | | | | [RFC] vim-patch:8.0.0420: text garbled when the system encoding differs from 'encoding'
| * lintJames McCoy2017-12-17
| |
| * vim-patch:8.0.0420: text garbled when the system encoding differs from ↵James McCoy2017-12-17
| | | | | | | | | | | | | | | | | | | | 'encoding' Problem: When running :make the output may be in the system encoding, different from 'encoding'. Solution: Add the 'makeencoding' option. (Ken Takata) https://github.com/vim/vim/commit/2c7292dc5bbf155fe2192d417363b8c085759cad
* | provider/nodejs: more robust version-check (#7738)Justin M. Keyes2017-12-18
| |
* | Merge #7739 'ASAN/LeakSanitizer: ignore loop_schedule_deferred()'Justin M. Keyes2017-12-18
|\ \
| * | ASAN/LeakSanitizer: ignore loop_schedule_deferred()Justin M. Keyes2017-12-17
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | clang ASAN/LeakSanitizer error (observed in #7706): ==21832==ERROR: LeakSanitizer: detected memory leaks Direct leak of 56 byte(s) in 1 object(s) allocated from: 0 0x511b26 in malloc (/home/travis/build/neovim/neovim/build/bin/nvim+0x511b26) 1 0x1009a84 in try_malloc /home/travis/build/neovim/neovim/src/nvim/memory.c:87:15 2 0x1009c44 in xmalloc /home/travis/build/neovim/neovim/src/nvim/memory.c:121:15 3 0xaa8c36 in loop_schedule_deferred /home/travis/build/neovim/neovim/src/nvim/event/loop.c:89:19 4 0x190856a in tui_main /home/travis/build/neovim/neovim/src/nvim/tui/tui.c:367:5 5 0x1963d61 in ui_thread_run /home/travis/build/neovim/neovim/src/nvim/ui_bridge.c:106:3 6 0x2b5d4190d183 in start_thread /build/eglibc-SvCtMH/eglibc-2.19/nptl/pthread_create.c:312 Possible explanation: During exit, `Loop.thread_events` may not get flushed, so `loop_deferred_event()` is never called. We could instead try to unwind `Loop.thread_events` during teardown, but it seems lower-risk to just tell ASAN to ignore it. Valgrind does not complain: $ while :; do { 2>valglog.txt valgrind ./build/bin/nvim -u NONE +q ; } ; if ! [ $? = 0 ] ; then break ; fi ; done
* | Merge pull request #7732 from jamessan/patch-summaryJames McCoy2017-12-17
|\ \ | | | | | | vim-patch.sh: Include upstream summary in commit message
| * | vim-patch.sh: Include upstream summary in commit messageJames McCoy2017-12-17
| | | | | | | | | | | | [ci skip]
* | | health.vim: mention g:ruby_host_prog #7737Alex Genco2017-12-17
| | |
* | | health.vim: Try `pyenv root` #7341quinoa422017-12-17
| |/ |/|
* | Merge #7706 'ci: nodejs acceptance-test'Justin M. Keyes2017-12-17
|\ \ | |/ |/|
| * provider/nodejs: check version in Detect()Justin M. Keyes2017-12-17
| |
| * health.vim: nodejs: skip if nodejs is too oldJustin M. Keyes2017-12-17
| |
| * test: remove inspect test; set NODE_PATH in nodejs_spec.luaJan Edmund Lazo2017-12-17
| | | | | | | | | | | | | | | | | | | | | | provider#node#can_inspect will fail on some systems because it is common to have old node versions in OS (any Linux OS that has LTS releases) and CI (Travis, Appveyor). NODE_PATH can be trivially set with VimL. Build scripts don't have to set it for the nodejs tests to work. NODE_PATH is optional to begin with and is used only as a workaround for the neovim node.js host.
| * ci: nodejs client acceptance-test #7706Jan Edmund Lazo2017-12-17
|/ | | | | | | | | | | | | | | | | | | | | | | | ci: install nodejs 8 in Appveyor, Travis provider: check node version for debug support Resolve https://github.com/neovim/neovim/pull/7577#issuecomment-350590592 for Unix. provider: test if nodejs in ci supports --inspect-brk nodejs host for neovim requires nodejs 6+ to work properly. nodejs 6.12+ or 7.6+ is required for debug support via `node --inspect-brk`. provider: run cli.js of nodejs host directly npm shims are useless because the user cannot set node to debug mode via --inspect-brk. This is problematic on Windows which use batchfiles and shell scripts to compensate for not supporting shebang. The patch uses `npm root -g` to get the absolute path of the global npm modules. If that fails, then the user did not install neovim npm package globally. Use that absolute path to find `neovim/bin/cli.js`, which is what the npm shim actually runs with node. glob() is for a simple file check in case bin/ is removed because the npm shims are ignored now.
* tui: rework deferred-termcodes ... againJustin M. Keyes2017-12-16
| | | | | | | | | | | | | | | | | | - Revert timer-based approach. - Instead, call loop_poll_events() with a timeout in an "active" loop, to infer that "TUI startup activity has mostly finished", but also to enforce a mininum time (100 ms) before emitting "enable focus reporting" termcode. (If TUI startup takes longer than that minimum time, it's probably a slow environment anyways.) - Tickle `main_loop` by sending a dummy event. Without this, the initial "focus-gained" response from the terminal may not get processed until the user hits a key. ref #7720 ref #7664 ref #7649 ref #7664 ref 27f9b1c7b029d8
* Merge pull request #7306 from DarkDeepBlue/vim-8.0.0074James McCoy2017-12-15
|\ | | | | vim-patch:8.0.0074
| * lintJames McCoy2017-12-15
| |
| * vim-patch:8.0.0074Michael Schupikov2017-12-15
|/ | | | | | | | | | Problem: Cannot make Vim fail on an internal error. Solution: Add IEMSG() and IEMSG2(). (Domenique Pelle) Avoid reporting an internal error without mentioning where. https://github.com/vim/vim/commit/95f096030ed1a8afea028f2ea295d6f6a70f466f Signed-off-by: Michael Schupikov <michael@schupikov.de>
* Merge #7720 'tui: rework deferred-termcodes implementation'Justin M. Keyes2017-12-14
|\
| * tui: defer termcodes using a timerJustin M. Keyes2017-12-13
| | | | | | | | | | | | | | | | | | | | | | | | | | With this implementation there is no "jank" during startup. Using the main_loop in any fashion is janky. Using only the TUI loop emits the termcodes too soon, or requires bad hacks like counting tui_flush invocations (9 seems to work). ref #7664 ref #7649 ref #7664 ref 27f9b1c7b029d8
| * tui: rework deferred-termcodes implementationJustin M. Keyes2017-12-13
| | | | | | | | | | | | | | | | | | | | Try another approach to defer the termcodes. Seems less janky, but still not perfect. ref #7664 ref #7649 ref #7664 ref 27f9b1c7b029d8
| * pty_process_unix: _exit() on execvp() failureJustin M. Keyes2017-12-13
| | | | | | | | | | Mostly cargo-culting based on a reading of the manpages, interwebs, and the Vim source.
* | typval_encode.c.h: avoid -Wnonnull-compare warning (#7712)Justin M. Keyes2017-12-13
|/ | | | | | | | | | | | | | | | | | | | | | | | * typval_encode.c.h: avoid -Wnonnull-compare warning closes #6847 The NULL check is needed because TYPVAL_ENCODE_CONV_EMPTY_DICT may be invoked with literal `NULL`. Warning occurs even for `Debug` build-type: neovim/src/nvim/eval/typval.c: In function ‘_typval_encode_nothing_convert_one_value’: neovim/src/nvim/eval/typval.c:1802:10: warning: nonnull argument ‘tv’ compared to NULL [-Wnonnull-compare] if (tv != NULL) { \ ^ ../src/nvim/eval/typval_encode.c.h:398:9: note: in expansion of macro ‘TYPVAL_ENCODE_CONV_EMPTY_DICT’ TYPVAL_ENCODE_CONV_EMPTY_DICT(tv, tv->vval.v_dict); ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~ gcc version: gcc (Ubuntu 6.3.0-12ubuntu2) 6.3.0 20170406 * fixup! typval_encode.c.h: avoid -Wnonnull-compare warning
* ui: forward relevant option updates to UIs (#7520)Björn Linse2017-12-12
| | | also make termguicolors mutable after startup
* Merge pull request #7718 from jamessan/disable-titleold-translationJames McCoy2017-12-11
|\ | | | | Disable translation of default 'titleold' value
| * Disable translation of default 'titleold' valueJames McCoy2017-12-11
|/ | | | | | It's an empty string, so there's no reason to try to translate it. Closes #7717
* Merge #7555 'vim-patch.sh, doc updates'Justin M. Keyes2017-12-11
|\
| * vim-patch.sh: remove version.c in generated patchJustin M. Keyes2017-12-11
| | | | | | | | | | Vim patch tracking is now driven completely by `vim-patch:xxx` tokens in the VCS logs. version.c will be auto-generated, if it is used at all.
| * vim-patch.sh: introduce `-L`Justin M. Keyes2017-12-11
| |
| * vim-patch: NAckelsel2017-12-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | vim-patch:8.0.0299 NA vim-patch:8.0.0309 NA vim-patch:8.0.0310 NA vim-patch:8.0.0215 NA Problem: When a Cscope line contains CTRL-L a NULL pointer may be used. (Coverity) Solution: Don't check for an emacs tag in a cscope line. https://github.com/vim/vim/commit/e362c3d2c34f2b7ff38b4c3d2a7ff127d2290e09 vim-patch:8.0.0244 NA Problem: When the user sets t_BE empty after startup to disable bracketed paste, this has no direct effect. Solution: When t_BE is made empty write t_BD. When t_BE is made non-empty write the new value. https://github.com/vim/vim/commit/d9c60648e50a82dcb85b8dffb47f6416c3d56972 Some patches were not properly marked in the commit logs. So they are marked here: vim-patch:8.0.1230 vim-patch:8.0.1229 vim-patch:8.0.0618 vim-patch:8.0.0104 vim-patch:8.0.0405 vim-patch:8.0.0400 vim-patch:8.0.0302 vim-patch:8.0.0288 vim-patch:8.0.0285 vim-patch:8.0.0284 vim-patch:8.0.0281 vim-patch:8.0.0279 vim-patch:8.0.0278 vim-patch:8.0.0277 vim-patch:8.0.0276 vim-patch:8.0.0273 vim-patch:8.0.0272 vim-patch:8.0.0271 vim-patch:8.0.0270 vim-patch:8.0.0269 vim-patch:8.0.0268 vim-patch:8.0.0267 vim-patch:8.0.0260 vim-patch:8.0.0257 vim-patch:8.0.0249 vim-patch:8.0.0248 vim-patch:8.0.0246 vim-patch:8.0.0244 vim-patch:8.0.0241 vim-patch:8.0.0240 vim-patch:8.0.0239 vim-patch:8.0.0232 vim-patch:8.0.0221 vim-patch:8.0.0217 vim-patch:8.0.0215 vim-patch:8.0.0213 vim-patch:8.0.0211 vim-patch:8.0.0203 vim-patch:8.0.0199 vim-patch:8.0.0193 vim-patch:8.0.0192 vim-patch:8.0.0191 vim-patch:8.0.0187 vim-patch:8.0.0183 vim-patch:8.0.0180 vim-patch:8.0.0173 vim-patch:8.0.0171 vim-patch:8.0.0170 vim-patch:8.0.0169 vim-patch:8.0.0166 vim-patch:8.0.0163 vim-patch:8.0.0162 vim-patch:8.0.0161 vim-patch:8.0.0152 vim-patch:8.0.0145 vim-patch:8.0.0144 vim-patch:8.0.0141 vim-patch:8.0.0139 vim-patch:8.0.0138 vim-patch:8.0.0130 vim-patch:8.0.0129 vim-patch:8.0.0123 vim-patch:8.0.0122 vim-patch:8.0.0120 vim-patch:8.0.0117 vim-patch:8.0.0115 vim-patch:8.0.0114 vim-patch:8.0.0113 vim-patch:8.0.0109 vim-patch:8.0.0108 vim-patch:8.0.0107 vim-patch:8.0.0105 vim-patch:8.0.0103 vim-patch:8.0.0098 vim-patch:8.0.0097 vim-patch:8.0.0095 vim-patch:8.0.0094 vim-patch:8.0.0093 vim-patch:8.0.0089 vim-patch:8.0.0087 vim-patch:8.0.0082 vim-patch:8.0.0080 vim-patch:8.0.0077 vim-patch:8.0.0076 vim-patch:8.0.0072 vim-patch:8.0.0071 vim-patch:8.0.0070 vim-patch:8.0.0067 vim-patch:8.0.0065 vim-patch:8.0.0063 vim-patch:8.0.0061 vim-patch:8.0.0059 vim-patch:8.0.0055 vim-patch:8.0.0054 vim-patch:8.0.0051 vim-patch:8.0.0050 vim-patch:8.0.0048 vim-patch:8.0.0045 vim-patch:8.0.0039 vim-patch:8.0.0036 vim-patch:8.0.0030 vim-patch:8.0.0029 vim-patch:8.0.0028 vim-patch:8.0.0027 vim-patch:8.0.0024 vim-patch:8.0.0022 vim-patch:8.0.0021 vim-patch:8.0.0018 vim-patch:8.0.0016 vim-patch:8.0.0015 vim-patch:8.0.0014 vim-patch:8.0.0013 vim-patch:8.0.0011 vim-patch:8.0.0010 vim-patch:8.0.0009 vim-patch:8.0.0007 vim-patch:8.0.0005
| * vim-patch.sh: always use git log, not version.cJustin M. Keyes2017-12-10
| |
| * docJustin M. Keyes2017-12-10
| | | | | | | | closes #7622
| * gen_api_vimdoc.py: require "nvim_" prefixJustin M. Keyes2017-12-10
| | | | | | | | | | Avoids doxygen bugs (things that aren't functions) and other noise (e.g. `remote_ui_disconnect()` was incorrectly included in api.txt).
| * doc: hack to avoid doxygen bugJustin M. Keyes2017-12-10
| | | | | | | | | | | | | | | | Use `@cond <something>` to obscure a section from doxygen. doxygen thinks kvec_withinit_t() is a function. That adds noise to the generated API documentation, and also prevents the following function from being noticed.
* | Merge pull request #7704 from jamessan/mac-lang-fixJames McCoy2017-12-10
|\ \ | |/ |/| mac: Set $LANG based on the system locale
| * mac: Set $LANG based on the system localeJames McCoy2017-12-10
| | | | | | | | | | | | | | | | | | Unix's typical locale-related environment variables aren't always set appropriately on a Mac. Instead of relying on them, query the locale information using Mac specific APIs and then set $LANG appropriately for the rest of nvim. Closes #5873
* | window.c: do BufEnter in correct window after closing help #7431glacambre2017-12-10
|/ | | | | | | | | | | | closes #7429 Problem: after a help window was closed, a window was selected and its autocommands triggered. After that, restore_snapshot was called and the focused window changed, confusing the user. Solution: Add function get_snapshot_focus() that returns the window that holds the cursor in a snapshot. Use this function in win_close to make sure the right window is selected before any autocommand is triggered.
* ci: run oldtests in Appveyor #7705Jan Edmund Lazo2017-12-10
|
generated by cgit (git 2.34.1) at 2025-06-11 00:20:09 +0000