| Commit message (Collapse) | Author | Age |
... | |
| |\
| | |
| | | |
fix(messages)!: vim.ui_attach message callbacks are unsafe
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Lua callbacks for "msg_show" events with vim.ui_attach() are
executed when it is not safe.
Solution: Disallow non-fast API calls for "msg_show" event callbacks.
Automatically detach callback after excessive errors.
Make sure fast APIs do not modify Nvim state.
|
| | | |
|
| |/
| |
| |
| | |
Resolves #30034
|
| |\
| | |
| | | |
fix(tests): needing two calls to setup a screen is cringe
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Before calling "attach" a screen object is just a dummy container for
(row, col) values whose purpose is to be sent as part of the "attach"
function call anyway.
Just create the screen in an attached state directly. Keep the complete
(row, col, options) config together. It is still completely valid to
later detach and re-attach as needed, including to another session.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
@Konfekt suggested adding this [1]; I confirmed that both source
repositories have permissive licenses [2], [3] that permit copying the
code (at least where the compiler scripts are concerned).
[1]: https://github.com/benknoble/Dotfiles/commit/570b1006fd794b0b9f5434b4fed4c2d785fcb05c
[2]: https://github.com/JalaiAmitahl/maven-compiler.vim
[3]: https://github.com/mikelue/vim-maven-plugin/issues/13
closes: vim/vim#16041
https://github.com/vim/vim/commit/c4208da0f4e59925f5e5828ed7725e22fd118e47
Co-authored-by: D. Ben Knoble <ben.knoble+github@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This brings the included Racket runtime files to commit c41bc5a (indent
for[*]/lists with accumulator clause correctly, 2024-11-12) of
https://github.com/benknoble/vim-racket.
Note that not all files from that repository are included.
closes: vim/vim#16046
https://github.com/vim/vim/commit/8e013b14211ee236f4866e7281ad4366e0ab18cd
Co-authored-by: D. Ben Knoble <ben.knoble+github@gmail.com>
|
| |\
| | |
| | | |
vim-patch: doc updates
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
netrw-handler
related: vim/vim#16043
https://github.com/vim/vim/commit/9b05326afdb0359a2dd40470b2b47a6e422662e9
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
| |/
| |
| |
| |
| |
| |
| |
| | |
fixes: vim/vim#16043
https://github.com/vim/vim/commit/8b96858996c4bdc68c055d2ef4afa5f88eda455e
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
**Problem:** Currently node names with non-alphanumeric, non
underscore/hyphen characters (only possible with anonymous nodes) are
not given a proper error message. See tree-sitter issue 3892 for more
details.
**Solution:** Apply a different scanning logic to anonymous nodes to
correctly identify the entire node name (i.e., up until the final double
quote)
|
| |\
| | |
| | | |
refactor(highlight): make enum of builtin highlights start with 1
|
| |/
| |
| |
| |
| | |
This makes it possible to use HLF_ values directly as highlight id:s
and avoids +1 adjustments especially around messages.
|
| |
| |
| |
| |
| |
| |
| | |
closes: vim/vim#16039
https://github.com/vim/vim/commit/210c49bbe8b2edf15fd4fbbc089ec128e4c9c0c9
Co-authored-by: Konfekt <Konfekt@users.noreply.github.com>
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
for (L)Idris2 + ipkg
closes: vim/vim#15993
https://github.com/vim/vim/commit/5ca8f223f03dbd85f5e06c8e1d500c65f311eaf1
Co-authored-by: Serhii Khoma <srghma@gmail.com>
Co-authored-by: Christian Clason <ch.clason+github@icloud.com>
|
| |
| |
| |
| |
| | |
Problem: Crash when initializing for --startuptime errors.
Solution: Report the error to stderr, as neither logging nor messages
have been initialized yet.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
commands (#31185)
related: vim/vim#16044
https://github.com/vim/vim/commit/f18987caa5095e9ff154f924d952047c67c9fb64
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: tests: mouse_shape tests use hard code sleep value
(Bram Moolenaar)
Solution: Use WaitForAssert() instead (Yee Cheng Chin)
related: vim/vim#12157
closes: vim/vim#16042
https://github.com/vim/vim/commit/24078e39cd10b8a65af5297ebe12ddf1e550167a
Co-authored-by: Yee Cheng Chin <ychin.git@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: Quitting source buffer for ```:InspectTree``` command raises
```E855``` when source buffer and tree views are the only open buffers.
Solution: Add ```QuitPre``` event to autocmd handling closing/hiding the
source buffer to close all open tree views. This allows nvim to quit
when source and tree buffers are the only open windows.
|
| |
| |
| |
| | |
Leftover from #21026.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: filetype: kubernetes config file not recognized
Solution: detect '/.kube/config' file as yaml filetype
(Jonathan Lopez)
closes: vim/vim#11076
https://github.com/vim/vim/commit/6fbf63de865001dedafc227465e651926cf6f6dc
Co-authored-by: Jonathan Lopez <jonathanglopez@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
These changes enable tar.vim to keep permissions of files that were
edited intact instead of replacing them with the default permissions.
The major change for this is switching from "tar -OPxf", which reads out
the contents of the selected file from an tar archive to stdout to
"tar -pPxf" which extracts the selected file to the current directory
with permissions intact
This requirs the temporary directory to be created earlier.
closes: vim/vim#7379
https://github.com/vim/vim/commit/129a8446d23cd9cb4445fcfea259cba5e0487d29
Co-authored-by: Lennart00 <73488709+Lennart00@users.noreply.github.com>
|
| |\
| | |
| | | |
refactor(tests): use more global highlight definitions
|
| | | |
|
| |\ \
| | | |
| | | | |
fix(messages): pass previous highlight id to ext chunks
|
| | | | |
|
| |/ / |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This changes the type for the sorted pattern table from
`vim.filetype.mapping[]` to `vim.filetype.mapping.sorted[]`
E.g. instead of:
```lua
{
{ ['/debian/changelog$'] = {'debchangelog', { parent = '/debian/' } },
{ ['%.git/'] = { detect.git , { parent = 'git/', priority = -1 } },
}
```
It is now:
```lua
{
{ '/debian/, '/debian/changelog$', 'debchangelog' },
{ 'git/' , '%.git/' , detect.git , -1 },
}
```
Overall this should roughly cut the amount of tables used by 3, and
replaces lots of hash indexes with array indexes.
|
| |\
| | |
| | | |
feat(ext_messages): add hl_id to ext_messages chunks
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Ext_messages chunks only contain the highlight attr id, which
is not very useful for vim.ui_attach() consumers.
Solotion: Add highlight group id to message chunks, which can easily be
used to highlight text in the TUI through nvim_buf_set_extmark():
hl_group = synIDattr(id, "name").
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Highlight group id is not propagated to the end of the message call
stack, where ext_messages are emitted.
Solution: Refactor message functions to pass along highlight group id
instead of attr id.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
So let's revert "runtime(tex): add Number highlighting to syntax file"
This (partly) reverts commits 8e6b5034f32049fd0 and 6065755a39d838aab
fixes: vim/vim#16030
https://github.com/vim/vim/commit/622f6f5b9a9c2b88423f31a98e99cd3324446fcf
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
view (#31161)
closes: vim/vim#16020
https://github.com/vim/vim/commit/5b63b236a0af198f6c3c9883a3f6344b110dabb3
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
related: vim/vim#11271
https://github.com/vim/vim/commit/6065755a39d838aaba03808f77d58c34b3b63e91
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: there are a few typos in the source.
Solution: Correct typos (zeertzjq).
closes: vim/vim#16026
https://github.com/vim/vim/commit/7c5152826f61bc968ba539ff6db3a55e75556bf2
|
| | |
| | |
| | |
| | |
| | | |
closes: vim/vim#16023
https://github.com/vim/vim/commit/060107cbc40a68b30d81e5531a1c8dde91fc9b59
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
closes: vim/vim#11271
https://github.com/vim/vim/commit/8e6b5034f32049fd0f1447c85ab71d47f49a820a
Co-authored-by: amarakon <amar.al-zubaidi45@tutanota.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
closes: vim/vim#11419
https://github.com/vim/vim/commit/a14c457cad99621db7950b78e7d257c300b7d897
Co-authored-by: Dani Dickstein <daniel.dickstein@gmail.com>
|
| | | |
|
| |\ \
| | | |
| | | | |
vim-patch: Vim syntax updates
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
highlighting
Fix command name termination, match bang, and allow a line-continued
argument.
closes: vim/vim#15358
https://github.com/vim/vim/commit/bbe5252c2c2a6a49c794719a894ab10cdafebc62
Co-authored-by: Doug Kearns <dougkearns@gmail.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
enum and interface highlighting
- Enable folding of class, enum and interface declarations.
- Highlight constructor names with the Function highlight group, like
other special methods.
- Mark function definitions using special method names as errors.
- Highlight :type arguments.
fixes: vim/vim#14393#issuecomment-2042796198.
closes: vim/vim#13810
https://github.com/vim/vim/commit/818c641b6fac73b574a2b760213f515cee9a3c8e
Co-authored-by: Doug Kearns <dougkearns@gmail.com>
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
from namesake builtin functions (vim/vim#14348)
Currently, the overriding object method definitions are
matched as vimFunctionError (:help builtin-object-methods,
v9.1.0148).
For example:
------------------------------------------------------------
vim9script
class Test
def string(): string
return "Test"
enddef
endclass
echo string(Test.new()) == Test.new().string()
------------------------------------------------------------
Instead, let's introduce a new syntax group vimMethodName
and make these methods its members. In order to emphasise
the link between the overriding methods and the overridden
functions for highlighting, vimMethodName is linked by
default to vimFuncName.
https://github.com/vim/vim/commit/80aabaab6636faa7cec461acc4b1fcc3a4c89376
Co-authored-by: Aliaksei Budavei <32549825+zzzyxwvut@users.noreply.github.com>
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
from the :new ex command (vim/vim#14050)
With the arrival of Vim9 classes, the syntax must allow for
_new_ constructors; multiple constructor definitions are
supported for a class, provided distinct suffix-names are
used. Currently, the defined constructors match either
vimCommand or vimFunctionError (for any newBar).
For example:
------------------------------------------------------------
vim9script
class Foo
def new()
enddef
def newBar()
enddef
endclass
------------------------------------------------------------
Since every constructor is required to bear a lower-cased
_new_ prefix name, it should suffice to distinguish them
from functions, and so there are no new highlight or syntax
groups introduced.
https://github.com/vim/vim/commit/dfcef890cbdd3ec26de040b2e26d77444dc46862
Co-authored-by: Aliaksei Budavei <32549825+zzzyxwvut@users.noreply.github.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
closes: vim/vim#16011
https://github.com/vim/vim/commit/5e7f43b6ac2ac23d4fbfded75827a13f981d9a96
Co-authored-by: Ella Moss <ella.moss@utah.edu>
Co-authored-by: Christian Brabandt <cb@256bit.org>
|