| Commit message (Collapse) | Author | Age |
... | |
|\ \ \
| | | |
| | | |
| | | |
| | | | |
This will allow us to reuse the parsing logic elsewhere, namely for
'inccommand' logic, so we don't need to duplicate it for changes such as the
repeated colon fix in #11319.
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This will allow us to reuse the parsing logic elsewhere,
namely for inccommand logic.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: Parsing Ex address range is not a separate function.
Solution: Refactor do_one_cmd() to separate address parsing.
https://github.com/vim/vim/commit/ee8415bc5998792fab6f4dcf289d027856e05b89
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Implements textDocument/formatting, textDocument/rangeFormatting,
workspace/applyEdit.
TODO:
- still has edge cases around replacement probably. Only tested with
inserts on the same position.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
This allows default_callbacks to be specified after client creation to
be considered. Also it simplifies the code.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
- Rename builtin_callbacks to default_callbacks and slightly change its
semantics:
- No longer contains the default implementations. Instead, any
default_callbacks will be used in preference for our .buf methods.
- Add this to the docs.
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
- Return after an error in RPC.
- Use an empty vim table for serialization.
|
| | | |
| | | |
| | | |
| | | | |
Don't modify your inputs.
|
| |_|/
|/| |
| | |
| | |
| | |
| | | |
If the preview is just a code block, then use the language as the
filetype instead of using markdown.
This reduces the size of the preview.
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes LuaJIT build on macOS Catalina.
ref https://github.com/LuaJIT/LuaJIT/issues/521
ref https://github.com/Homebrew/homebrew-core/pull/46823
|
| | |
| | |
| | |
| | |
| | | |
Python 3.8 was released 2019-10-14:
https://www.python.org/dev/peps/pep-0569
|
|\ \ \
| | | |
| | | | |
vim-patch:8.1.{1922,2289,2305}
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: No warning for wrong entry in translations.
Solution: Check semicolons in keywords entry of desktop file.
https://github.com/vim/vim/commit/e53ec39270c805a95e405812e4c463c87a150eda
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: After :diffsplit closing the window does not disable diff.
Solution: Add "closeoff" to 'diffopt' and add it to the default.
https://github.com/vim/vim/commit/c8234779790dd873acb88331c50988adf94cc383
|
| | | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: In diff mode global operations can be very slow.
Solution: Do not call diff_redraw() many times, call it once when redrawing.
And also don't update folds multiple times.
https://github.com/vim/vim/commit/4f57eefe1e84b5a90e08474092ea6fc8825ad5c9
|
|/ / /
| | |
| | |
| | |
| | | |
* Display ✓ or ✗ based on the line user sees
* Add vim-tutor-mode expectations to the lines marked with an arrow.
* Fix some existing expectations to behave predictably.
|
|\ \ \
| | | |
| | | | |
v:lua and better error messages for vimL->lua
|
|/ / /
| | |
| | |
| | | |
Also simplify error messages when calling lua from vimL.
|
|\ \ \
| | | |
| | | | |
extmark: do not crash in read-only buffer
|
| | | | |
|
| | | | |
|
|/ / /
| | |
| | |
| | |
| | |
| | | |
Problem: A :normal command while executing a register resets the
reg_executing() result.
Solution: Save and restore reg_executing. (closes vim/vim#4066)
https://github.com/vim/vim/commit/cce713ddcc0c9ab29926c28e287cbb587a959b08
|
|\ \ \
| | | |
| | | | |
vim-patch:8.1.{927,2293}
|
| | | |
| | | |
| | | |
| | | |
| | | | |
https://neovim.io/doc/reports/clang/report-487b01.html#EndPath
https://neovim.io/doc/reports/clang/report-ce4c3c.html#EndPath
|
| | | |
| | | |
| | | |
| | | | |
Cherry-picked from vim patch 8.1.1489.
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: USE_CR is never defined.
Solution: Remove usage of USE_CR. (Ken Takata, closes vim/vim#3958)
https://github.com/vim/vim/commit/00590740081489db69f43d9f1c0e3f70e29ce6da
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: Join adds trailing space when second line is empty. (Brennan
Vincent)
Solution: Do not add a trailing space.
https://github.com/vim/vim/commit/cc184cfb09161b3bbc7d5d8859a18e812367d19c
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Multiple Debian builds were failing these tests:
Failures:
From test_environ.vim:
Found errors in Test_external_env():
function RunTheTest[37]..Test_external_env line 16: Expected '' but got 'FOO=null\n'
Found errors in Test_getenv():
function RunTheTest[37]..Test_getenv line 2: Expected v:null but got v:false
Found errors in Test_setenv():
function RunTheTest[37]..Test_setenv line 5: Expected v:null but got 'null'
This is because nvim has a separate tag (`v_special`) in `typval_T` for
special variables, whereas vim re-uses the `v_number` tag.
On little-endian architectures, using the incorrect tag is not an issue
because the byte representation is the same. However, on big-endian
systems this caused the `v_number == kSpecialVarNull` checks to fail,
and the non-special code to execute.
|
| | |
| | |
| | |
| | |
| | |
| | | |
Mainly configuration and RPC infrastructure can be considered "done". Specific requests and their callbacks will be improved later (and also served by plugins). There are also some TODO:s for the client itself, like incremental updates.
Co-authored by at-tjdevries and at-h-michael, with many review/suggestion contributions.
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | | |
The spelling "Extmark" is used almost everywhere, so don't spell it
"ExtMark" inconsistently.
|
| | | | |
|
|/ / / |
|
|\ \ \ |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: scripts/gen_vimdoc.py gets confused and tries to generate docs
for `fn_index` and `func`.
Solution: Rename them to be private.
|