aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
| * vim-patch:8.1.2028: options test script does not workJan Edmund Lazo2019-09-14
| | | | | | | | | | | | Problem: Options test script does not work. Solution: Use optiondefs.h for input. https://github.com/vim/vim/commit/d9b0d83b13d2691e4544709abd87eac004715175
| * vim-patch:8.1.0289: cursor moves to wrong column after quickfix jumpJan Edmund Lazo2019-09-14
| | | | | | | | | | | | Problem: Cursor moves to wrong column after quickfix jump. Solution: Set the curswant flag. (Andy Massimino, closes vim/vim#3331) https://github.com/vim/vim/commit/2dfcef4c08a3371e2126504bea00b274f937a840
* | autocmds: TermEnter, TermLeave #8550Usama Hameed2019-09-14
|/ | | fix #8428
* vim-patch:8.1.2023: no test for synIDattr() returning "strikethrough" (#11018)Daniel Hahler2019-09-14
| | | | | Problem: No test for synIDattr() returning "strikethrough". Solution: Extend the synIDattr() test. (Jaskaran Singh, closes vim/vim#4929) https://github.com/vim/vim/commit/dcb2b9cb085288d2a2e4cc31abc591ade04e782e
* lintJustin M. Keyes2019-09-13
|
* getdigits: introduce `strict`, `def` parametersJustin M. Keyes2019-09-13
| | | | | | | | | | | | Problem: During a refactor long ago, we changed the `getdigits_*` familiy of functions to abort on overflow. But this is often wrong, because many of these codepaths are handling user input. Solution: Decide at each call-site whether to use "strict" mode. fix #5555
* rename: getdigits_safe => try_getdigitsJustin M. Keyes2019-09-13
|
* vim-patch:8.1.0719: too many #ifdefs [ci skip] #11016Jan Edmund Lazo2019-09-13
| | | | | Problem: Too many #ifdefs. Solution: Always build with the +visualextra feature. https://github.com/vim/vim/commit/870ba5f6dce974b6c1c47bf9d3b20db805d10b36
* vim-patch:8.1.2026: possibly using uninitialized memory #11013Jan Edmund Lazo2019-09-13
| | | | | Problem: Possibly using uninitialized memory. Solution: Check if "dict" is NULL. (closes vim/vim#4925) https://github.com/vim/vim/commit/dbec74907eb614517bcf27116d5aad32e087f241
* startup: fail if --embed with -es/-Es #10753glacambre2019-09-13
| | | | Closes https://github.com/neovim/neovim/issues/10031
* syntax, TUI: support "strikethrough"Jaskaran Singh2019-09-13
| | | | | | fix #3436 Includes: vim-patch:8.0.1038: strike-through text not supported
* vim-patch:8.1.0267: no good check if restoring quickfix list workedJan Edmund Lazo2019-09-13
| | | | | | Problem: No good check if restoring quickfix list worked. Solution: Let qf_restore_list() return OK/FAIL. (Yegappan Lakshmanan) https://github.com/vim/vim/commit/90f1e2b7bcf56112e1535b693acf131727179a6e
* vim-patch:8.1.0261: Coverity complains about a negative array indexJan Edmund Lazo2019-09-13
| | | | | | Problem: Coverity complains about a negative array index. Solution: When qf_id2nr() cannot find the list then don't set qf_curlist. https://github.com/vim/vim/commit/38efd1d17a6e6aa2add71efdf2cde4a788e5f5e5
* vim-patch:8.1.0259: no test for fixed quickfix issueJan Edmund Lazo2019-09-13
| | | | | | Problem: No test for fixed quickfix issue. Solution: Add a test. Clean up the code a bit. (Yegappan Lakshmanan) https://github.com/vim/vim/commit/3f347e4716c44cf6458be407e712e3d708d82580
* vim-patch:8.1.0248: duplicated quickfix codeJan Edmund Lazo2019-09-13
| | | | | | Problem: duplicated quickfix code. Solution: Move the code to a function. https://github.com/vim/vim/commit/8d8a65e389cef318ae661ff0fe7b1b00fd7cb25f
* vim-patch:8.0.1772: quickfix: mixup of FALSE and FAIL, returning -1Jan Edmund Lazo2019-09-13
| | | | | | Problem: Quickfix: mixup of FALSE and FAIL, returning -1. Solution: Use FAIL and INVALID_QFIDX. (Yegappan Lakshmanan) https://github.com/vim/vim/commit/29ce409bfca52bb8a07e2975d06fd788458e9861
* UIEnter/UILeave: fire for embedder UI, builtin TUIJustin M. Keyes2019-09-12
| | | | | | | | | Before this, --embed UIs (without --headless) would not trigger UIEnter. For TUI, maybe UIEnter isn't useful, but: - It is less "surprising"/special. - Makes documentation simpler. - When TUI becomes a coprocess, it will happen anyway.
* rename: UIAttach/UIDetach => UIEnter/UILeaveJustin M. Keyes2019-09-12
| | | | | "enter"/"leave" is more conventional for Vim events, and "attach"/"detach" distinction does not gain much.
* API/nvim_list_uis(): include "chan" field for TUIJustin M. Keyes2019-09-12
| | | | | Even though it's always zero currently, it's less confusing if all UIs have the same fields.
* UIAttach, UIDetachJustin M. Keyes2019-09-12
| | | | | doc: ginit.vim, gvimrc fix #3656
* UIAttach, UIDetachRui Abreu Ferreira2019-09-12
|
* lintJan Edmund Lazo2019-09-12
|
* fixup! cursor_shape: check if modep is nonnullJan Edmund Lazo2019-09-11
|
* Remove excess <stdint.h>Jan Edmund Lazo2019-09-11
|
* rename: SplitEvent => MulticastEvent #10989Justin M. Keyes2019-09-11
| | | | | "Multicast" is perhaps a more conventional name for the concept. "One-shot" is the conventional name for how the event is (currently) scheduled.
* eval: wait(): always spin up dummy-timer #10990Justin M. Keyes2019-09-11
| | | | This avoids getting "stuck". If user actually _wants_ to get stuck forever, they could use `:sleep` or specify a really big `interval`.
* Merge #10995 'paste: fix paste in terminal mode'Justin M. Keyes2019-09-11
|\
| * paste: fix paste in terminal modeBjörn Linse2019-09-11
|/
* docJustin M. Keyes2019-09-11
| | | | | fix #10127 fix #5972
* doc: nvim_ui_pum_set_height [ci skip]Daniel Hahler2019-09-10
|
* spell: assert nonull pointersJan Edmund Lazo2019-09-10
|
* cursor_shape: check if modep is nonnullJan Edmund Lazo2019-09-10
|
* regexp: assert nonnull pointer for regnext()Jan Edmund Lazo2019-09-10
|
* quickfix: fix pvs/v547 warningJan Edmund Lazo2019-09-10
|
* terminal: fix rgb rendering of palette colorsBjörn Linse2019-09-10
| | | | | | | | | | simplify handling of default colors nvim is always true color internally, remove ui_rgb_attached() check. Fix "runtime termguicolors" test. The test actually reflected broken behavior in (parent) nvim: nvim_ui_set_option("rgb", true) was not respected by existing :terminal instances, so all 16-palette colors became dark blue.
* lint / test groupingDaniel Hahler2019-09-10
|
* Changes for new VTermColor structPaul "LeoNerd" Evans2019-09-10
|
* vim-patch:8.0.1309: cannot use 'balloonexpr' in a terminal #10983Jan Edmund Lazo2019-09-09
| | | | | | | | (Port some refactoring, but ignore "balloon" changes.) Problem: Cannot use 'balloonexpr' in a terminal. Solution: Add 'balloonevalterm' and add code to handle mouse movements in a terminal. Initial implementation for Unix with GUI. https://github.com/vim/vim/commit/51b0f3701ecb440aa72ab6017c1df6940c0e0f6f
* vim-patch:8.0.0941: existing color schemes don't like StatusLineTermJan Edmund Lazo2019-09-09
| | | | | | | Problem: Existing color schemes don't work well with StatusLineTerm. Solution: Don't use "reverse", use fg and bg colors. Also add StatusLineTermNC. https://github.com/vim/vim/commit/05fbfdcda48a564e7a778c67251f732481f3ceaa
* vim-patch:8.0.0937: user highlight groups not adjusted for terminalJan Edmund Lazo2019-09-09
| | | | | | Problem: User highlight groups are not adjusted for StatusLineTerm. Solution: Combine attributes like for StatusLineNC. https://github.com/vim/vim/commit/bce4f62d3043f04fe29f3fef2b927b2268b15255
* Merge #10546 'doc'Justin M. Keyes2019-09-09
|\
| * doc/API/lua: detaching Lua buffer callbacksBjörn Linse2019-09-09
| |
| * doc: |api-fast| [ci skip]Justin M. Keyes2019-09-09
| |
| * docJustin M. Keyes2019-09-09
| |
* | provider: has("python3_dynamic") et al. #10980Justin M. Keyes2019-09-09
| | | | | | | | | | | | | | | | | | | | | | Vim added more flags for testing yet more dimensions of its Python situation. Handle those in eval_has_provider(). vim-patch:8.0.1436: not enough information about what Python version may work Problem: Not enough information about what Python version may work. Solution: Add "python_compiled", "python3_compiled", "python_dynamic" and "python3_dynamic" values for has(). ref: https://github.com/neovim/neovim/pull/10942#issuecomment-529479500
* | version.c: update [ci skip] #10961Marvim the Paranoid Android2019-09-09
|/ | | | | | | | | | | | | | | | | | | vim-patch:8.1.1680: the command table is not well aligned vim-patch:8.1.1994: MS-Windows: cannot build with eval but without cscope vim-patch:8.1.2002: version number 2000 missing vim-patch:8.1.2003: MS-Windows: code page 65001 is not recognized vim-patch:8.1.2006: build failure with huge features but without channel feature vim-patch:8.1.2015: terminal altscreen test still fails sometimes vim-patch:8.1.2016: terminal altscreen test now fails on MS-Windows `beval` patches are N/A now. See https://github.com/neovim/neovim/pull/10942#issuecomment-528029830 vim-patch:8.0.1366: https://github.com/vim/vim/commit/1ad022a9b81d7829d5dc98cf5b8d0ee410558040 vim-patch:8.1.0444: unnecessary check for NULL pointer vim-patch:8.1.0652: freeing memory for balloon eval too early vim-patch:8.1.1302: v:beval_text is not tested in Visual mode vim-patch:8.1.1648: MS-Windows: build error with normal feaures vim-patch:8.1.1650: warning for using uninitialized variable vim-patch:8.1.1654: GUI: screen updates from 'balloonexpr' are not displayed vim-patch:8.1.1708: Coverity warns for using uninitialized variable
* paste: fix normal-mode paste by different approach #10976Justin M. Keyes2019-09-09
| | | | | | | | Forcing insert-mode after the first paste-chunk seems to work, as an alternative to a9e2bae0eb69 (insert-before-cursor). NB: Dot-repeat needs to match the original action. Since a9e2bae0eb69 changed paste to insert-before-cursor, dot-repeat must also. But that makes dot-repeat unpleasant/unusual.
* vim-patch:8.1.1197: when starting with multiple tabs file messages is confusingJan Edmund Lazo2019-09-08
| | | | | | Problem: When starting with multiple tabs file messages is confusing. Solution: Set 'shortmess' when loading the other tabs. (Christian Brabandt) https://github.com/vim/vim/commit/c75e81262347e47a69faabd72caf89fec3f06e8f
* paste: insert before cursor alwaysJustin M. Keyes2019-09-08
| | | | | | | | | Inserting "after" the cursor in Normal-mode, for big paste-streams, is not reliable: sometimes the text "after" the cursor ends up in the middle of the pasted text. Maybe the cursor position is not updated? To avoid weird behavior, always paste "before". Maybe nvim_put() or vim.paste() can be fixed more properly later.
* paste: do not clobber msg area for small pastesJustin M. Keyes2019-09-08
|
generated by cgit (git 2.34.1) at 2025-07-23 05:52:28 +0000