aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
| * | | revert: "refactor: use S_LEN macro" (#29319)Lewis Russell2024-06-14
| | | | | | | | | | | | | | | | | | | | revert: "refactor: use S_LEN(s) instead of s, n (#29219)" This reverts commit c37695a5d5f2e8914fff86f3581bed70b4c85d3c.
| * | | Merge pull request #29322 from zeertzjq/vim-02f3ebacfbfazeertzjq2024-06-14
| |\ \ \ | | | | | | | | | | vim-patch:02f3eba,d353d27
| | * | | vim-patch:d353d27: runtime(doc): restore description of "$" in col() and ↵zeertzjq2024-06-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | virtcol() (vim/vim#14981) These are different from line() and getpos(). https://github.com/vim/vim/commit/d353d2782032b91498601afefee4256592f48074
| | * | | vim-patch:02f3eba: runtime(doc): deduplicate getpos(), line(), col(), virtcol()zeertzjq2024-06-14
| |/ / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Move the main description to getpos() and link to that from the other functions. closes: vim/vim#14970 https://github.com/vim/vim/commit/02f3ebacfbfa1f892347d7532278f24620e68300
| * | | vim-patch:902b766: runtime(java): Include element values in non-marker ↵Christian Clason2024-06-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | annotations (vim/vim#14979) Make a formal definition for normal and single-element kinds of annotations that otherwise require for their containment to repeat each time all syntax groups that describe element values. Reference: https://docs.oracle.com/javase/specs/jls/se21/html/jls-9.html#jls-9.7 https://github.com/vim/vim/commit/902b766858fad89ab30b4e0a92ddd1244b2a4cbe Co-authored-by: Aliaksei Budavei <32549825+zzzyxwvut@users.noreply.github.com>
| * | | fix(tui): skip TUI in ui_rgb_attached (#29096)Gregory Anders2024-06-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The ui_rgb_attached function determines if any UI is attached which supports RGB (truecolor). We determine if the TUI supports RGB via the 'termguicolors' option which is checked at the beginning of this function. If the TUI does not support RGB ('termguicolors' is unset), we check to see if any _other_ UI is attached which supports RGB. Normally, the TUI's "rgb" flag and the 'termguicolors' option are the same. However, they may differ during startup when the "rgb" flag is set by tui/tui.c to indicate to the core that the terminal emulator supports truecolor. The 'termguicolors' option is not actually set until _defaults.lua runs.
| * | | Merge pull request #29103 from gpanders/test-no-tgcGregory Anders2024-06-12
| |\ \ \ | | | | | | | | | | test: do not set termguicolors in test runner
| | * | | test: remove checks for failed tests on WindowsGregory Anders2024-05-31
| | | | |
| | * | | fix(vim.text): remove assert from vim.text.hexdecodeGregory Anders2024-05-31
| | | | | | | | | | | | | | | | | | | | Instead, return nil plus an error message if the input is invalid.
| | * | | test: do not set termguicolors in test runnerGregory Anders2024-05-31
| | | | | | | | | | | | | | | | | | | | | | | | | It's not clear why this is needed and it has adverse side effects on other tests.
| * | | | Merge pull request #29303 from lewis6991/fix/wobufLewis Russell2024-06-12
| |\ \ \ \ | | | | | | | | | | | | fix(vim.wo): never allow non-zero bufnr
| | * | | | test: fix vim.deprecate testsLewis Russell2024-06-12
| | | | | |
| | * | | | fix(vim.wo): never allow non-zero bufnrLewis Russell2024-06-12
| | | | | |
| * | | | | Merge pull request #29290 from gpanders/push-wuqlkrkuypzzGregory Anders2024-06-12
| |\ \ \ \ \ | | |/ / / / | |/| | | | Add StatusLineTerm highlight group and move terminal buffer defaults
| | * | | | refactor(terminal): move :terminal defaults to _defaults.luaGregory Anders2024-06-12
| | | | | |
| | * | | | feat(highlight): add StatusLineTerm and StatusLineTermNC groupsGregory Anders2024-06-12
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These highlight groups are used for the statusline in :terminal windows. By default they link to StatusLine and StatusLineNC (respectively), so there is no visual difference unless a colorscheme defines these groups separately.
| * | | | vim-patch:210b39c: runtime(doc): clarify documentation for "v" position at ↵zeertzjq2024-06-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | line() (#29296) Problem: the previous documentation falsely states that "v" always refers to the start of a visual area. In fact, the reference of "v" and "." complement each other. If the cursor is at the start of a (characterwise) visual area, then "v" refers to the end of the area. Solution: be more verbose and explicit about the connection between "." and "v" and also refer to |v_o| which many vim users will be familiar with for visual areas. https://github.com/vim/vim/commit/210b39c2d686d875e2464ca1f42131453dc6bd41 Co-authored-by: Peter Aronoff <peter@aronoff.org>
| * | | | vim-patch:9.1.0477: block_editing errors out when using <enter> (#29294)zeertzjq2024-06-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: block_editing errors out when using <enter> (Ali Rizvi-Santiago, after v9.1.0274) Solution: Change ins_len from size_t to int so that the test if ins_len is negative actually works properly Add a test, so that this doesn't regress. fixes: vim/vim#14960 https://github.com/vim/vim/commit/1fb9eae5794c3f808468fbc2935c5144f9e0b5b1 Co-authored-by: Christian Brabandt <cb@256bit.org>
| * | | | vim-patch:b4e648a: runtime(doc): fix typos in syntax.txt (#29293)zeertzjq2024-06-12
| | | | | | | | | | | | | | | | | | | | | | | | | https://github.com/vim/vim/commit/b4e648a0066940e0e8b513ff2e7347b5a3473694 Co-authored-by: Ken Takata <kentkt@csc.jp>
| * | | | Merge pull request #29292 from zeertzjq/vim-059cbe893355zeertzjq2024-06-12
| |\ \ \ \ | | | | | | | | | | | | vim-patch:059cbe8,959c3c8
| | * | | | vim-patch:959c3c8: runtime(vim): Update base-syntax, configurable comment ↵zeertzjq2024-06-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | string highlighting (vim/vim#14931) Allow highlighting of strings within comments to be disabled by setting g:vimsyn_comment_strings to false. https://github.com/vim/vim/commit/959c3c887b2e52c7141b2a09a53634481911b1b7 Co-authored-by: dkearns <dougkearns@gmail.com>
| | * | | | vim-patch:059cbe8: runtime(vim): Update base-syntax, match multiline ↵zeertzjq2024-06-12
| |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | continued comments (vim/vim#13936) Match multiline (continued) line comments. Continued tail comments are not supported yet. https://github.com/vim/vim/commit/059cbe8933550e4f2b10ab564fb4398e95280198 Co-authored-by: dkearns <dougkearns@gmail.com>
| * | | | vim-patch:2e3b2a8: runtime(kdl): use shiftwidth() instead of &tabstop in ↵Christian Clason2024-06-12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | indent script closes: vim/vim#14962 https://github.com/vim/vim/commit/2e3b2a8d8971850f15fb367ddb358a8565e15324 Co-authored-by: Yinzuo Jiang <jiangyinzuo@foxmail.com>
| * | | | feat(terminal): add support for copying with OSC 52 in embedded terminal ↵Gregory Anders2024-06-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | (#29117) When libvterm receives the OSC 52 escape sequence it ignores it because Nvim does not set any selection callbacks. Install selection callbacks that forward to the clipboard provider, so that setting the clipboard with OSC 52 in the embedded terminal writes to the system clipboard using the configured clipboard provider.
| * | | | Merge pull request #29278 from bfredl/strcatbfredl2024-06-11
| |\ \ \ \ | | | | | | | | | | | | refactor(memory): use builtin strcat() instead of STRCAT()
| | * | | | refactor(memory): use builtin strcat() instead of STRCAT()bfredl2024-06-11
| | | |/ / | | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The latter was mostly relevant with the past char_u madness. NOTE: STRCAT also functioned as a counterfeit "NOLINT" for clint apparently. But NOLINT-ing every usecase is just the same as disabling the check entirely.
| * | | | refactor: use S_LEN(s) instead of s, n (#29219)James2024-06-11
| | | | |
| * | | | fix(types): add some vim.fn type annotationsnotomo2024-06-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Some vim.fn have no type annotations. Solution: Add type annotations.
| * | | | fix(types): use vararg return type annotationWill Hopkins2024-06-11
| | | | | | | | | | | | | | | | | | | | build(types): allow vararg returns in function types
| * | | | vim-patch:2d88210: runtime(kdl): include syntax, indent and ftplugin filesChristian Clason2024-06-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | closes: vim/vim#14956 https://github.com/vim/vim/commit/2d88210b3c8516c30ed104054e5cdaef67880755 Co-authored-by: inzuo Jiang <jiangyinzuo@foxmail.com> Co-authored-by: Aram Drevekenin <aram@poor.dev>
| * | | | vim-patch:b8076f9: runtime(deb822sources): add missing Enabled field in ↵Christian Clason2024-06-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | syntax script closes: vim/vim#14898 It lacks the support of Enabled: boolean option field [1]: e.g. Types: deb Uris: https://paulcarroty.gitlab.io/vscodium-deb-rpm-repo/debs/ Components: main Suites: vscodium Architectures: amd64 i386 arm64 armhf Enabled: yes Signed-By: /var/lib/extrepo/keys/vscodium.asc This patch was also forwarded to upstream. [2] [1] https://manpages.debian.org/unstable/apt/sources.list.5.en.html#DEB822-STYLE_FORMAT [2] https://salsa.debian.org/vim-team/vim-debian/-/merge_requests/16 https://github.com/vim/vim/commit/b8076f92a1a1a12101ab8288e9e173e687afecff Co-authored-by: Kentaro Hayashi <kenhys@gmail.com>
| * | | | vim-patch:7e9a1a7: runtime(svelte): basic svelte ftplugin fileChristian Clason2024-06-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | closes: vim/vim#14949 https://github.com/vim/vim/commit/7e9a1a75b80c73b1dbe83adb69c9708aa2f0bc4d Co-authored-by: Igor <igorlfs@ufmg.br>
| * | | | refactor(lua): improve type annotationsLewis Russell2024-06-11
| |/ / /
| * | | Merge pull request #29272 from luukvbaal/signcolbfredl2024-06-11
| |\ \ \ | | |_|/ | |/| | fix(column): clamp line number for legacy signs
| | * | fix(column): clamp line number for legacy signsLuuk van Baal2024-06-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Legacy :sign API still allows placing signs beyond the end of the buffer. This is unaccounted for by the signcolumn tracking logic and is disallowed in general for the extmark API which implements it now. Solution: Clamp legacy sign line number to the length of the buffer.
| * | | fix(lsp): do not reset buf version when detaching client (#29242)Ilia Choly2024-06-10
| |/ /
| * | Merge #29238 from clason/feat/help-tocJustin M. Keyes2024-06-10
| |\ \
| | * | docs: fix more treesitter parsing errorsChristian Clason2024-06-09
| | | |
| | * | feat(help): use treesitter for table of contentsChristian Clason2024-06-09
| | | | | | | | | | | | | | | | | | | | | | | | Problem: Creating the table of contents for `gO` is complicated. Solution: Use treesitter instead.
| | * | build(deps): bump tree-sitter-vimdoc to v3.0.0Christian Clason2024-06-08
| | | |
| * | | fix(glob): handle overlapping `{}` condition elements #29236Jon Huhn2024-06-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change fixes an issue where glob patterns like `{a,ab}` would not match `ab` because the first option `a` matches, then the end of the string is expected but `b` is found, and LPeg does not backtrack to try the next option `ab` which would match. The fix here is to also append the rest of the pattern to the generated LPeg pattern for each option. This changes a glob `{a,ab}` from being parsed as ("a" or "ab") "end of string" to ("a" "end of string" or "ab" "end of string") Here, matching against `ab` would try the first option, fail to match, then proceed to the next option, and match. The sacrifice this change makes is dropping support for nested `{}` conditions, which VSCode doesn't seem to support or test AFAICT. Fixes #28931 Co-authored-by: Sergey Slipchenko <faergeek@gmail.com>
| * | | fix(api): allow `scope = 'local'` with `buf` when using `nvim_get_option_value`dundargoc2024-06-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | `nvim_get_option_value` throws a warning if both `scope` and `buf` options are used at the same time. This is because using `buf` always implies `scope` is local, and is therefore not needed. There's however no need to error if `scope` is already set "local" as it's the correct value.
| * | | feat(lsp): include end_col, end_lnum in vim.lsp.buf.locations_to_items #29164Tom Praschan2024-06-09
| | | |
| * | | vim-patch:9c4389a: runtime(doc): Fix small style issues (#29263)zeertzjq2024-06-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | closes: vim/vim#14942 https://github.com/vim/vim/commit/9c4389acc307943a2cd754ecbec3834810d152e4 Co-authored-by: h-east <h.east.727@gmail.com>
| * | | vim-patch:9.1.0472: Inconsistencies between functions for option flags (#29262)zeertzjq2024-06-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Inconsistencies between functions for option flags. Solution: Consistently use "unsigned int" as return type and rename get_bkc_value() to get_bkc_flags() (zeertzjq). closes: vim/vim#14925 https://github.com/vim/vim/commit/aa925eeb97bd294d4a5253a3194949a37cbc8365
| * | | vim-patch:d6b4afb: runtime(java): Exclude lambda expressions from _when_ ↵Christian Clason2024-06-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | _switch-case_ label clauses (vim/vim#14945) These guard clauses are always boolean expressions, whereas lambda expressions can only appear in either an assignment, a casting, or an invocation context. References: https://docs.oracle.com/javase/specs/jls/se21/html/jls-14.html#jls-14.11.1 https://docs.oracle.com/javase/specs/jls/se21/html/jls-15.html#jls-15.27 https://github.com/vim/vim/commit/d6b4afb636aed7eaf709eb27c4944a1263a0f887 Co-authored-by: Aliaksei Budavei <32549825+zzzyxwvut@users.noreply.github.com>
| * | | fix(runtime): add commentstring for glsl ftpluginSamuel Born2024-06-09
| | | |
| * | | Merge pull request #29248 from bfredl/dynamic_kvecbfredl2024-06-09
| |\ \ \ | | | | | | | | | | refactor(os/shell): we have DynamicBuffer at home
| | * | | refactor(os/shell): we have DynamicBuffer at homebfredl2024-06-09
| |/ / / | | | | | | | | | | | | DynamicBuffer at home: KVÄCK
| * | | Merge pull request #29141 from bfredl/rstream2bfredl2024-06-09
| |\ \ \ | | | | | | | | | | refactor(io): make rstream use a linear buffer
generated by cgit (git 2.34.1) at 2025-05-08 14:13:42 +0000