| Commit message (Collapse) | Author | Age |
... | |
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
refactor(state): Remove EXMODE_NORMAL
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | | |
There's already an ignore directive but it's placed on the wrong line.
This commit should correct it.
|
| |/ / /
|/| | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
This fixes an issue introduced in #14771 (fix: source syncolors.vim
before startup scripts) that affected highlights for users who set
'background' to light in their startup script. Because syncolor.vim
checks for the value of &background, it was always setting up the 'dark'
background colors, which looked wrong for users using light backgrounds.
The primary benefit of #14771 is that it decoupled highlighting from the
syntax engine. This is useful for e.g. treesitter, which still makes use
of highlights even if the syntax engine is disabled. For this reason, it
is still worthwhile to source syncolor.vim separately from synload.vim,
which #14771 accomplishes. However, we should still source syncolor.vim
after the user startup scripts, to ensure that we are respecting the
options the user sets.
Another corollary benefit is that this reduces some redundancy in
highlight definitions, since we now only source syncolors.vim if the
user did not already enable a colorscheme.
|
|\ \ \ \
| |/ / /
|/| | | |
fix: source syncolors.vim before startup scripts
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This fixes an issue (#12573) where colorscheme files are sourced twice
upon startup. This occurs when the startup script calls `:colorscheme`,
which sets the `g:colors_name` global variable. When syntax highlighting
is enabled in `syn_maybe_enable()` the `syntax.vim` script is sourced
which in turn sources `synload.vim`. This script checks to see if
`g:colors_name` is set and, if so, runs
exe "colors " . colors_name
This is done to ensure that highlight groups are defined before enabling
the syntax highlighting engine.
Instead, source syncolors.vim before the startup scripts which sets up
default highlights and only load the full syntax engine after
the startup scripts or when the user runs `:syntax on`. Add a guard
variable `did_syncolor` to prevent syncolor.vim from being sourced
twice and remove the line mentioned above from synload.vim so that
the colorscheme file is not re-sourced when the syntax engine is loaded.
|
|\ \ \
| | | |
| | | | |
refactor(lua): initialize lua state at startup instead of dynamically
|
| |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
lua is used as part of implementation for more core features. As an
example, every user keypress will invoke a lua function to check for
keypress handlers (regardless if they are registered or not). Thus not
starting lua until it is first used doesn't make much sense anymore.
nlua_enter was also needed due to the earlier stateful &rtp
translation, which by now have been made stateless.
|
|\ \ \
| | | |
| | | | |
[RDY] chore(PVS/V768): don't use enum as bool.
|
| |/ / |
|
|/ /
| |
| |
| |
| | |
False positive. Documentation for grid_scroll says "`cols` is always
zero, reserved for future use".
|
| |
| |
| |
| |
| | |
It might come as a schocking surprise, but the defaults we support
are the NEOVIM defaults.
|
| | |
|
| | |
|
| |
| |
| |
| | |
stdin is a macro in Windows builds.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Some programs behave differently when they detect that stdin is being
piped. This can be problematic when these programs are used with the job
control API where stdin is attached, but not typically used. It is
possible to run the job using a PTY which circumvents this problem, but
that includes a lot of overhead when simply closing the stdin pipe would
suffice.
To enable this behavior, add a new parameter to the jobstart options
dict called "stdin" with two valid values: "pipe" (the default)
implements the existing behavior of opening a channel for stdin and
"null" which disconnects stdin (or, if you prefer, connects it to
/dev/null). This is extensible so that other modes can be added in the
future.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Check that `wip2` does not point to the same address as `wip`, to address the
Coverity test failure from PR #14884.
Based on the `if` clauses, `free_wininfo(wip2, ...)` is only called when
`wip2->wi_win == NULL` and `wip->wi_win == wp`. I think `wip2` would only point
to the same address as `wip` in scenarios where `wp` were `NULL`, which can be
assumed otherwise based on the earlier code.
|
| | |
|
|\ \
| | |
| | | |
Decrease reliance on curbuf in BUFEMPTY and `undo.c`
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Variables are set but not used.
Solution: Move the declarations to the block where they are used.
(closes vim/vim#8527)
https://github.com/vim/vim/commit/09f688c33aad9692276dfb68842cf0621a0e2002
|
| | |
| | |
| | |
| | |
| | | |
Problem: Garbage collection has useless code.
Solution: Bail out when aborting. (closes vim/vim#8504)
https://github.com/vim/vim/commit/20cc52832067d22a3cd47dfb0805251228c32e7d
|
| | | |
|
| | |
| | |
| | |
| | | |
#15015
|
|/ / |
|
| |
| |
| |
| | |
This assignment is informative/documenting though technically unnecessary.
https://github.com/neovim/neovim/pull/11900#discussion_r381860165 .
|
| |
| |
| |
| |
| | |
b_signcols_max isn't used to store the max value, it is use to
invalidate b_signcols.
|
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: Crash when using "quit" at recovery prompt and autocommands are
triggered.
Solution: Block autocommands when creating an empty buffer to use as the
current buffer. (closes vim/vim#8506)
https://github.com/vim/vim/commit/1d97efce0ce31ddf0dd4c1ae2228ef4caee6880c
|
| |
| |
| |
| |
| |
| | |
Problem: tablabel_tooltip test fails with Athena. (Dominique Pellé)
Solution: Skip the test when using Athena. (closes vim/vim#8508)
https://github.com/vim/vim/commit/fb773a3e0aa9466bb953c29bad0bf4ba34461a40
|
| |
| |
| |
| |
| |
| |
| | |
Problem: With 'virtualedit' set to "block" Visual highlight is wrong after
using "$". (Marco Trosi)
Solution: Do not set w_old_cursor_lcol to MAXCOL. (closes vim/vim#8495)
https://github.com/vim/vim/commit/9cee4a1c9c69542ccd73bcd2db05920150856361
|
| |
| |
| |
| |
| |
| | |
Problem: Gemtext files are not recognized.
Solution: Recognize .gmi and .gemini files. (closes vim/vim#8427)
https://github.com/vim/vim/commit/fcde67c99fbb6d7294e01b9e87d8d2ae7af31255
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: JSONC files are not recognized.
Solution: Recognize .jsonc files. (Izhak Jakov, closes vim/vim#8500)
https://github.com/vim/vim/commit/acbb4b5720fc27b8b07357b763ed4e5a944ae1da
N/A patches for version.c:
vim-patch:8.2.3081: cannot catch errors in a channel command
Problem: Cannot catch errors in a channel command.
Solution: Instead of skipping the error make it silent. (closes vim/vim#8477)
https://github.com/vim/vim/commit/11a632d60bde616feb298d180108819ebb1d04a0
vim-patch:8.2.3082: a channel command "echoerr" does not show anything
Problem: A channel command "echoerr" does not show anything.
Solution: Do not use silent errors when using an "echoerr" command.
(closes vim/vim#8494)
https://github.com/vim/vim/commit/b836f631dba2534efd314a8f77439cebc75acd4e
vim-patch:8.2.3094: Test_popup_atcursor_pos() fails without the conceal feature
Problem: Test_popup_atcursor_pos() fails without the conceal feature.
Solution: Add a check for the conceal feature. (Dominique Pellé,
closes vim/vim#8505)
https://github.com/vim/vim/commit/c60e959cba03fae9cff9b2674fab646cc70819fc
vim-patch:8.2.3098: popup window test is flaky on MS-Windows with GUI
Problem: Popup window test is flaky on MS-Windows with GUI.
Solution: Skip the check in this situation.
https://github.com/vim/vim/commit/999db2346b61e6f6e6fde2d0b56f4646a46b727d
|
| | |
|
| |
| |
| |
| | |
long_u was a custom integer type that is no longer used.
More information can be found in https://github.com/neovim/neovim/issues/459.
|
| |
| |
| |
| |
| | |
The warning is triggered by the second division when arr is a char array
since sizeof(char) is 1. A modulo by 1 may normally indicate a logic
error, but in this case it's intended.
|
| | |
|
| | |
|
|\ \
| | |
| | | |
fix(api/win_get_config): include z-index
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
* Revert "tui: improve support for tmux, GNU Screen"
This reverts commit c266c2f36ea56220268d2b19364e28815e338c2f.
This commit broke neovim under tmux, where it "types" the background
string as input to the terminal. Fixing this with neovim as-is requires
changing tmux keybindings or TERM settings, which has to be done by
every single user, therefore a fix should happen on neovim's side.
Fixes #14298
* tui: fix code lints.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: The wininfo list may contain stale entries.
Solution: When closing a window remove any other entry where the window
pointer is NULL.
https://github.com/vim/vim/commit/4882d983397057ea91c584c5a54aaccf15016d18
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: The "zy" command does not work well when 'virtualedit' is set to
"block". (Johann Höchtl)
Solution: Make endspaces zero. (Christian Brabandt, closes vim/vim#8468,
closes vim/vim#8448)
https://github.com/vim/vim/commit/7d7bcc6ba01454c1cbb1dcbf5f11c3a4051535d6
N/A patches for version.c:
vim-patch:8.2.3075: xxd always reports an old version string
Problem: Xxd always reports an old version string. (Åsmund Ervik)
Solution: Update the version string with the last known change date.
(Jürgen Weigert, closes vim/vim#8475)
https://github.com/vim/vim/commit/80b2ba3e9602e09ab523e78946fbb26da311b68b
|