| Commit message (Collapse) | Author | Age |
|
|
| |
* preserve fields from LSP diagnostics via adding a user_data table to the diagnostic, which can hold arbitrary data in addition to the lsp diagnostic information.
|
|
|
|
|
|
|
|
| |
This fixes the handler signature and also prevents n+1 requests firing
if there are multiple clients.
(The first `prepareCallHierarchy` handler is called once per client,
each invocation used `buf_request` to make more requests using *all*
clients)
|
| |
|
|
|
|
|
|
| |
- main.c: remove os_setenv("MYVIMRC",…), it is already done by
do_source().
- This also sets $MYVIMRC to a full (absolute) path.
- code cleanup.
|
|\
| |
| | |
build: enhance Makefile
|
|/
|
|
|
|
|
| |
- fix regression where `-j` is not passed to ninja
(39c886551bf8323b63938f5dee5beb650c61f02b, #15708)
- enable to pass `-l` (load) to ninja as well
- s/BUILD_TYPE/CMAKE_GENERATOR/
|
|\
| |
| | |
build: Add ${CMAKE_THREAD_LIBS_INIT} to LIBUV_LIBRARIES
|
|/
|
|
|
|
|
| |
This is a workaround for not yet having fully correct Find* cmake
modules for static builds.
https://github.com/Tronic/cmake-modules/issues/3#issuecomment-624469020
|
|
|
|
|
|
| |
Some parts of LSP need to use cached diagnostics as sent from the LSP
server unmodified. Rather than fixing invalid line numbers when
diagnostics are first set, fix them when they are displayed to the user
(e.g. in show() or one of the get_next/get_prev family of functions).
|
|
|
|
| |
* fix function parameter comments
* remove space after star in function names
|
|
|
|
|
|
|
|
| |
Since the `State` is global, other scripts are unexpectedly affected during the
'inccommand' preview. This commit introduces a new flag for `do_cmdline`, in
order to ignore trailing '|'-separated commands only for the command invoking
the preview.
fix #8796, update #7494
|
| |
|
|\ |
|
| | |
|
|/ |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Changes to the main Makefile:
- add `MAKEFILE_PATH` and `MAKEFILE_DIR` that are set with native commands
- add `NVIM_PRG`
- rename `BUILD_TYPE` to `CMAKE_GENERATOR` to align with CMake naming
- remove the misleading `BUILD_CMD` and use `BUILD_TOOL` instead
Add the following phony target to quickly test the changes
```make
debug-print:
@echo makefile path: $(MAKEFILE_PATH)
@echo makefile dir: $(MAKEFILE_DIR)
@echo build dir: $(BUILD_DIR)
@echo cmake generator tool: $(CMAKE_GENERATOR)
@echo build-tool: $(BUILD_TOOL)
@echo nvim-prg: $(NVIM_PRG)
```
|
|
|
|
|
|
| |
* feat(diagnostic): add vim.diagnostic.match()
Provide vim.diagnostic.match() to generate a diagnostic from a string and
a Lua pattern.
* feat(diagnostic): add tolist() and fromlist()
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Example test failure:
$ nvim -es +"lua require('scripts.lintcommit')._test()"
[ FAIL ]: expected=true, got=false
input: ":no type before colon 1"
[ FAIL ]: expected=true, got=false
input: "ci: tab after colon"
Example main({trace=true}) output:
$ nvim -es +"lua require('scripts.lintcommit').main()"
run: { "git", "branch", "--show-current" }
run: { "git", "merge-base", "origin/master", "master" }
run: { "git", "merge-base", "upstream/master", "master" }
run: { "git", "rev-list", "89db07556dbdce97c0c150ed7e47d80e1ddacad3..master" }
run: { "git", "show", "-s", "--format=%s", "d2e6d2f5fc93b6da3c6153229135ba2f0b24f8cc" }
Invalid commit message: "buildlint): commit linter #15620"
Commit: d2e6d2f5fc93b6da3c6153229135ba2f0b24f8cc
Invalid commit type "buildlint)". Allowed types are:
{ "build", "ci", "docs", "feat", "fix", "perf", "refactor", "revert", "test", "chore", "vim-patch" }
See also:
https://github.com/neovim/neovim/blob/master/CONTRIBUTING.md#commit-messages
https://www.conventionalcommits.org/en/v1.0.0/
|
|\
| |
| | |
vim-patch:8.1.{1071,1078,1079,1110},8.2.{2640,3424,3425,3437}
|
| |
| |
| |
| |
| |
| | |
Problem: Compiler warnings for 32/64 bit usage.
Solution: Add type casts. (Mike Williams, closes vim/vim#8870)
https://github.com/vim/vim/commit/f5785cf0592626ec17676e814d3ba58f5123bcda
|
| |
| |
| |
| |
| |
| | |
Problem: Warning for using uninitialized variable.
Solution: Initialize it. (John Marriott)
https://github.com/vim/vim/commit/56e14698b45a9c4ef8fa65c55c9bfe86fbb3d6bf
|
| |
| |
| |
| |
| |
| | |
Problem: A sequence of spaces is hard to see in list mode.
Solution: Add the "multispace" option to 'listchars'. (closes vim/vim#8834)
https://github.com/vim/vim/commit/f14b8ba1373f569705cb80419248054100b02360
|
| |
| |
| |
| |
| |
| | |
Problem: screenstring() returns non-existing composing characters.
Solution: Only use composing characters if there is a base character.
https://github.com/vim/vim/commit/f1387285e2ebe5cb3688d729fc6fd01a169a76c1
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Composing chars on space wrong when 'listchars' is set.
Solution: Do not use "space" and "nbsp" entries of 'listchars' when there is
a composing character. (Yee Cheng Chin, closes vim/vim#4197)
https://github.com/vim/vim/commit/e5e4e22c1c15c8c22b14935affe969569acc8df9
|
| |
| |
| |
| |
| |
| | |
Problem: No need for a separate ScreenLinesUtf8() test function.
Solution: Get the composing characters with ScreenLines().
https://github.com/vim/vim/commit/48aed0824e47147faf19fc235ad4bcf851584c9c
|
| |
| |
| |
| |
| |
| |
| | |
Problem: When 'listchars' is set a composing char on a space is wrong.
Solution: Separate handling a non-breaking space and a space. (Yasuhiro
Matsumoto, closes vim/vim#4046)
https://github.com/vim/vim/commit/5f8069bbf5d989936a2f4d7a76ae42434017e3a2
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Cannot get composing characters from the screen.
Solution: Add screenchars() and screenstring(). (partly by Ozaki Kiichi,
closes vim/vim#4059)
https://github.com/vim/vim/commit/2912abb3a2fd72074e3901c8ae1d4a77ce764675
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
|
|
|
| |
Problem
- `redir_exec` is obsolete, but it keeps getting used in new tests
because people copy existing tests.
- Disadvantages of `redir_exec`:
- Captures extra junk before the actual error/message that we _want_ to test.
- Does not fail on error, unlike e.g. `command()`.
Solution
- Use new functions like `nvim_exec` and `pcall_err`.
|
|
|
|
|
| |
When vim.diagnostic.config() is called, the decorations for diagnostics
are re-displayed to use the new configuration. This should only be done
for loaded buffers.
|
| |
|
|
|
|
|
| |
- Fix the cursor position after applying TextEdits
- Support reversed range of TextEdit
- Invoke nvim_buf_set_text one by one
|
|\
| |
| | |
fix(diagnostic): resolve nil bufnr in show_line_diagnostics
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
(#15547)
Problem: Filler lines are wrong when changing text in diff mode.
Solution: Don't change the filler lines on every change. Check
scrollbinding when updating the filler lines. (closes vim/vim#8809)
https://github.com/vim/vim/commit/04626c243c47af91c2580eaf23e12286180e0e81
|
|/ |
|
|\
| |
| | |
runtime: always use DIP_START and remove duplication of start packages in &rtp
|
| |
| |
| |
| |
| |
| |
| |
| | |
The order should be:
XDG_CONFIG_HOME/nvim
XDG_DATA_HOME/nvim/site/pack/foo/start/bar/
XDG_CONFIG_HOME/nvim/after
XDG_DATA_HOME/nvim/site/pack/foo/start/bar/after
|
|/
|
|
|
|
|
|
| |
Now remove the addition of "start/*" packages in 'packpath' as
explicit items in 'runtimepath'. This avoids 'runtimepath' from becoming
very long when using a lot of plugins as packages.
To get the effective search path as a list, use |nvim_list_runtime_paths()|
|
|\ |
|
| |
| |
| |
| |
| | |
vim.diagnostic._set_signs doesn't return anything, so checking the
return value will always fail.
|
| | |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
When severity_sort is true, higher severities should be displayed before
lower severities (e.g. ERROR is displayed over WARN).
Also improved the test case for this.
|
|/ |
|
|\
| |
| | |
Diagnostic hot fixes
|
| | |
|