| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
|
|
|
|
|
|
|
|
| |
Problem: filetype: kubectl config file is not recognized
Solution: Detect .kube/kubectl as yaml filetype
(Volodymyr Chernetskyi).
References:
- https://kubernetes.io/docs/reference/kubectl/kuberc/
closes: vim/vim#18169
https://github.com/vim/vim/commit/6cd6857cbe671ff8bc4e057b528d37795e1b5c2a
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Problem: filetype: AWS cli alias file is not recognized
Solution: Detect .aws/cli/alias as confini filetype
(Volodymyr Chernetskyi).
References:
- https://docs.aws.amazon.com/cli/v1/userguide/cli-usage-alias.html
related: vim/vim#18169
https://github.com/vim/vim/commit/be0589f1d21f543cedbcd243152721b74d7317dc
|
| |
|
|
|
|
|
|
|
|
| |
Implements [on-type
formatting](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.18/specification/#textDocument_onTypeFormatting)
using a `vim.on_key()` approach to listen to typed keys. It will listen
to keys on the *left hand side* of mappings. The `on_key` callback is
cleared when detaching the last on-type formatting client. This feature
is disabled by default.
Co-authored-by: Maria José Solano <majosolano99@gmail.com>
|
| |
|
|
|
| |
Problem: `:checkhealth` advice for Python is out-of-date.
Solution: Update the advice to point to `:help provider-python`.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: filetype: kyaml files are not recognized
Solution: Detect *.kyml files as yaml filetype
(Volodymyr Chernetskyi)
References:
- https://kubernetes.io/blog/2025/08/27/kubernetes-v1-34-release/#alpha-support-for-kyaml-a-kubernetes-dialect-of-yaml
closes: vim/vim#18158
https://github.com/vim/vim/commit/d5c89cc6bb6aa105abbd6ac07e4265e7da32d606
Co-authored-by: Volodymyr Chernetskyi <19735328+chernetskyi@users.noreply.github.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Problem: filetype: fvwm2m4 files are no longer recognized
(after 9.1.1687).
Solution: Add a special case in m4 filetype detection (zeertzjq).
closes: vim/vim#18146
https://github.com/vim/vim/commit/5355e81868ea9e6a14eeba4b9140aa1bf239fb65
Co-authored-by: Damien Lejay <damien@lejay.be>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Problem: filetype: autoconf filetype not always correct
Solution: Detect aclocal.m4 as config filetype, detect configure.ac as
config filetype, fall back to POSIX m4 (Damien Lejay).
closes: vim/vim#18065
https://github.com/vim/vim/commit/2b55474f0a78bd252290578a5774316dc5f60180
Co-authored-by: Damien Lejay <damien@lejay.be>
|
| |\
| |
| | |
feat(decor): add range-based highlighting
|
| | | |
|
| |/ |
|
| | |
|
| |
|
|
|
| |
tmux-direct is functionally the same as tmux-256color, except it
directly reports 24-bit color and how to set them (setaf/setab)
via ncurses 6.x's extended terminfo format.
|
| |
|
|
|
|
|
|
|
| |
Problem:
Hover response of MarkedString[] where the first element contains a
language identifier treated as empty.
Solution:
Fix empty check to handle case of MarkedString[] where the first element
is a pair of a language and value.
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Problem: Error on empty string prompt.
Solution: (prompt .. '\n'):gmatch('(.-)\n').
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(#35504)
Problem: filetype: Buck eXtension Lang files are not recognized
Solution: Detect *.bxl files as bzl filetype.
(Jade Lovelace)
References:
- https://buck2.build/docs/bxl/
closes: vim/vim#18130
https://github.com/vim/vim/commit/3aea867b276360ab8eb675fc4a9af5be774323e4
Co-authored-by: Jade Lovelace <jadel@mercury.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
Nvim does not have a core concept for indicating "progress" of
long-running tasks. The LspProgress event is specific to LSP.
Solution:
- `nvim_echo` can emit `kind="progress"` messages.
- Emits a `Progress` event.
- Includes new fields (id, status, percent) in the `msg_show` ui-event.
- The UI is expected to overwrite any message having the same id.
- Messages have a globally unique ID.
- `nvim_echo` returns the message ID.
- `nvim_echo(… {id=…})` updates existing messages.
Example:
local grp = vim.api.nvim_create_augroup("Msg", {clear = true})
vim.api.nvim_create_autocmd('Progress', {
pattern={"term"},
group = grp,
callback = function(ev)
print(string.format('event fired: %s', vim.inspect(ev))..'\n')
end
})
-- require('vim._extui').enable({enable=true, msg={target='msg', timeout=1000}})
vim.api.nvim_echo({{'searching'}}, true, {kind='progress', percent=80, status='running', title="terminal(ripgrep)"})
local id = vim.api.nvim_echo({{'searching'}}, true, {kind='progress', status='running', percent=10, title="terminal(ripgrep)"})
vim.api.nvim_echo({}, true, {id = id, kind='progress', percent=20, status = 'running', title='find tests'})
vim.api.nvim_echo({}, true, {id = id, kind='progress', status='running', percent=70})
vim.api.nvim_echo({{'complete'}}, true, {id = id, kind='progress', status='success', percent=100, title="find tests"})
Followups:
- Integrate with 'statusline' by listening to the Progress autocmd event.
- Integrate progress ui-event with `vim._extui`.
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
|
|
|
| |
`gopls` seems to send a nil result when there are no inlay hints for the
buffer. [The protocol](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_inlayHint)
allows for the server to send an array or nil, and it isn't clear what
nil should represent. I think it's reasonable to treat it as an empty
array though.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: completion: cannot add timeouts for 'cpt' sources
(Evgeni Chasnovski)
Solution: Add the 'autocompletetimeout' and 'completetimeout' options
(Girish Palya)
fixes: vim/vim#17908
closes: vim/vim#17967
https://github.com/vim/vim/commit/69a337edc15a6c6eba6f16d2f3b7b223a149a938
Co-authored-by: Girish Palya <girishji@gmail.com>
|
| | |
|
| |
|
|
|
|
|
|
| |
closes: vim/vim#18078
https://github.com/vim/vim/commit/5ca1ea83ad79c8d1ebd25e61c91f1199c9bc4f09
Co-authored-by: Hirohito Higashi <h.east.727@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: completion: not possible to delay the autcompletion
Solution: add the 'autocompletedelay' option value (Girish Palya).
This patch introduces a new global option 'autocompletedelay'/'acl' that
specifies the delay, in milliseconds, before the autocomplete menu
appears after typing.
When set to a non-zero value, Vim waits for the specified time before
showing the completion popup, allowing users to reduce distraction from
rapid suggestion pop-ups or to fine-tune the responsiveness of
completion.
The default value is 0, which preserves the current immediate-popup
behavior.
closes: vim/vim#17960
https://github.com/vim/vim/commit/a09b1604d4fe7516d87fbcbf2ffd2dc484799b23
N/A patch: vim-patch:9.1.1641: a few compiler warnings are output
Co-authored-by: Girish Palya <girishji@gmail.com>
|
| |
|
|
| |
This function allows the Nvim core to write arbitrary data to a TTY
connected to a UI's stdout.
|
| |
|
|
|
|
|
|
|
|
| |
Problem: Some use cases might lead to `vim.pack.add()` failing to
`:packadd` a plugin because of missing entry in 'packpath'. Like with
`nvim --clean` or manually setting `$XDG_DATA_HOME` during startup.
Solution: Document it. A more proactive approach can be ensuring correct
'packpath' entry, but it is currently somewhat verbose to do (due to
having to adjust for Windows using `\` in 'packpath' entries).
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
The load function in opts was difficult to use if you wished to
customize based on the plugin being loaded.
You could get the name, but without some way to mark a spec, that was of
limited usefulness unless you wanted to hardcode a list of names in the
function, or write a wrapper around the whole thing
Solution:
Allow users to provide an arbitrary data field in plugin specs so that
they may receive info as to how to handle that plugin in load, get() and
events, and act upon it
Co-authored-by: BirdeeHub <birdee@localhost>
Co-authored-by: Evgeni Chasnovski <evgeni.chasnovski@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
Problem: Unable to see e.g. `inputlist()` prompts that exceed the dialog
window height.
Multi-line prompts are not handled properly, and tracking
is insufficient for messages in cmdline_block mode.
Solution: Add vim.on_key handler while the dialog window is open that
forwards paging keys to the window.
Properly render multi-line prompts. Keep track of both the start
and end of the current cmdline prompt. Append messages after the
current prompt in cmdline_block mode.
|
| |
|
|
|
|
|
|
| |
The returned value is only in arbitrary order for a Dict.
closes: vim/vim#18050
https://github.com/vim/vim/commit/84a343a6ed34995adc67c062b64533c1b0bf7fb1
|
| |
|
|
|
|
|
|
|
|
| |
String type
related: vim/vim#18021
https://github.com/vim/vim/commit/44c8072ef64a7a218eb8cf4b72866921762633e4
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
| |
|
|
|
|
|
|
| |
closes: vim/vim#18021
https://github.com/vim/vim/commit/308a3130be89148cdaf83bfaf00e3e7c69ed2133
Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: filetype: Cangjie files are not recognized
Solution: Detect *.cj files as cangjie filetype, include a syntax plugin
(WuJunkai2004)
This commit introduces a new syntax highlighting file for the Cangjie
programming language, includes 4 parts as required:
- The main syntax file: runtime/syntax/cangjie.vim
- The filetype detection rule in: runtime/filetype.vim
- The documentation update in: runtime/doc/syntax.txt
- Some menus
References:
- https://gitcode.com/Cangjie
- https://cangjie-lang.cn/
fixes: 18014
closes: vim/vim#18027
https://github.com/vim/vim/commit/0c4405a6b2bc4d93c127e1b66da1b93dcfbbe3db
Co-authored-by: WuJunkai2004 <wujunkai20041123@outlook.com>
|
| |
|
|
|
|
|
|
|
| |
Problem: many FileType autocommands assume curbuf is the same as the target
buffer; this can cause &syntax to be restored for the wrong buffer in some cases
when TSHighlighter:destroy is called.
Solution: run nvim_exec_autocmds in the context of the target buffer via
nvim_buf_call.
|
| | |
|
| |\ |
|
| | | |
|
| | | |
|
| | | |
|
