aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* vim-patch:8.1.1325: cannot build with +eval but without +channel and +timersJan Edmund Lazo2019-05-18
| | | | | | | Problem: Cannot build with +eval but without +channel and +timers. (John Marriott) Solution: Adjust #ifdef for get_callback(). https://github.com/vim/vim/commit/97b0075b0d733cc58c29247b09e7887b9991d7bf
* vim-patch:8.1.1345: stuck in sandbox with ":s/../\=Function/gn"Jan Edmund Lazo2019-05-18
| | | | | | Problem: Stuck in sandbox with ":s/../\=Function/gn". Solution: Don't skip over code to restore sandbox. (Christian Brabandt) https://github.com/vim/vim/commit/6349e9411fd17f80c7aff9c678a8800647d34cfa
* kbtree.h: assert valid range #10022Justin M. Keyes2019-05-18
| | | ref #10012
* Merge pull request #10025 from bfredl/bufhl_fixesBjörn Linse2019-05-18
|\ | | | | kbtree: pointer UB and unitialized value fixes
| * kbtree: pointer UB and unitialized value fixesBjörn Linse2019-05-18
|/ | | | | | | - don't underflow itr->p pointer (C standard only allows one past the end, not one before the beginning) - make sure itr->p->i is always initialized (even when not used) - don't rely on `NULL < &object` (likely UB)
* vim-patch:8.1.1338: fix hang when concealing wide char #10023Jan Edmund Lazo2019-05-18
| | | | | | | Problem: Hang when concealing the '>' shown for a wide char that doesn't fit in the last cell. Solution: Put back the pointer when the '>' is not going to be displayed. (closes vim/vim#4377) https://github.com/vim/vim/commit/0ebe12be86d9f79bfa833306a0302a68a0f4fc30
* runtime/termdebug.vim #10015Kwon-Young Choi2019-05-16
| | | | | | | | | | | * bugfix * use NormalFloat for floating window background * use floating window by default * correctly use nvim_open_win() * use nvim_win_set_option to set window local option * use nvim_buf_set_option for buffer options * renamed augroup to nvim_termdebug_close_hover to be consistent with nvim_terminal_... augroup
* runtime/termdebug.vim #8364Kwon-Young Choi2019-05-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | * commit 36257d0f97b396467bef7a5937befd894fb23e31 Author: Kwon-Young Choi <kwon-young.choi@hotmail.fr> Date: Sat May 5 16:57:45 2018 +0200 Port of the termdebug.vim plugin to neovim terminal feature. For neovim compatibility, The vim specific calls were replaced with neovim specific calls: term_start -> term_open term_sendkeys -> jobsend term_getline -> getbufline job_info && term_getjob -> using linux command ps to get the tty fix1: forgot to port EndDebug callback to neovim fix2: use nvim_get_chan_info to get pty of job remove the use of communication buffer by using jobstart instead of termopen fix3: get gdbbuf using nvim_get_chan_info * cleaned up if has('nvim') to remove vim support. added neovim floating window support for expression evaluation * improvred documentation, cleaned up vim menu code, fixed bug when floating window feature is not available
* Merge pull request #9883 from bfredl/termredrawBjörn Linse2019-05-14
|\ | | | | make terminal state redraw like any other state
| * ui/terminal: make terminal state redraw like any other stateBjörn Linse2019-05-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously, ordinary redraws were missing from terminal mode. Instead, there was an async callback that invoked update_screen() on terminal data regardless of mode (as if :redraw! was invoked by a timer). This created some issues: - async changes to an unrelated ordinary buffer were not always redrawn in terminal mode - screen cursor position was not properly updated in terminal mode (partial fix, will be properly fixed in a follow up PR) - ad-hoc logic was needed for interaction with special states such as inccommand or horizontal wildmenu. Instead redraw terminal mode just like any other state. This disables forced redraws in cmdline mode, which were inconisent which async changes to normal buffers (which are not redrawn in cmdline mode).
* | Merge pull request #9985 from bfredl/shenanigansBjörn Linse2019-05-13
|\ \ | | | | | | Fix aucmd_win issues: crashes and redrawing errors.
| * | autocmd: fixes and tests for autocmd window issuesBjörn Linse2019-05-13
| | | | | | | | | | | | | | | | | | - redraw! in an invisible buffer rendered the screen unusable. - storing the autocmd window handle and using it in API function could lead to crashes. Unregister the handle when the window is not active.
* | | Merge #10003 from justinmk/api-keymapJustin M. Keyes2019-05-13
|\ \ \ | |/ / |/| | API/nvim_set_keymap: minor cleanup
| * | API/nvim_set_keymap: remove mode-shortname aliasesJustin M. Keyes2019-05-12
| | | | | | | | | | | | | | | Reduce the API surface-area a bit. No need to have aliases for a mode. ref #9924
| * | API/nvim_set_keymap: minor cleanupJustin M. Keyes2019-05-12
|/ / | | | | | | ref #9924
* | API: nvim_set_keymap, nvim_del_keymap #9924Yilin Yang2019-05-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | closes #9136 - Treat empty {rhs} like <Nop> - getchar.c: Pull "repl. MapArg termcodes" into func The "preprocessing code" surrounding the replace_termcodes calls needs to invoke replace_termcodes, and also check if RHS is equal to "<Nop>". To reduce code duplication, factor this out into a helper function. Also add an rhs_is_noop flag to MapArguments; buf_do_map_explicit expects an empty {rhs} string for "<Nop>", but also needs to distinguish that from something like ":map lhs<cr>" where no {rhs} was provided. - getchar.c: Use allocated buffer for rhs in MapArgs Since the MAXMAPLEN limit does not apply to the RHS of a mapping (or else an RHS that calls a really long autoload function from a plugin would be incorrectly rejected as being too long), use an allocated buffer for RHS rather than a static buffer of length MAXMAPLEN + 1. - Mappings LHS and RHS can contain literal space characters, newlines, etc. - getchar.c: replace_termcodes in str_to_mapargs It makes sense to do this; str_to_mapargs is, intuitively, supposed to take a "raw" command string and parse it into a totally "do_map-ready" struct. - api/vim.c: Update lhs, rhs len after replace_termcodes Fixes a bug in which replace_termcodes changes the length of lhs or rhs, but the later search through the mappings/abbreviations hashtables still uses the old length value. This would cause the search to fail erroneously and throw 'E31: No such mapping' errors or 'E24: No such abbreviation' errors. - getchar: Create new map_arguments struct So that a string of map arguments can be parsed into a more useful, more portable data structure. - getchar.c: Add buf_do_map function Exactly the same as the old do_map, but replace the hardcoded references to the global `buf_T* curbuf` with a function parameter so that we can invoke it from nvim_buf_set_keymap. - Remove gettext calls in do_map error handling
* | test/channels_spec: cleanupJustin M. Keyes2019-05-12
| | | | | | | | | | - Remove stray print() - Use uname() instead of system('uname')
* | Merge #9993 from justinmk/ui-message-kindsJustin M. Keyes2019-05-12
|\ \ | | | | | | UI/ext_messages: learn more message kinds
| * | docJustin M. Keyes2019-05-11
| | |
| * | UI/ext_messages: learn more message kindsJustin M. Keyes2019-05-11
|/ / | | | | | | ref #6201
* | vim-patch:8.1.0543: fix memory leak #10001Jan Edmund Lazo2019-05-11
| | | | | | | | | | | | Problem: Coverity warns for leaking memory and using wrong struct. Solution: Free pointer when allocation fails. Change "boff" to "loff". (closes vim/vim#3634) https://github.com/vim/vim/commit/4e303c8ba8dcd0566a1ad7c82ff18eb016eea335
* | Merge #9994 from janlazo/vim-8.1.1306Justin M. Keyes2019-05-11
|\ \ | | | | | | vim-patch:8.1.{1306,1312}
| * | vim-patch:8.1.1312: Coverity warning for using uninitialized variableJan Edmund Lazo2019-05-09
| | | | | | | | | | | | | | | | | | Problem: Coverity warning for using uninitialized variable. Solution: Clear exarg_T. https://github.com/vim/vim/commit/4ca41534b726c4116d2e430e877e34146b4d4831
| * | vim-patch:8.1.1306: Borland support is outdated and doesn't workJan Edmund Lazo2019-05-09
|/ / | | | | | | | | | | | | Problem: Borland support is outdated and doesn't work. Solution: Remove Borland support, there are other (free) compilers available. (Thomas Dziedzic, Ken Takata, closes vim/vim#4364) https://github.com/vim/vim/commit/eae1b91fea74842000fc055afc74fe2e7934c6ee
* | runtime/tutor [ci skip] #9990juliancoffee2019-05-09
| |
* | Merge #9992 from justinmk/ui-upgradeJustin M. Keyes2019-05-09
|\ \ | | | | | | UI/nvim_ui_attach(): add "override" option
| * | UI/nvim_ui_attach(): add `override` optionJustin M. Keyes2019-05-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Before now, Nvim always degrades UI capabilities to the lowest-common denominator. For example, if any connected UI has `ext_messages=false` then `ext_messages=true` requested by any other connected UI is ignored. Now `nvim_ui_attach()` supports `override=true`, which flips the behavior: if any UI requests an `ext_*` UI capability then the capability is enabled (and the legacy behavior is disabled). Legacy UIs will be broken while a `override=true` UI is connected, but it's useful for debugging: you can type into the TUI and observe the UI events from another connected (UI) client. And the legacy UI will "recover" after the `override=true` UI disconnects. Example using pynvim: >>> n.ui_attach(2048, 2048, rgb=True, override=True, ext_multigrid=True, ext_messages=True, ext_popupmenu=True) >>> while True: n.next_message();
* | | Merge pull request #9987 from janlazo/vim-8.1.0865Justin M. Keyes2019-05-09
|\ \ \ | |/ / |/| | vim-patch:8.1.{865,1299}
| * | vim-patch:8.1.1299: "extends" from 'listchars' is used when 'list' is offJan Edmund Lazo2019-05-08
| | | | | | | | | | | | | | | | | | | | | | | | Problem: "extends" from 'listchars' is used when 'list' is off. (Hiroyuki Yoshinaga) Solution: Only use the "extends" character when 'list' is on. (Hirohito Higashi, closes vim/vim#4360) https://github.com/vim/vim/commit/a5c6a0b6c71ae11078cbf6f5e18ce49a0468a117
| * | vim-patch:8.1.0865: when 'listchars' only contains "nbsp:X" it does not workJan Edmund Lazo2019-05-08
|/ / | | | | | | | | | | Problem: When 'listchars' only contains "nbsp:X" it does not work. Solution: Set extra_check when lcs_nbsp is set. (Ralf Schandl, closes vim/vim#3889) https://github.com/vim/vim/commit/895d966e341c187ffcf9da88dba193cbfcebf000
* | vim-patch:8.1.1205: BufReadPre may move the cursor #9980Justin M. Keyes2019-05-08
| | | | | | | | | | | | | | Problem: A BufReadPre autocommand may cause the cursor to move. Solution: Restore the cursor position after executing the autocommand, unless the autocommand moved it. (Christian Brabandt, closes vim/vim#4302, closes vim/vim#4294) https://github.com/vim/vim/commit/a68e59590905da9b4448ff1fcac929ad1a18da9e
* | vim-patch:8.1.1293: MSVC files are no longer useful #9982Jan Edmund Lazo2019-05-08
| | | | | | | | | | | | Problem: MSVC files are no longer useful for debugging. Newer Visual Studio versions cannot read them. Solution: Delete the files. (Ken Takata, closes vim/vim#4357) https://github.com/vim/vim/commit/fda9784dc9596e1e36f840bbf1935a4c4b502bd9
* | Merge #9979 from janlazo/vim-8.0.0876Justin M. Keyes2019-05-07
|\ \ | | | | | | vim-patch:8.0.{876,1144},8.1.0133
| * | vim-patch:8.0.1144: using wrong #ifdef for computing lengthJan Edmund Lazo2019-05-07
| | | | | | | | | | | | | | | | | | | | | Problem: Using wrong #ifdef for computing length. Solution: use BACKSLASH_IN_FILENAME instead of COLON_IN_FILENAME. (Yasuhiro Matsomoto, closes vim/vim#2153) https://github.com/vim/vim/commit/0b05e491b473dbf39cd9f519030bf6363c272300
| * | lintJan Edmund Lazo2019-05-07
| | |
| * | vim-patch:8.1.0133: tagfiles() can have duplicate entriesJan Edmund Lazo2019-05-07
| | | | | | | | | | | | | | | | | | | | | Problem: tagfiles() can have duplicate entries. Solution: Simplify the filename to make checking for duplicates work better. Add a test. (Dominique Pelle, closes vim/vim#2979) https://github.com/vim/vim/commit/46577b5e5445c4aaa1e7ae1764373d11dae71663
| * | vim-patch:8.0.0876: backslashes and wildcards in backticks don't workJan Edmund Lazo2019-05-07
| | | | | | | | | | | | | | | | | | | | | Problem: MS-Windows: Backslashes and wildcards in backticks don't work. Solution: Do not handle backslashes inside backticks in the wrong place. (Yasuhiro Matsumoto, closes vim/vim#1942) https://github.com/vim/vim/commit/39d21e3c30f3391f3b27f5ddb7e1ad411bdb8f2e
* | | API: fix cursor position when lines are added #9961hashinclude2019-05-07
|/ / | | | | | | Restore code removed in #9674.
* | Merge #9978 from janlazo/vim-8.1.1285Justin M. Keyes2019-05-07
|\ \ | | | | | | vim-patch:8.1.{1284,1285,1286}
| * | fixup! vim-patch:8.0.1782: no simple way to label quickfix entriesJan Edmund Lazo2019-05-06
| | |
| * | vim-patch:8.1.1284: detecting *.tmpl as htmlcheetah is outdatedJan Edmund Lazo2019-05-06
| | | | | | | | | | | | | | | | | | Problem: Detecting *.tmpl as htmlcheetah is outdated. Solution: Use the generic name "template". (closes vim/vim#4348) https://github.com/vim/vim/commit/d1362211291c85d29609baab65abc764b1aec169
| * | vim-patch:8.1.1286: running tests leaves XTest_tabpage_cmdheight file behindJan Edmund Lazo2019-05-06
| | | | | | | | | | | | | | | | | | Problem: Running tests leaves XTest_tabpage_cmdheight file behind. Solution: Delete the right file. (closes vim/vim#4350) https://github.com/vim/vim/commit/4fa06870e5d347c30fe55290dab87e494c8aa06a
| * | vim-patch:8.1.1285: test17 is old styleJan Edmund Lazo2019-05-06
|/ / | | | | | | | | | | Problem: Test17 is old style. Solution: Turn into new style test. (Yegappan Lakshmanan, closes vim/vim#4347) https://github.com/vim/vim/commit/f0ab01f6d868164ed0bb247b6f7b152e6929ef18
* | Merge #9977 from justinmk/pvsJustin M. Keyes2019-05-06
|\ \
| * | lintJustin M. Keyes2019-05-06
| | |
| * | PVS/V781: "maxlen" variable checked after useJustin M. Keyes2019-05-06
| | | | | | | | | | | | False positive.
| * | PVS/V547: Expression is always trueJustin M. Keyes2019-05-06
| | | | | | | | | | | | | | | Since 67bac681ea6b (see msg_multiline_attr()) msg_clr_eos() is always called.
| * | PVS/V547: Expression is always falseJustin M. Keyes2019-05-06
| | |
| * | PVS/V547: Expression is always falseJustin M. Keyes2019-05-06
| | |
| * | PVS/V571: condition was already verifiedJustin M. Keyes2019-05-06
| | |
generated by cgit (git 2.34.1) at 2025-06-25 15:03:27 +0000