| Commit message (Collapse) | Author | Age |
|\
| |
| | |
feat(treesitter): allow capture text to be transformed
|
| | |
|
| | |
|
| |
| |
| |
| | |
Co-authored-by: Lewis Russell <lewis6991@gmail.com>
|
|/
|
|
|
|
|
|
| |
Problem: Cadence files are not recognized.
Solution: Recognize Cadence files. (Janez Podhostnik, closes vim/vim#11951)
https://github.com/vim/vim/commit/cb626a4692df7154be02b47d6089ec679e95cb44
Co-authored-by: Janez Podhostnik <janez.podhostnik@gmail.com>
|
|
|
|
|
|
|
|
| |
Problem: Display shows lines scrolled down erroneously. (Yishai Lerner)
Solution: Do not change "wl_lnum" at index zero. (closes vim/vim#11938)
https://github.com/vim/vim/commit/61fdbfa1e3c842252b701aec12f45839ca41ece5
Co-authored-by: Bram Moolenaar <Bram@vim.org>
|
|
|
|
|
|
|
|
|
| |
Problem: go.work.sum files are not recognized.
Solution: Recognize go.work.sum files as the gosum filetype. (Amaan Qureshi,
closes vim/vim#11940)
https://github.com/vim/vim/commit/4ad8ae8465e30df38dba31910f130891b16d38a0
Co-authored-by: Amaan Qureshi <amaanq12@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
1. Some calls to preserve_exit() don't put a message in IObuff, so the
IObuff printed by preserve_exit() contains unrelated information.
2. If a TUI client runs out of memory or receives a deadly signal, the
error message is shown on alternate screen and cannot be easily seen
because the TUI exits alternate screen soon afterwards.
Solution:
Pass error message to preserve_exit() and exit alternate screen before
printing it.
Note that this doesn't fix the problem that server error messages cannot
be easily seen on exit. This is tracked in #21608 and #21843.
|
|
|
|
|
|
|
| |
Problem: Cursor may move with autocmd in Visual mode.
Solution: Restore "VIsual_active" before calling check_cursor().
(closes vim/vim#11939)
https://github.com/vim/vim/commit/49f0524fb575bb1cf4881e472afab7d37c579440
|
|
|
|
|
|
|
| |
file(GENERATE) has surprising behavior as it doesn't allow different
file contents for configurations with the same file name. This results
in an error when building neovim with a multi-config generator. Use a
workaround for now where we set the build type for multi-config
generators to "Unknown".
|
|
|
|
|
|
|
| |
Update runtime files.
https://github.com/vim/vim/commit/be4e01637e71c8d5095c33b9861fd70b41476732
Co-authored-by: Bram Moolenaar <Bram@vim.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Any logic involving CMAKE_BUILD_TYPE is automatically broken as it won't
work with multi-config generators. The only exception is if we
explicitly check whether the current generator is single-config as well.
Instead, use generator expressions or cmake variables that allows to set
options for certain build types only such as
INTERPROCEDURAL_OPTIMIZATION_<CONFIG>.
Opt to generate all headers with optimization level O2 with no debug
information for all build types as that is the simplest way to make it
behave the same for all generators.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The "length-of-one" trick, where the last element of a struct is an
array of size 1, but extra size is allocated when calling malloc where
it uses more than 1 element in the array, cause problems with some
compilers. Some compilers set _FORTIFY_SOURCE=2 by default which
incorrectly considers it as an overflow. More information:
https://github.com/neovim/neovim/issues/223#issuecomment-1413828554
Using flexible array members allows us to to properly convey to the
compiler that its size may be larger than 1. This also enables us to
remove lengthy workarounds that are unreliable, as they depend on
CMAKE_BUILD_TYPE which isn't defined for multi-config generators.
Closes: https://github.com/neovim/neovim/issues/223
|
|\
| |
| | |
docs: clarify "pipe" mode for sockconnect
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Make it more clear that on unix the "pipe" mode of sockconnect uses unix
local domain sockets, not named pipes (FIFOs) which are not currently
supported.
See discussion in #22080.
Signed-off-by: Thayne McCombs
|
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: FIRRTL files are not recognized.
Solution: Add a pattern for FIRRTL files. (Amaan Qureshi, closes vim/vim#11931)
https://github.com/vim/vim/commit/685bf83b73d0fe6fd36bb2949bebd6aae66a139e
Co-authored-by: Amaan Qureshi <amaanq12@gmail.com>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem:
When a TUI client is suspended it still receives UI events from the
server, and has to process these accumulated events when it is resumed.
With mulitple TUI clients this is a bigger problem, considering the
following steps:
1. A TUI client is attached.
2. CTRL-Z is pressed and the first client is suspended.
3. Another TUI client is attached.
4. CTRL-Z is pressed and a "suspend" event is sent to both clients. The
second client is suspended, while the first client isn't able to
process the event because it has already been suspended.
5. The first client is resumed. It processes the accumulated "suspend"
event and suspends immediately.
Solution:
Make a TUI client detach on suspend and re-attach on resume.
|
|\ \
| | |
| | | |
fix(extmarks): adjust extmarks when inserting prompt prefix
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | | |
paths.lua.in doesn't rely on any generator expressions, so it's safe to
remove file(GENERATE).
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: The 'statuscolumn' width is being estimated without the
proper context. In particular, this resulted in the fact
that a custom fold column could be included in the estimated
`number_width()`, and doubly added when actually drawing the
statuscolumn due to `win_col_off()` also adding the
`'foldcolumn'` width. Resulting in a status column that is
`'foldcolumn'` cells wider than necessary.
Solution: Estimate 'statuscolumn' width in `get_statuscol_str()` when
a buffer's line count has changed.
|
| | |
| | |
| | |
| | | |
This prevents the TUI from doing unexpected things when receiving a
deadly signal or running out of memory.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Co-authored-by: marvim <marvim@users.noreply.github.com>
N/A patches:
vim-patch:9.0.1272: typo in pattern for filetype detection
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: "1v" may select block with wrong size. (Evgeni Chasnovski)
Solution: Compute "curswant" in the right line. (closes vim/vim#11925)
https://github.com/vim/vim/commit/8f531662e28c37560bf5ac20a059bf00d01ee5a4
Co-authored-by: Bram Moolenaar <Bram@vim.org>
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
fix(man): use italics for <bs>_
Even though underline is strictly what this should be. <bs>_ was used by
nroff to indicate italics which wasn't possible on old typewriters so
underline was used. Modern terminals now support italics so lets use
that now.
See:
- https://unix.stackexchange.com/questions/274658/purpose-of-ascii-text-with-overstriking-file-format/274795#274795
- https://cmd.inp.nsk.su/old/cmd2/manuals/unix/UNIX_Unleashed/ch08.htm
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Using sizeof() and subtract array size is tricky.
Solution: Use offsetof() instead. (closes vim/vim#11926)
https://github.com/vim/vim/commit/1b438a8228a415720efb5ca1c0503f5467292e8e
|
|\ \ \
| | | |
| | | | |
build(deps): bump tree-sitter-vimdoc to v1.3.0
|
|/ / / |
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| | |
(#22081)
Problem: Allocating more memory than needed for extended structs.
Solution: Use offsetof() instead of sizeof(). (Dominique Pelle,
closes vim/vim#4786)
https://github.com/vim/vim/commit/47ed553fd5bebfc36eb8aa81686eeaa5a84eccac
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: .clangd and .stylelintrc files don't get a filetype.
Solution: Use yaml for .clangd and json for .stylelintrc files. (Mark
Skelton, closes vim/vim#11916)
https://github.com/vim/vim/commit/9c51798a1f3b79ace5ae0551a8bb122025ac94ed
Co-authored-by: Mark Skelton <mdskelton99@gmail.com>
|
| |
| |
| |
| |
| |
| | |
Problem: Crash when using search stat in narrow screen.
Solution: Check length of message. (closes vim/vim#11921)
https://github.com/vim/vim/commit/a7d36b732070944aab614944075ec0b409311482
|
| |
| |
| | |
Align comments in did_set_string_option_for() at column 57.
|
|\ \
| | |
| | | |
refactor(tests): run unittests using main nvim binary - delete separate nvim-test build
|
| | |
| | |
| | |
| | | |
This allows us to get rid of the separate "nvim-test" target
|
| | | |
|
| | | |
|
|\ \ \
| |/ /
|/| | |
fix(treesitter): validate language name
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Some injections (like markdown) allow specifying arbitrary
language names for code blocks, which may be lead to errors when
looking for a corresponding parser in runtime path.
Solution: Validate that the language name only contains alphanumeric
characters and `_` (e.g., for `c_sharp`) and error otherwise.
|
|\ \ \
| | | |
| | | | |
fix(tests): use -l mode for lsp tests
|
|/ / /
| | |
| | |
| | |
| | | |
This fixes "fake server" from leaking memory, which makes ASAN very
upset, except on current ASAN CI for some reason.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: KDL files are not recognized.
Solution: Add a pattern for KDL files. (Amaan Qureshi, closes vim/vim#11898)
https://github.com/vim/vim/commit/907349a74331fc1bc48cf43c1e7d54cb9e0e4fc9
Co-authored-by: Amaan Qureshi <amaanq12@gmail.com>
|
| | | |
|
| | |
| | |
| | |
| | |
| | | |
This value can not be relied on as it doesn't work for
multi-configuration generators. I don't think this undocumented option
is used much, if at all, so I think we should remove it.
|
| | |
| | |
| | |
| | | |
We already have a "make install", it makes sense to also have a "make
uninstall".
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
When I run ./scripts/bump_deps.lua I get an error:
Vim:E475: Invalid value for argument cmd: 'command' is not executable
Running command -v in shell fixes this.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Elsa files are not recognized.
Solution: Add the name of Elsa files. (Amaan Qureshi)
https://github.com/vim/vim/commit/2a99fe6c41efcd5d1eb47823e7e73cf391e230ba
|