aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
| | * vim-patch:8.1.0800: may use a lot of memory when a function refers itselfJan Edmund Lazo2020-05-03
| | | | | | | | | | | | | | | | | | | | | | | | Problem: May use a lot of memory when a function creates a cyclic reference. Solution: After saving a funccal many times, invoke the garbage collector. (closes vim/vim#3835) https://github.com/vim/vim/commit/4456ab527a6a5faae9287f3bd2e52cc18966cfb0
| | * vim-patch:8.1.1581: shared functions for testing are disorganisedJan Edmund Lazo2020-05-03
| | | | | | | | | | | | | | | | | | Problem: Shared functions for testing are disorganised. Solution: Group finctions in script files. (Ozaki Kiichi, closes vim/vim#4573) https://github.com/vim/vim/commit/7a39dd7f00239059ce34660611589b26126a550c
| | * vim-patch:8.2.0649: undo problem whn an InsertLeave autocommand resets undoJan Edmund Lazo2020-05-03
| | | | | | | | | | | | | | | | | | | | | Problem: Undo problem whn an InsertLeave autocommand resets undo. (Kutsan Kaplan) Solution: Do not create a new undo block when leaving Insert mode. https://github.com/vim/vim/commit/db93495d276642f63f80471fbcb900b9aa1e9e42
| | * vim-patch:8.2.0648: semicolon search does not work in first lineJan Edmund Lazo2020-05-03
| | | | | | | | | | | | | | | | | | | | | Problem: Semicolon search does not work in first line. Solution: Allow the cursor to be in line zero. (Christian Brabandt, closes vim/vim#5996) https://github.com/vim/vim/commit/0e71704b77a9891ccae9f5a9c7429e933078f232
| * | vim-patch:8.1.1120: cannot easily get directory entry matches #12222Hennadii Chernyshchyk2020-05-05
| | | | | | | | | | | | | | | | | | | | | Problem: Cannot easily get directory entry matches. Solution: Add the readdir() function. (Yasuhiro Matsumoto, closes vim/vim#2439) https://github.com/vim/vim/commit/543c9b1921d7605498b54afdef518e312f1b4515 closes #12212
| * | paste: support replace mode (#11945)Jesse2020-05-05
| | | | | | | | | | | | | | | | | | * paste: support replace mode * Clean up Co-authored-by: Jesse Bakker <git@jessebakker.com>
| * | tag: fix problem when tagfunc return value is v:null (#12251)erw72020-05-05
| | | | | | | | | fixes #12250.
| * | terminal: disable 'scrolloff' (fixes flicker)Justin M. Keyes2020-05-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Besides the special-case in get_scrolloff_value(), it makes sense for 'scrolloff' and 'sidescrolloff' to reflect the correct values (for plugins, scripts, …). ref 53d607af9c53accfd634435908fb79061f1212b9 ref #11915 ref #12230
| * | terminal: always return zero from get_scrolloff_value() #12230LawAbidingCactus2020-05-04
| | | | | | | | | | | | | | | | | | | | | Fixes flicker fix #11072 fix #11915
| * | funcs: Fix a memory leak in f_expand (#12227)erw72020-05-04
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | :echo expand('%', v:false, v:true) ==423== 28 bytes in 1 blocks are definitely lost in loss record 124 of 420 ==423== at 0x4C2FB0F: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so) ==423== by 0x2AD09C: try_malloc (memory.c:71) ==423== by 0x2AD0B8: xmalloc (memory.c:105) ==423== by 0x2AE05D: xmallocz (memory.c:182) ==423== by 0x1F7CF4: vim_strnsave (strings.c:68) ==423== by 0x318813: eval_vars (ex_docmd.c:8885) ==423== by 0x34F5FC: f_expand (funcs.c:2058) ==423== by 0x36D023: call_func (eval.c:6419) ==423== by 0x370C28: get_func_tv.lto_priv.707 (eval.c:6150) ==423== by 0x372748: eval7 (eval.c:4326) ==423== by 0x37291A: eval6 (eval.c:4036) ==423== by 0x372BF6: eval5 (eval.c:3884)
| * vim-patch:8.1.0816: test for 'runtimepath' in session fails on MS-WindowsBilly Su2020-05-02
| | | | | | | | | | | | Problem: Test for 'runtimepath' in session fails on MS-Windows. Solution: Skip the test for now. https://github.com/vim/vim/commit/681b6bc86c8f60473854c0141935c07494528884
| * vim-patch:8.1.0814: :mksession cannot handle a very long 'runtimepath'Billy Su2020-05-02
| | | | | | | | | | | | | | | | Problem: :mksession cannot handle a very long 'runtimepath'. (Timothy Madden) Solution: Expand each part separately, instead of the whole option at once. (Christian Brabandt, closes vim/vim#3466) https://github.com/vim/vim/commit/ed18f2c03ae4786b489943cb575bb781a70356e4
| * version.c: update [ci skip] #12196Marvim the Paranoid Android2020-05-01
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | vim-patch:8.2.0621: after running tests asan files may remain vim-patch:8.2.0622: Haiku: GUI does not compile vim-patch:8.2.0630: "make tags" does not cover Haiku GUI file vim-patch:8.2.0631: Haiku file formatted with wrong tabstop vim-patch:8.2.0632: crash when using Haiku vim-patch:8.2.0636: :messages does not show the maintainer when $LANG is unset vim-patch:8.2.0642: Vim9: using invalid index vim-patch:8.2.0643: terminal uses brown instead of dark yellow vim-patch:8.2.0645: MS-Windows terminal: CTRL-C does not get to child job vim-patch:8.2.0651: old style benchmark test still in list of distributed files vim-patch:8.2.0654: building with Python fails vim-patch:8.2.0664: included undesired changes in Makefile vim-patch:8.2.0667: cannot install Haiku version from source vim-patch:8.2.0671: Haiku: compiler warnings
| * Merge pull request #12204 from archseer/lsp-user-dataMatthieu Coudron2020-04-30
| |\ | | | | | | lsp/completion: Expose completion_item under completed_items.user_data + vim-patch:8.2.0084
| | * vim-patch:8.2.0084: complete item "user_data" can only be a stringBlaž Hrastnik2020-04-29
| | | | | | | | | | | | | | | | | | Problem: Complete item "user_data" can only be a string. Solution: Accept any type of variable. (closes vim/vim#5412) https://github.com/vim/vim/commit/0892832bb6c7e322fcae8560eaad5a8140ee4a06
| * | lsp: use vim.tbl_isempty to check sign (#12190)Hirokazu Hata2020-04-28
| | | | | | | | | | | | | | | ref: #12164 fix #12201 sign_getdefined() returns a list, {} if the sign is not defined.
| * | tui: Fix italics when $TERM is screen in tmux #12199erw72020-04-28
| |/ | | | | | | | | | | Tmux uses smso to display italics when the default-terminal is screen, screen-*. That's not the display the user wants, so change it to do the same display as before f3ffe0b32. fixes #12193.
| * api/ui: simplify popup menu position get/set logic; fix testYatao Li2020-04-28
| |
| * api/ui: allow set bounds row and col to be less than 0; ui_pum_get_pos: ↵Yatao Li2020-04-28
| | | | | | | | return first extui bounds information instead of reducing
| * gen_api_dispatch.lua: allow msgpack int for Float args; test: add ↵Yatao Li2020-04-28
| | | | | | | | ui_pum_set_bounds and tv_dict_add_float tests
| * external pum: use floating point geometry; typval: add tv_dict_add_floatYatao Li2020-04-28
| |
| * ui_pum_get_pos: return internal pum position if external pum pos not foundYatao Li2020-04-28
| |
| * API/UI: Allow UI to set PUM position and size, and pass the position to ↵Yatao Li2020-04-28
| | | | | | | | CompleteChanged
| * Merge pull request #12018 from janlazo/vim-8.0.1123Matthieu Coudron2020-04-27
| |\ | | | | | | [RFC]vim-patch:8.0.{1123,1125,1138,1139,1142,1292,1334,1375},8.1.1264
| | * vim-patch:8.0.1375: window size wrong after maximizing with WinBarJan Edmund Lazo2020-04-26
| | | | | | | | | | | | | | | | | | | | | Problem: Window size wrong after maximizing with WinBar. (Lifepillar) Solution: Fix height computations. Redraw window when it is zero height but has a WinBar. (closes vim/vim#2356) https://github.com/vim/vim/commit/415a6939a4e8d4e26b4af26c24eb75243d3a2756
| | * vim-patch:8.1.1264: crash when closing window from WinBar clickJan Edmund Lazo2020-04-26
| | | | | | | | | | | | | | | | | | Problem: Crash when closing window from WinBar click. (Ben Jackson) Solution: Check that window pointer is still valid. (closes vim/vim#4337) https://github.com/vim/vim/commit/d2fad67e3eb71f48d23f283ef8e7b7ddf4ee180f
| | * vim-patch:8.0.1139: using window toolbar changes stateJan Edmund Lazo2020-04-26
| | | | | | | | | | | | | | | | | | Problem: Using window toolbar changes state. Solution: Always execute window toolbar actions in Normal mode. https://github.com/vim/vim/commit/a21a6a9ade7bec3a07992d4d900d4ce82eeb8a29
| | * vim-patch:8.0.1334: splitting a window with a WinBar damages window layoutJan Edmund Lazo2020-04-26
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Splitting a window with a WinBar damages window layout. (Lifepillar) Solution: Take the winbar into account when computing the new window position. Add WINBAR_HEIGHT(). https://github.com/vim/vim/commit/3167c3e7010ac7e2fd7d3aa198dd2d1dcff8ecc8
| | * vim-patch:8.0.1292: quick clicks in the WinBar start Visual modeJan Edmund Lazo2020-04-26
| | | | | | | | | | | | | | | | | | Problem: Quick clicks in the WinBar start Visual mode. Solution: Use a double click in the WinBar like a normal click. https://github.com/vim/vim/commit/d327b0c68fa9b32877123f77560f4521a9eb39db
| | * vim-patch:8.0.1138: click in window toolbar starts Visual modeJan Edmund Lazo2020-04-26
| | | | | | | | | | | | | | | | | | Problem: Click in window toolbar starts Visual mode. Solution: Add the MOUSE_WINBAR flag. https://github.com/vim/vim/commit/eb163d73b11c10b461a2839530173a33d7915a33
| | * vim-patch:8.0.1142: window toolbar menu gets a tear-off itemJan Edmund Lazo2020-04-26
| | | | | | | | | | | | | | | | | | Problem: Window toolbar menu gets a tear-off item. Solution: Recognize the window toolbar. https://github.com/vim/vim/commit/378daf87d380b9f3c4f822786dfbfdcad9ca2db9
| | * vim-patch:8.0.1125: wrong window height when splitting window with window ↵Jan Edmund Lazo2020-04-26
| | | | | | | | | | | | | | | | | | | | | | | | toolbar Problem: Wrong window height when splitting window with window toolbar. Solution: Add or subtract the window toolbar height. https://github.com/vim/vim/commit/d326ad6e93604222c64bae51f47521fe9114d1ea
| | * vim-patch:8.0.1123: cannot define a toolbar for a windowJan Edmund Lazo2020-04-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Cannot define a toolbar for a window. Solution: Add a window-local toolbar. https://github.com/vim/vim/commit/1b9645de3c05f37b5c30e78f999351b0cf486ade "WinBar" code in "screen.c" was not ported. Fix https://github.com/neovim/neovim/issues/11513#issuecomment-562012827
| * | Merge #11851 'eval.c: factor out eval/userfunc.c'Justin M. Keyes2020-04-27
| |\ \ | | | | | | | | vim-patch:7.4.2058
| | * \ Merge #11851 'eval.c: factor out eval/userfunc.c'Justin M. Keyes2020-04-26
| | |\ \ | | | |/ | | |/| | | | | vim-patch:7.4.2058
| | | * mark userfunc as legacyJakub Łuczyński2020-02-13
| | | |
| | | * rename: user_funcs -> userfuncJakub Łuczyński2020-02-13
| | | | | | | | | | | | | | | | Lets stick with vim for now
| | | * fix: includesJakub Łuczyński2020-02-13
| | | |
| | | * fix: moved macrosJakub Łuczyński2020-02-13
| | | |
| | | * fix: moved some static inline functionJakub Łuczyński2020-02-13
| | | |
| | | * fix: vvlua_partialJakub Łuczyński2020-02-13
| | | |
| | | * fix: made eval_lavars_used globalJakub Łuczyński2020-02-13
| | | |
| | | * fix: include static function declarationsJakub Łuczyński2020-02-13
| | | |
| | | * fix: header updatesJakub Łuczyński2020-02-13
| | | |
| | | * Removed redundant defineJakub Łuczyński2020-02-13
| | | |
| | | * fix: factor out make_partialJakub Łuczyński2020-02-13
| | | |
| | | * fix: prof functionsJakub Łuczyński2020-02-13
| | | |
| | | * fix: var_set_globalJakub Łuczyński2020-02-13
| | | |
| | | * fix: find_var_ht_dictJakub Łuczyński2020-02-13
| | | |
| | | * fix: factor out new functionsJakub Łuczyński2020-02-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | free_unref_funccal get_funccal_local_var get_funccal_args_var get_current_funccal_dict set_ref_in_previous_funccal set_ref_in_call_stack set_ref_in_func_args note: In vim semantic for garbage_collect was changed (the result of free_unref_funccal is ignored, bug or intentional?) For nvim I did leave previous behavior thus did_free = did_free || free_unref_funccal(copyID, testing); instead of just free_unref_funccal(copyID, testing);