aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
| * | 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);
| | * | | fix: func_initJakub Łuczyński2020-02-13
| | | | |
| | * | | unstatic some functionsJakub Łuczyński2020-02-13
| | | | |
| | * | | moved more stuffJakub Łuczyński2020-02-13
| | | | |
| | * | | created header fileJakub Łuczyński2020-02-13
| | | | |
| | * | | moved functions to user_funcs.c (no code changes)Jakub Łuczyński2020-02-13
| | | | |
* | | | | Merge #12155 ':ls filter by terminal, lastused'Justin M. Keyes2020-04-26
|\ \ \ \ \ | |_|_|/ / |/| | | |
| * | | | vim-patch:8.1.2225: the "last used" info of a buffer is under usedRob Pilling2020-04-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: The "last used" info of a buffer is under used. Solution: Add "lastused" to getbufinfo(). List buffers sorted by last-used field. (Andi Massimino, closes vim/vim#4722) https://github.com/vim/vim/commit/52410575be50d5c40bbe6380159df48cfc382ceb
| * | | | vim-patch:8.0.1651: cannot filter :ls output for terminal buffersRob Pilling2020-04-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Cannot filter :ls output for terminal buffers. Solution: Add flags for terminal buffers. (Marcin Szamotulski, closes vim/vim#2751) https://github.com/vim/vim/commit/0751f51a5b428805a8c1e9fe529693d032bec991
| * | | | vim-patch:7.4.1988Rob Pilling2020-04-19
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: When updating viminfo with file marks there is no time order. Solution: Remember the time when a buffer was last used, store marks for the most recently used buffers. https://github.com/vim/vim/commit/ab9c89b68dcbdb3fbda8c5a50dd90caca64f1bfd As this is a viminfo fix, most of this is irrelevant - the patch has just been brought across for the creation and updating of buffer's `b_last_used` properties.
* | | | | LSP: don't redefine LspDiagnostics signs #12164jakbyte2020-04-26
| | | | | | | | | | | | | | | fix #12162
* | | | | LSP: Fix show_line_diagnostics #12186Mathias Fußenegger2020-04-26
| |/ / / |/| | | | | | | Messed this up in ef0398fe88e6cc74f33fb20519997774168d7832
* | | | lint: use docstring style #12187Billy SU2020-04-26
| | | |
* | | | LSP: Add a check for null version in VersionedTextDocumentIdentifier (#12185)Chris Kipp2020-04-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | According to the spec there is the possibility that when a VersionedTextDocumentIdentifier is used in a TextEdit the value may be null. Currently we don't check for this and always assume that it's set. So currently if a TextEdit comes in for a rename for example with the version null, it fails as we are comparing the bufnumber with nil. https://microsoft.github.io/language-server-protocol/specification#versionedTextDocumentIdentifier
* | | | tui: improve support for GNU Screen (#12098)erw72020-04-26
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Wrapping it in DCS allows the following features to work with GNU Screen. - Changing the cursor style. - bracketed paste. - focus reporting.
* | | | Merge #12177 'folds: decrease reliance on globals'Justin M. Keyes2020-04-26
|\ \ \ \
| * | | | helpers: fix FIXED_TEMP_ARRAYMatthieu Coudron2020-04-24
| | | | | | | | | | | | | | | | | | | | ...was using wrong macro argument.
| * | | | lint: fix linting issuesMatthieu Coudron2020-04-24
| | | | |
| * | | | extmark: introduce extmark_splice_colsMatthieu Coudron2020-04-24
| | | | | | | | | | | | | | | | | | | | to ease up notations.
| * | | | folds: decrease reliance on global 'curwin'Matthieu Coudron2020-04-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | TODO in a future commit: - remains 2 instances of changed_lines that dont take into account buffer
* | | | | LSP: remove obsolete "peek definition" code #12178Thore Weilbier2020-04-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The method with the name 'textDocument/peekDefinition' is not part of the official language server protocol specification. Therefore no language server can/will support this. Thereby all related code and documentation as been removed.
* | | | | TUI: block signals on suspend #12180Kei Kamikawa2020-04-25
| | | | | | | | | | | | | | | fix #8075
* | | | | Merge #12181 from janlazo/vim-8.2.0635Justin M. Keyes2020-04-25
|\ \ \ \ \ | | | | | | | | | | | | vim-patch:8.2.{635,638}
| * | | | | vim-patch:8.2.0638: MS-Windows: messages test failsJan Edmund Lazo2020-04-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: MS-Windows: messages test fails. Solution: Clear environment variables. https://github.com/vim/vim/commit/47a1a8baf9c8eb22b24f667e57a1dab579999a74
| * | | | | vim-patch:8.2.0635: when using 256 colors DarkYellow does not show expected ↵Jan Edmund Lazo2020-04-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | color Problem: When using 256 colors DarkYellow does not show expected color. Solution: Use color 3 instead of 130. (Romain Lafourcade, closes vim/vim#5985) https://github.com/vim/vim/commit/e93c968f520ee8d6bc29ccc6e18055ac65e832b3
* | | | | | ci/travis: Enable ipv6 #12182Justin M. Keyes2020-04-25
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ref: a39c8b7ce30ddeed4329c28c42b1b699103dccab ref: https://github.com/vim/vim/commit/bfe13ccc58ccb96f243a58309800410db1ccb52c Also: - Remove unused macos_rvm_dance() function. (It was there for reference, but we have since resolved (or gave up) on Travis + macOS + ruby.
* | | | | LSP: Expose diagnostics grouped by bufnr (#11932)Mathias Fußenegger2020-04-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Expose `vim.lsp.buf.diagnostics_by_buf` This makes it easier to customize the diagnostics behavior. For example to defer the update they can override the `textDocument/publishDiagnostics` callback to only call `buf_diagnostics_save_positions` and then defer the other actions to a autocmd event.