| Commit message (Collapse) | Author | Age |
... | |
| | |
| | |
| | |
| | |
| | | |
This ensures that any OptionSet autocommands will fire when the value is
changed.
|
| | | |
|
| | |
| | |
| | |
| | | |
Uploads are significantly faster, upwards of 90% improvement in worst case
scenarios.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Notable changes:
- Downloads are significantly faster, upwards of 90% improvement in worst case
scenarios.
- Artifacts can be downloaded from other workflow runs and repositories when
supplied with a PAT.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
runtime(cmake): sync runtime files with upstream (vim/vim#13597)
https://github.com/vim/vim/commit/3afc9f2556faf2574d7950d879f2bf61612f3367
Co-authored-by: Eisuke Kawashima <e-kwsm@users.noreply.github.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
runtime(vim): Update syntax file, fix missing for highlight (vim/vim#13668)
Fix highlighting of :for command. Link the vimFor syntax group to the
vimCommand highlight group.
Error introduced in commit f686921
https://github.com/vim/vim/commit/1c97b5c0c0b4a60d652b78da4470aeb8a7509700
Co-authored-by: dkearns <dougkearns@gmail.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
runtime(netrw): Fix `w:netrw_bannercnt` ref error with `netrw_fastbrowse=2` (vim/vim#13659)
* NetRW: Fix `w:netrw_bannercnt` ref error with `netrw_fastbrowse=2`
* NetRW: Fix wrong `w:netrw_bannercnt` setting
closes: vim/vim#13640
https://github.com/vim/vim/commit/b52e7ac7c61cd88d04ee6b7b1808c361dd4a7640
Co-authored-by: KSR-Yasuda <31273423+KSR-Yasuda@users.noreply.github.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
runtime(sbt): do not set b:did_ftplugin before sourcing scala ftplugin(vim/vim#13657)
The `b:did_ftplugin` guard was set and prevented us from actually sourcing `ftplugin/scala.vim`. Since the latter script also sets the guard properly, we can simply remove the guard here.
https://github.com/vim/vim/commit/5a68cdf14915f20a1a6889cd0a76d29ecd374f24
Co-authored-by: Karl Yngve Lervåg <karl.yngve@lervag.net>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
runtime(vim): Update syntax file (vim/vim#13653)
Improve variable highlighting in :let, :unlet, :const and :for commands.
Match registers and local, global and terminal option variables.
https://github.com/vim/vim/commit/f6869212c9e19ec8f2a4434732dd28f84f170163
Co-authored-by: dkearns <dougkearns@gmail.com>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Having a dynamically generated string is more maintainable than having
multiple files.
Also add linker flags and any potential LTO flags to the --version
output.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
runtime(doc): grammar & typo fixes
closes: vim/vim#13654
https://github.com/vim/vim/commit/17dca3cb97cdd7835e334b990565c8c0b93b1284
Co-authored-by: Dominique Pellé <dominique.pelle@tomtom.com>
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| | |
runtime(termdebug): add Tbreak command
closes: vim/vim#13656
https://github.com/vim/vim/commit/323dda1484d95ee5c8a1b2205f8c495446df75ee
Co-authored-by: iam28th <artyom28th@gmail.com>
|
| |
| |
| |
| |
| | |
Anonymous namespaces are more difficult to extend or hook into since
they do not appear in the output of nvim_get_namespaces(). Use named
namespaces instead.
|
| | |
|
| |
| |
| |
| |
| |
| | |
Bumps [github/codeql-action](https://github.com/github/codeql-action) from 2 to 3.
- [Release notes](https://github.com/github/codeql-action/releases)
- [Changelog](https://github.com/github/codeql-action/blob/main/CHANGELOG.md)
- [Commits](https://github.com/github/codeql-action/compare/v2...v3)
|
|/ |
|
|
|
|
|
|
| |
Problem: Unpaired marks are invalidated if its column is deleted,
which may just be a "placeholder" column, e.g. for signs.
Solution: Only remove unpaired marks if its entire row is deleted.
|
|
|
| |
This makes the screen states consistently have no EOB lines.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
Unlike termopen(), nvim_open_term() PTYs do not carriage-return the
cursor on newline ("\n") input.
nvim --clean
:let chan_id = nvim_open_term(1, {})
:call chansend(chan_id, ["here", "are", "some", "lines"])
Actual behavior:
here
are
some
lines
Expected behaviour:
here
are
some
lines
Solution:
Add `force_crlf` option, and enable it by default.
|
| |
|
|
|
|
|
| |
Problem: 'termsync' overwrites the first parameter of a format string
when UNIBI_OUT() encounters an overflow.
Solution: Don't use tui->params[] for 'termsync'.
|
|
|
| |
Wrap the query with passthrough sequence
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
Diagnostic sign fixups
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
|
| |
Problem: Wiki contents are not discoverable and hard to maintain.
Solution: Move FAQ to runtime docs.
Co-authored-by: Christian Clason <c.clason@uni-graz.at>
|
|
|
|
| |
after sign implementation refactor by using extmark, we can use
`nvim_buf_set_extmark` to set diagnostic sign instead use `sign_define`
|
|
|
|
|
|
|
| |
If multiple XTGETTCAP requests are active at once (for example, for
requesting the Ms capability and truecolor capabilities), then the
TermResponse autocommand may fire for capabilities that were not
requested. Instead, make sure that the provided callback is only called
for capabilities that were actually requested.
|
|
|
|
|
|
|
|
| |
Problem: screenpos() may crash with neg. column
Solution: validate and correct column
closes: vim/vim#13669
https://github.com/vim/vim/commit/ec54af4e26952d954a4cc009f62c80ea01445d30
|
| |
|
|
|
|
|
| |
uv_close asserts that a handle is not already closing. We can guard
against this assertion failure by manually checking the handle's closing
status ourselves.
|
|
|
|
|
| |
Instead of a markdown file, just use a lua file instead that users can
use directly.
|
| |
|
| |
|
| |
|
|
|
|
| |
Problem: Vimscript function exists() can't check v:lua functions.
Solution: Add support for v:lua functions to exists().
|
|\
| |
| | |
fix(eval): use no_ff instead of ffdos as condition
|
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: line2byte behavior is changed after commit b051b13. It no
longer return `-1` on empty buffer.
Solution: use `nof_ff` instead of `!ff_dos` as condition. Then
compatible behavior of line2byte() is restored.
|
| |
| |
| | |
See also: https://github.com/neovim/neovim/pull/26364
|
| | |
|
| | |
|
|\ \
| | |
| | | |
fix(treesitter): improve vim.treesitter.foldexpr
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Collect on_bytes and flush at the invocation of the scheduled callback
to take account of commands that triggers multiple on_bytes.
* More accurately track movement of folds so that foldexpr returns
reasonable values even when the scheduled computation is not run yet.
* Start computing folds from the line above (+ foldminlines) the changed
lines to handle the folds that are removed due to the size limit.
* Shrink folds that end at the line at which another fold starts to
assign proper level to that line.
* Use level '=' for lines that are not computed yet.
|
| | | |
|
| | | |
|