aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* vim-patch:8607192: runtime(typescriptreact): fix highlighting nested and ↵Christian Clason2024-05-27
| | | | | | | | escaped quotes in string props (vim/vim#14852) https://github.com/vim/vim/commit/86071925ede1030d86e764054e36ef8ab56fc666 Co-authored-by: Linda_pp <rhysd@users.noreply.github.com>
* vim-patch:76174e7: runtime(asm): remove the indent plugin since it has too ↵Christian Clason2024-05-27
| | | | | | | | | | many issues fixes: vim/vim#14791 https://github.com/vim/vim/commit/76174e71101503900d54d38e00b3a869af1fdd85 Co-authored-by: Christian Brabandt <cb@256bit.org>
* vim-patch:9.1.0446: getregionpos() inconsistent for partly-selected ↵zeertzjq2024-05-27
| | | | | | | | | | | | multibyte char (#29032) Problem: getregionpos() behaves inconsistently for a partly-selected multibyte char. Solution: Always use column of the first byte for a partly-selected multibyte char (zeertzjq). closes: vim/vim#14851 https://github.com/vim/vim/commit/ef73374dc3e4bf8104ba31d5b22517f8028b467a
* fix(extmarks): issues with revalidating marks #28961luukvbaal2024-05-26
| | | | | | Problem: Invalid marks appear to be revalidated multiple times, and decor is added at the old position for unpaired marks. Solution: Avoid revalidating already valid marks, and don't use old position to add to decor for unpaired marks.
* fix(tui): reset clear_region attributes during startup #28713luukvbaal2024-05-26
| | | | | | Problem: Fix added in #28676 worked accidentally(used variables were themselves uninitialized at this point during startup) and does not always work. Solution: Reset attributes when clearing regions during startup.
* fix(tohtml): properly handle multiple hl groups #29012Riley Bruins2024-05-26
| | | | | | | | | Problem: :TOhtml doesn't properly handle virtual text when it has multiple highlight groups. It also improperly calculates position offset for multi-byte virt_text characters. Solution: Apply the `vim.api.nvim_strwidth` broadly to properly calculate character offset, and handle the cases where the `hl` argument can be a table of multiple hl groups.
* Merge #29021 TOhtml fixesJustin M. Keyes2024-05-26
|\
| * fix(tohtml): show how many warnings are hiddenaltermo2024-05-26
| |
| * fix(tohtml): ignore lsp inlay hintsaltermo2024-05-26
| |
| * fix(tohtml): replace ipairs with pairsaltermo2024-05-26
| |
* | Merge pull request #29014 from bfredl/editortestbfredl2024-05-26
|\ \ | |/ |/| refactor(tests): more global highlight definitions
| * refactor(tests): more global highlight definitionsbfredl2024-05-26
| |
* | build(deps): bump tree-sitter-c to v0.21.3Christian Clason2024-05-26
| |
* | build(deps): bump tree-sitter-query to v0.4.0Christian Clason2024-05-26
| |
* | build(deps): bump luajit to HEAD - 93e87998bChristian Clason2024-05-26
|/
* Merge pull request #29006 from bfredl/apitestbfredl2024-05-26
|\ | | | | refactor(tests): use more global highlight definitions
| * refactor(tests): use more global highlight definitionsbfredl2024-05-26
| |
* | vim-patch:9.1.0442: hare runtime files outdated (#29011)zeertzjq2024-05-26
| | | | | | | | | | | | | | | | | | | | | | Problem: hare runtime files outdated Solution: runtime(hare): update hare.vim to match upstream (Amelia Clarke) closes: vim/vim#14836 https://github.com/vim/vim/commit/35dfe58a540e2fb0eff953630f8e4fcbf4bc26ca Co-authored-by: Amelia Clarke <selene@perilune.dev>
* | vim-patch:0076ddc: runtime(debian): update Debian runtime files (vim/vim#14849)Christian Clason2024-05-25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | * Add space in template for 'commentstring' * Add 'comments' and 'commentstring' support to debcontrol * debversions: Move Ubuntu releases outside of standard support to unsupported Although trust, xenial, and bionic are not EOL yet, their standard support period has ended. Reported-by: Riley Bruins <ribru17@gmail.com> https://github.com/vim/vim/commit/0076ddc07dc1d97afcf3252fd361885abbaf23d5 Co-authored-by: James McCoy <jamessan@debian.org> Co-authored-by: Riley Bruins <ribru17@gmail.com>
* | fix(snippet): don't override unnamed register on tabstop select (#28998)Mathias Fußenegger2024-05-25
| |
* | fix(lsp): handle nil root_dir in health check (#29007)Mathias Fußenegger2024-05-25
| | | | | | | | | | | | | | The root directory could show up as something like: Root directory: ~/path/to/cwd/v:null Despite being `nil`
* | refactor: move provider-related to where they are useddundargoc2024-05-25
|/
* Merge pull request #28999 from bfredl/snapshot2bfredl2024-05-25
|\ | | | | refactor(tests): update screen:snapshot_util() to use new-style highlights
| * refactor(tests): update screen:snapshot_util() to use new-style highlightsbfredl2024-05-25
|/ | | | | | | | | | | This makes screen:snapshot_util() generate code with the new screen:add_extra_attr_ids { ... } pattern. For convenience, the old-style configuration is still detected and supported (until all tests have been refactored, which is my goal for the 0.11 cycle) Remove the last traces of the "ignore" attr anti-pattern. This code is no longer functional, it is just "ignore" argument being passed around like a hot potato at this point.
* test(unit): skip flaky 'typval.c dict extend() works' testdundargoc2024-05-25
|
* feat(main): expand file ~\ or ~/ prefix on Windows (#28515)Rafael Kitover2024-05-25
| | | | | | | | In command_line_scan() for MSWIN, expand "~\" or "~/" prefixed paths to the USERPROFILE environment variable for the user's profile directory. Fix #23901 Signed-off-by: Rafael Kitover <rkitover@gmail.com>
* refactor(lua): rewrite vim.highlight.range() (#28986)zeertzjq2024-05-25
| | | | - Use getregionpos(). - Use a single extmark for non-blockwise selection.
* Merge pull request #28617 from glepnir/border_hlbfredl2024-05-25
|\ | | | | fix(float): missing default highlight for title
| * fix(float): missing default highlight for titleglepnir2024-05-25
| | | | | | | | | | | | Problem: there is missing default title highlight when highlight not defined in title text chunk. Solution: when attr is not set use default title highlight group.
* | vim-patch:9.1.0444: Not enough tests for getregion() with multibyte chars ↵zeertzjq2024-05-25
| | | | | | | | | | | | | | | | | | | | (#29000) Problem: Not enough tests for getregion() with multibyte chars. Solution: Add a few more tests (zeertzjq). closes: vim/vim#14844 https://github.com/vim/vim/commit/dff55a335889c746a79974f7c52cdcdebad682c2
* | vim-patch:5e45715: runtime(typescript): update outdated syntax filesChristian Clason2024-05-25
| | | | | | | | | | | | | | | | | | | | fixes: vim/vim#14721 fixes: HerringtonDarkholme/yats.vim#277 closes: vim/vim#14840 https://github.com/vim/vim/commit/5e4571508480c8f51748e49fb05c1891db0cb803 Co-authored-by: rhysd <lin90162@yahoo.co.jp>
* | vim-patch:b1ffc52: runtime(i3config/swayconfig): fix floating_modifier ↵Christian Clason2024-05-25
| | | | | | | | | | | | | | | | highlight (vim/vim#14841) https://github.com/vim/vim/commit/b1ffc52694756efef339f01bbb1fc6ef4eaf16da Co-authored-by: Josef Litoš <54900518+JosefLitos@users.noreply.github.com>
* | test(lintdoc): check that input list is same length as output list (#28976)dundargoc2024-05-25
| |
* | feat(lsp): update LSP healthcheck format (#28980)Gregory Anders2024-05-24
| | | | | | | | | | | | This is mostly an aesthetic change, although there are a few new pieces of information included. Originally I wanted to investigate including server capabilities in the healthcheck, but until we have the ability to fold/unfold text in health checks that would be too much information.
* | vim-patch:9.1.0443: Can't use blockwise selection with width for getregion() ↵zeertzjq2024-05-25
| | | | | | | | | | | | | | | | | | | | | | | | (#28985) Problem: Can't use a blockwise selection with a width for getregion(). Solution: Add support for blockwise selection with width like the return value of getregtype() or the "regtype" value of TextYankPost (zeertzjq). closes: vim/vim#14842 https://github.com/vim/vim/commit/afc2295c2201ae87bfbb42d5f5315ad0583ccabf
* | docs: update LSP quickstart (#28954)Gregory Anders2024-05-24
| | | | | | | | | | | | | | | | | | | | The LSP quickstart can act as our true "entrypoint" for answering the question "How do I use LSP in Neovim?" As such, it can be a little more beginniner-friendly than other sections of our help docs by including explanatory comments and a more fleshed out example (including a `FileType` autocommand). This also includes some other minor wording updates and points users toward `:checkhealth lsp`.
* | feat(defaults): add LSP default mappings (again) (#28650)Gregory Anders2024-05-24
| |
* | fix(fs): make vim.fs.root work for relative paths and unnamed buffers (#28964)Gregory Anders2024-05-24
| | | | | | | | If a buffer does not have a backing file then fall back to the current working directory.
* | fix: show swapfile warning as a warning (#28971)Gregory Anders2024-05-24
| | | | | | | | | | The new default SwapExists autocommand displays warning text (W325) but does not use the WarningMsg highlight group as other warnings do. Use the WARN log level when displaying this warning.
* | refactor: replace deprecated vim.loop with vim.uvdundargoc2024-05-24
| |
* | vim-patch:9.1.0440: function get_lval() is too long (#28963)zeertzjq2024-05-24
| | | | | | | | | | | | | | | | | | | | | | Problem: function get_lval() is too long Solution: factor out the get_lval_subscript() function (Yegappan Lakshmanan) closes: vim/vim#14839 https://github.com/vim/vim/commit/44cadaa18c1816f7a576f1870790ee01a23c1071 Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
* | vim-patch:8.2.3158: strange error message when using islocked() with a ↵zeertzjq2024-05-24
| | | | | | | | | | | | | | | | | | | | | | | | | | number (#28962) Problem: Strange error message when using islocked() with a number. (Yegappan Lakshmanan) Solution: Check that the name is empty. https://github.com/vim/vim/commit/1840a7b4e3577e617f724c9d07ccc78195cc010a Use ll_name_len instead. Co-authored-by: Bram Moolenaar <Bram@vim.org>
* | feat(complete): specify reason for CompleteDoneFamiu Haque2024-05-24
| | | | | | | | | | Problem: `CompleteDone` currently does not specify the reason for why completion was done, which is problematic for completion plugins as they cannot know whether the event was triggered due to the completion being canceled, accepted, or for some other reason. Solution: Add a `reason` key to `v:event`, which is set by `CompleteDone` to indicate why completion ended.
* | fix: change deprecation presentationdundargoc2024-05-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | Deprecation with vim.deprecate is currently too noisy. Show the following warning instead: [function] is deprecated. Run ":checkhealth vim.deprecated" for more information. The important part is that the full message needs to be short enough to fit in one line in order to not trigger the "Press ENTER or type command to continue" prompt. The full information and stack trace for the deprecated functions will be shown in the new healthcheck `vim.deprecated`.
* | feat: allow gx to function for markdown linksdundargoc2024-05-24
| | | | | | | | | | | | | | In other words, `gx` works regardless of where it was used in `[...](https://...)`. This only works on markdown buffers. Co-authored-by: ribru17 <ribru17@gmail.com>
* | docs: extract health to its own filedundargoc2024-05-24
| |
* | vim-patch:9.1.0439: Cannot filter the history (#28958)zeertzjq2024-05-24
| | | | | | | | | | | | | | | | | | | | Problem: Cannot filter the history Solution: Implement :filter :history closes: vim/vim#14835 https://github.com/vim/vim/commit/42a5b5a6d0d05255b9c464abe71f29c7677b5833 Co-authored-by: Christian Brabandt <cb@256bit.org>
* | vim-patch:9.1.0441: getregionpos() can't properly indicate positions beyond ↵zeertzjq2024-05-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | eol (#28957) Problem: getregionpos() can't properly indicate positions beyond eol. Solution: Add an "eol" flag that enables handling positions beyond end of line like getpos() does (zeertzjq). Also fix the problem that a position still has the coladd beyond the end of the line when its column has been clamped. In the last test case with TABs at the end of the line the old behavior is obviously wrong. I decided to gate this behind a flag because returning positions that don't correspond to actual characters in the line may lead to mistakes for callers that want to calculate the length of the selected text, so the behavior is only enabled if the caller wants it. closes: vim/vim#14838 https://github.com/vim/vim/commit/2b09de910458247b70751928217422c38fd5abf8
* | vim-patch:9.1.0438: Wrong Ex command executed when :g uses '?' as delimiter ↵zeertzjq2024-05-24
| | | | | | | | | | | | | | | | | | | | | | (#28956) Problem: Wrong Ex command executed when :g uses '?' as delimiter and pattern contains escaped '?'. Solution: Don't use "*newp" when it's not allocated (zeertzjq). closes: vim/vim#14837 https://github.com/vim/vim/commit/3074137542961ce7b3b65c14ebde75f13f5e6147
* | vim-patch:22ac941: runtime(i3config/swayconfig): support floating_modifier ↵Christian Clason2024-05-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | none; revert broken highlighting - fix floating_modifier $mod normal|inverse was being hightlighted as error reverting the floating_modifier change from dd83b63 - will currently allow invalid syntax after floating_modifier fixes: vim/vim#14826 closes: vim/vim#14827 https://github.com/vim/vim/commit/22ac941208fcb2c63ad172c6cf0b39b077b5b682 Co-authored-by: James Eapen <james.eapen@vai.org> Co-authored-by: JosefLitos <litosjos@fit.cvut.cz>
generated by cgit (git 2.34.1) at 2025-05-28 20:25:34 +0000