aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
| * | vim-patch:8.2.3425: warning for using uninitialized variablezeertzjq2021-09-19
| | | | | | | | | | | | | | | | | | Problem: Warning for using uninitialized variable. Solution: Initialize it. (John Marriott) https://github.com/vim/vim/commit/56e14698b45a9c4ef8fa65c55c9bfe86fbb3d6bf
| * | vim-patch:8.2.3424: a sequence of spaces is hard to see in list modezeertzjq2021-09-19
| | | | | | | | | | | | | | | | | | Problem: A sequence of spaces is hard to see in list mode. Solution: Add the "multispace" option to 'listchars'. (closes vim/vim#8834) https://github.com/vim/vim/commit/f14b8ba1373f569705cb80419248054100b02360
| * | vim-patch:8.2.2640: screenstring() returns non-existing composing characterszeertzjq2021-09-19
| | | | | | | | | | | | | | | | | | Problem: screenstring() returns non-existing composing characters. Solution: Only use composing characters if there is a base character. https://github.com/vim/vim/commit/f1387285e2ebe5cb3688d729fc6fd01a169a76c1
| * | vim-patch:8.1.1110: composing chars on space wrong when 'listchars' is setzeertzjq2021-09-19
| | | | | | | | | | | | | | | | | | | | | Problem: Composing chars on space wrong when 'listchars' is set. Solution: Do not use "space" and "nbsp" entries of 'listchars' when there is a composing character. (Yee Cheng Chin, closes vim/vim#4197) https://github.com/vim/vim/commit/e5e4e22c1c15c8c22b14935affe969569acc8df9
| * | vim-patch:8.1.1079: no need for a separate ScreenLinesUtf8() test functionzeertzjq2021-09-19
| | | | | | | | | | | | | | | | | | Problem: No need for a separate ScreenLinesUtf8() test function. Solution: Get the composing characters with ScreenLines(). https://github.com/vim/vim/commit/48aed0824e47147faf19fc235ad4bcf851584c9c
| * | vim-patch:8.1.1078: when 'listchars' is set a composing char on a space is wrongzeertzjq2021-09-19
| | | | | | | | | | | | | | | | | | | | | Problem: When 'listchars' is set a composing char on a space is wrong. Solution: Separate handling a non-breaking space and a space. (Yasuhiro Matsumoto, closes vim/vim#4046) https://github.com/vim/vim/commit/5f8069bbf5d989936a2f4d7a76ae42434017e3a2
| * | vim-patch:8.1.1071: cannot get composing characters from the screenzeertzjq2021-09-19
| | | | | | | | | | | | | | | | | | | | | Problem: Cannot get composing characters from the screen. Solution: Add screenchars() and screenstring(). (partly by Ozaki Kiichi, closes vim/vim#4059) https://github.com/vim/vim/commit/2912abb3a2fd72074e3901c8ae1d4a77ce764675
* | | build(lint): commit linter #15620Justin M. Keyes2021-09-19
| | |
* | | build(lint): commit linter #15620dundargoc2021-09-19
| | |
* | | refactor(tests): remove redir_exec #15718Justin M. Keyes2021-09-19
|/ / | | | | | | | | | | | | | | | | | | | | Problem - `redir_exec` is obsolete, but it keeps getting used in new tests because people copy existing tests. - Disadvantages of `redir_exec`: - Captures extra junk before the actual error/message that we _want_ to test. - Does not fail on error, unlike e.g. `command()`. Solution - Use new functions like `nvim_exec` and `pcall_err`.
* | fix(diagnostic): only update decorations for loaded buffers (#15715)Gregory Anders2021-09-18
| | | | | | | | | | When vim.diagnostic.config() is called, the decorations for diagnostics are re-displayed to use the new configuration. This should only be done for loaded buffers.
* | ci(labeler): diagnosticJustin M. Keyes2021-09-18
| |
* | feat(lsp): improve vim.lsp.util.apply_text_edits (#15561)hrsh7th2021-09-18
| | | | | | | | | | - Fix the cursor position after applying TextEdits - Support reversed range of TextEdit - Invoke nvim_buf_set_text one by one
* | Merge pull request #15710 from gpanders/show_line_diagnosticsMichael Lingelbach2021-09-18
|\ \ | | | | | | fix(diagnostic): resolve nil bufnr in show_line_diagnostics
| * | test: add test case for show_line_diagnosticsGregory Anders2021-09-18
| | |
| * | fix(diagnostic): resolve nil bufnr in show_line_diagnosticsGregory Anders2021-09-18
| | |
* | | vim-patch:8.2.3394: filler lines are wrong when changing text in diff mode ↵Jaehwang Jerry Jung2021-09-18
| | | | | | | | | | | | | | | | | | | | | | | | (#15547) Problem: Filler lines are wrong when changing text in diff mode. Solution: Don't change the filler lines on every change. Check scrollbinding when updating the filler lines. (closes vim/vim#8809) https://github.com/vim/vim/commit/04626c243c47af91c2580eaf23e12286180e0e81
* | | refactor: format #15702dundargoc2021-09-18
|/ /
* | Merge pull request #15632 from bfredl/rtptestBjörn Linse2021-09-18
|\ \ | | | | | | runtime: always use DIP_START and remove duplication of start packages in &rtp
| * | refactor(runtime): handle pack/foo/start/bar/after dirs properlyBjörn Linse2021-09-18
| | | | | | | | | | | | | | | | | | | | | | | | The order should be: XDG_CONFIG_HOME/nvim XDG_DATA_HOME/nvim/site/pack/foo/start/bar/ XDG_CONFIG_HOME/nvim/after XDG_DATA_HOME/nvim/site/pack/foo/start/bar/after
| * | refactor(runtime): always use DIP_START when searching for runtime filesBjörn Linse2021-09-18
|/ / | | | | | | | | | | | | | | Now remove the addition of "start/*" packages in 'packpath' as explicit items in 'runtimepath'. This avoids 'runtimepath' from becoming very long when using a lot of plugins as packages. To get the effective search path as a list, use |nvim_list_runtime_paths()|
* | fix(diagnostic): change default severity_sort order Mathias Fußenegger2021-09-18
|\ \
| * | fix(diagnostic): remove check on nil return valueGregory Anders2021-09-17
| | | | | | | | | | | | | | | vim.diagnostic._set_signs doesn't return anything, so checking the return value will always fail.
| * | refactor(diagnostic): combine config() and set() callsGregory Anders2021-09-17
| | |
| * | refactor(diagnostic): group local functions togetherGregory Anders2021-09-17
| | |
| * | fix(diagnostic): change default severity_sort orderGregory Anders2021-09-17
| | | | | | | | | | | | | | | | | | | | | When severity_sort is true, higher severities should be displayed before lower severities (e.g. ERROR is displayed over WARN). Also improved the test case for this.
* | | refactor: convert TRUE/FALSE to true/false (#15660)dundargoc2021-09-18
|/ /
* | Merge pull request #15696 from gpanders/diagnostic-sign-fixMichael Lingelbach2021-09-17
|\ \ | | | | | | Diagnostic hot fixes
| * | fix(diagnostic): support severity_sortGregory Anders2021-09-17
| | |
| * | fix(diagnostic): correctly handle folder level diagnosticsGregory Anders2021-09-17
| | |
| * | docs(diagnostics): fix typosGregory Anders2021-09-17
| | |
| * | fix(diagnostic): fix wrong data type in setqflist()Gregory Anders2021-09-17
| | |
| * | fix(diagnostic): don't overwrite existing sign definitionsGregory Anders2021-09-17
| | |
* | | fix(termdebug): replace mapset with nvim_set_keymap (#15699)ii142021-09-17
| | | | | | | | | Co-authored-by: ii14 <ii14@users.noreply.github.com>
* | | fix(typo): overriden -> overridden (RE: PR #14159) (#15360)Oliver Marriott2021-09-17
| | |
* | | test: reorg #15698Justin M. Keyes2021-09-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Subdirectories like "visual", "insert", "normal" encourage people to separate *related* tests for no good reason. Typically the _mode_ is not the relevant topic of a test (and when it is, _then_ create an appropriate describe() or it()). Solution: - Delete the various `test/functional/<mode>/` subdirectories, move their tests to more meaningful topics. - Rename `…/normal/` to `…/editor/`. - Move or merge `…/visual/*` and `…/insert/*` tests into here where appropriate. - Rename `…/eval/` to `…/vimscript/`. - Move `…/viml/*` into here also. * test(reorg): insert/* => editor/mode_insert_spec.lua * test(reorg): cmdline/* => editor/mode_cmdline_spec.lua * test(reorg): eval core tests => eval_spec.lua
* | | Merge pull request #15364 from seandewar/vim-8.2.3337Jan Edmund Lazo2021-09-17
|\ \ \ | |/ / |/| | vim-patch:8.2.{3286,3289,3293,3298,3313,3321,3328,3330,3331,3337,3354,3355,3357,3360,3369,3375}
| * | vim-patch:8.2.3375: using uninitialized memorySean Dewar2021-09-17
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Using uninitialized memory. Solution: Initialize textprop_save_len. https://github.com/vim/vim/commit/df9070e300dabf0c54de87a75973a80adb38afa3 textprop_save_len is N/A.
| * | vim-patch:8.2.3369: auto formatting after "cw" leaves cursor in wrong spotSean Dewar2021-09-17
| | | | | | | | | | | | | | | | | | Problem: Auto formatting after "cw" leaves cursor in wrong spot. Solution: Do not auto-format after the delete. (closes vim/vim#8789) https://github.com/vim/vim/commit/6b36d2a16d7931bac82ef8b5654c68ac456b24bf
| * | vim-patch:8.2.3360: user function completion fails with dict functionSean Dewar2021-09-17
| | | | | | | | | | | | | | | | | | | | | | | | Problem: User function completion fails with dict function. Solution: Do not stop sequencing through the list if user functions when encountering an empty name. (Naohiro Ono, closes vim/vim#8765, closes vim/vim#8774) https://github.com/vim/vim/commit/5aec755b678cfd434b8ea2158d06992f33e1ff80
| * | vim-patch:8.2.3357: crash when 'virtualedit' is set and window is narrowSean Dewar2021-09-17
| | | | | | | | | | | | | | | | | | Problem: Crash when 'virtualedit' is set and window is narrow. () Solution: Check that width is not zero. (closes vim/vim#8767) https://github.com/vim/vim/commit/02f8694a6bd116ab3316add4a7ea6735bf2e8839
| * | vim-patch:8.2.3337: completing "call g:" returns entries with just "g:"Sean Dewar2021-09-17
| | | | | | | | | | | | | | | | | | Problem: Completing "call g:" returns entries with just "g:". (Naohiro Ono) Solution: Skip empty strings returned by get_user_func_name(). (closes vim/vim#8753) https://github.com/vim/vim/commit/069f90852f1444cac50491c10dfbd339a3f9e0c8
| * | vim-patch:8.2.3330: Coverity reports using uninitialized fieldSean Dewar2021-09-17
| | | | | | | | | | | | | | | | | | Problem: Coverity reports using uninitialized field. Solution: Initialize the field early. https://github.com/vim/vim/commit/7deb4115ef72c0468cd6f9cc5f036d5c405641d4
| * | vim-patch:8.2.3328: Coverity error for not checking return valueSean Dewar2021-09-17
| | | | | | | | | | | | | | | | | | Problem: Coverity error for not checking return value. Solution: Check value is not negative. https://github.com/vim/vim/commit/b85d3627d9a7b41d603c58a16d0ddbf6b88beeaf
| * | vim-patch:8.2.3321: some code is not testedSean Dewar2021-09-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Some code is not tested. Solution: Add some more tests. (Dominique Pellé, closes vim/vim#8735) https://github.com/vim/vim/commit/bd9e7961256ea6a98bd5a7bfe14e32c4c47186e6 Include Test_confirm_write_partial_file() anyway, even though it will not be run.
| * | vim-patch:8.2.3313: unused code in win_exchange() and frame_remove()Sean Dewar2021-09-17
| | | | | | | | | | | | | | | | | | Problem: Unused code in win_exchange() and frame_remove(). Solution: Remove the code. (closes vim/vim#8728) https://github.com/vim/vim/commit/9e2fa4bb9eb40a78a1ae1f67a4064651b5ce0aac
| * | vim-patch:8.2.3293: finding completions may cause an endless loopSean Dewar2021-09-17
| | | | | | | | | | | | | | | | | | | | | Problem: Finding completions may cause an endless loop. Solution: Use a better way to check coming back where the search started. (Andy Gozas, closes vim/vim#8672, closes vim/vim#8671) https://github.com/vim/vim/commit/6a230c6b32695393785ae64b440ce5f023a22382
| * | vim-patch:8.2.3286: win_enter_ext() has too many boolean argumentsSean Dewar2021-09-17
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: win_enter_ext() has too many boolean arguments. Solution: use one flags argument with defined values. https://github.com/vim/vim/commit/d61f2f772a59617850e9aa2f5fa069c1aad8e074 Include some style changes to appease the linter. N/A patches for version.c: vim-patch:8.2.3289: compiler warning for unused variable with small features Problem: Compiler warning for unused variable with small features. Solution: Rearrange #ifdefs. https://github.com/vim/vim/commit/f18e8a969a3414ed5e6b7159c40fe43963021ff3 vim-patch:8.2.3298: build failure with small features Problem: Build failure with small features. Solution: Add #ifdef. https://github.com/vim/vim/commit/6f6d58c3809010b1386634c1aeec61f1a66e72c2 vim-patch:8.2.3331: Coverity warns for using value without boundary check Problem: Coverity warns for using value without boundary check. Solution: Add a boundary check. https://github.com/vim/vim/commit/ed7cb2df35244e40e5c4df06169b50e705427576 vim-patch:8.2.3354: build failure with +byte_offset but without +textprop Problem: Build failure with +byte_offset but without +textprop. (John Marriott) Solution: Adjust the #ifdef. https://github.com/vim/vim/commit/92755bba30ec7a4c72ae0280420ba5c3847a9385 vim-patch:8.2.3355: MS-Windows: compiler warning for 64-32 bit conversion Problem: MS-Windows: compiler warning for 64-32 bit conversion. Solution: Add type casts. https://github.com/vim/vim/commit/434df7a401c92d4084bb0a01ffd6d1737ae0193b
* | | refactor(style): switch-case formatting, "uncrustify:indent-off" #15669dundargoc2021-09-17
| | | | | | | | | | | | | | | | | | * refactor: disable formatting for attribute in macro * fixup: disable/enable uncrustify with uncrustify:indent-off/on * fixup: stop indenting contents inside braces in case * fixup: remove case brace if no variable declaration
* | | Merge pull request #15580 from seandewar/vim-8.2.3378Jan Edmund Lazo2021-09-17
|\ \ \ | | | | | | | | vim-patch:8.2.{3378,3379,3384,3386,3398,3400}
generated by cgit (git 2.34.1) at 2025-05-10 00:03:16 +0000