aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Merge pull request #11025 from bfredl/doublescrollBjörn Linse2019-09-15
|\ | | | | compositor: avoid transmitting invalid lines on double scroll
| * compositor: avoid transmitting invalid lines on double scrollBjörn Linse2019-09-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This happens in an operation which both increases topline and also inserts new lines somewhere in the remaining are. So before drawing any line, win_update() is performing two grid_scroll operations. === A B C D E^ F === Consider that new line will be inserted after line E and screen also scrolled up to line C. First the topline will be adjusted (x is the scrolling region, ! invalid/empty space created by the scroll): === C x D x E^ x F x ! x ! x === and then space is inserted for the new line === C D E^ ! x F x ! x === The problem is that we are now assuming that any invalid area ! created by a scroll is filled with actual contents (by win_line etc) before it is scrolled again. But in this case the last invalid line ! gets scrolled. Ideally we should make win_update smarter and just scroll valid lines for the later scroll (it is just wasteful to scroll the larger area anyway), but for the 0.4 releasejust make the compositor ignore such an invalid line (as it will get overdrawn anyway later).
* | Merge pull request #11026 from janlazo/vim-8.1.0220Daniel Hahler2019-09-15
|\ \ | |/ |/| vim-patch:8.1.0220
| * test/old: detect user modules for python,rubyJan Edmund Lazo2019-09-15
| | | | | | | | | | | | | | | | | | Set the environment variables before changing $HOME so that python,ruby can find user modules not in $HOME. Reference: - https://github.com/neovim/neovim/commit/7be7ec98a22451ec75ce5eb9284fa1722b53c697 - https://github.com/neovim/neovim/issues/10270#issuecomment-531516948
| * vim-patch:8.1.0220: Ruby converts v:true and v:false to a numberJan Edmund Lazo2019-09-15
|/ | | | | | | | | Problem: Ruby converts v:true and v:false to a number. Solution: Use Qtrue and Qfalse instead. (Masataka Pocke Kuwabara, closes vim/vim#3259) https://github.com/vim/vim/commit/d84b26a03b13cd816d80ff32b61e8de740d499ce nvim does not support v:none.
* Merge #11021 from justinmk/ctx-rename-buflistJustin M. Keyes2019-09-14
|\ | | | | API: Context: "opts" param, et al.
| * Context: rename "buflist" => "bufs"Justin M. Keyes2019-09-14
| | | | | | | | | | Given the other type names "jumps", "vars", etc., the name "buflist" is somewhat unintuitive.
| * API: nvim_get_context: "opts" paramJustin M. Keyes2019-09-14
|/ | | | | Since the parameter is already non-primitive, make it an `opts` map instead of just a list, in case we want to extend it later.
* release.sh: bump nvim.appdata.xmlJustin M. Keyes2019-09-14
|
* Merge #11020 from janlazo/vim-8.1.0289Justin M. Keyes2019-09-14
|\ | | | | | | vim-patch:8.0.{1134,1148},8.1.{212,289,2028} fix #10270
| * test/old: skip python-bindeval testsJan Edmund Lazo2019-09-14
| |
| * vim-patch:8.1.0212: preferred cursor column not set in interfacesJan Edmund Lazo2019-09-14
| | | | | | | | | | | | | | | | | | | | Problem: Preferred cursor column not set in interfaces. Solution: Set w_set_curswant when setting the cursor. (David Hotham, closes vim/vim#3060) https://github.com/vim/vim/commit/53901442f37a59e5495165f91db5574c0b43ab04 This contains test_ruby changes only. test_python changes were ported before.
| * ci/travis: install pynvim outside of $HOMEJan Edmund Lazo2019-09-14
| | | | | | | | | | This runs the python tests on Travis. WIP: skip failing python tests
| * test/old: skip failing ruby testsJan Edmund Lazo2019-09-14
| | | | | | | | These tests didn't pass in https://github.com/neovim/neovim/pull/9245
| * vim-patch:8.0.1448: segfault with exception inside :rubyfile commandJan Edmund Lazo2019-09-14
| | | | | | | | | | | | | | | | Problem: Segmentation fault when Ruby throws an exception inside :rubyfile command. Solution: Use rb_protect() instead of rb_load_protect(). (ujihisa, closes vim/vim#2147, greywolf, closes vim/vim#2512, vim/vim#2511) https://github.com/vim/vim/commit/37badc898b8d167e11553b6d05908ffd35928a6e
| * vim-patch:8.0.1134: superfluous call to syn_get_final_id()Jan Edmund Lazo2019-09-14
| | | | | | | | | | | | Problem: Superfluous call to syn_get_final_id(). Solution: Remove it. (Ken Takata) https://github.com/vim/vim/commit/76301956f0c079d893cfd927b11456328bed4f9b
| * 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
* Merge #11015 from justinmk/getdigitsJustin M. Keyes2019-09-13
|\ | | | | getdigits: introduce `strict`, `def` parameters
| * 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
* test: fix failure on Windows (allow ".exe")Justin M. Keyes2019-09-13
| | | | ref 77594d55f709
* win/dist: nvim-qt v0.2.14 #11008Justin M. Keyes2019-09-13
|
* 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
* Merge #11007 from janlazo/vim-8.0.1772Justin M. Keyes2019-09-13
|\ | | | | vim-patch:8.0.1772,8.1.{248,259,261,267}
| * 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
* Merge #6917 'UIEnter, UILeave'Justin M. Keyes2019-09-12
|\
| * 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
|/
* Merge #10999 from janlazo/clang_pvs2Justin M. Keyes2019-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
|/
* tests: fix system_spec when run with clipboard manager (#10956)Daniel Hahler2019-09-12
| | | | | | | | | * tests: move os_kill to functional helpers * tests: fix system_spec when run with clipboard manager Replaces "xclip" with a dedicated helper program. Fixes: https://github.com/neovim/neovim/issues/4900#issuecomment-501866842
* build: dependencies: specify minimum libvterm (#10997)Justin M. Keyes2019-09-12
| | | | | | | | libvterm now advertises a version number, so we can specify the minimum required version. And this is necessary because there were breaking changes in its API. ref 2a590e229363 ref https://github.com/neovim/neovim/issues/10991
* 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`.