| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
|
| |
These had broken encodings, set it to UTF-8. All remianing Neovim
non-ASCII documentation files are UTF-8 encoded. And so are their Vim
original versions.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Co-Authored-By: Peter Lithammer <peter.lithammer@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
fix #11753
close #11781
The virtualenv troubleshooting in the Python provider health checks is
supposed to help the user determine whether running Python from Neovim
(as in `system('python')` or `system(exepath('python'))`) will use the
correct executable when a virtualenv is active. Currently however, it
issues spurious warnings in legitimate setups, and conversely, fails to
warn about potentially problematic ones.
See https://github.com/neovim/neovim/issues/11753#issuecomment-578715584
for a more detailed analysis, but at a high level, this is due to two
things:
- the virtualenv check is part of the Python provider check defined in
`s:check_python`, which uses a roundabout and sometimes erroneous way of
determining the Python executable
- more generally, it shouldn't be part of the provider check at all,
because it's not really related to the Python *provider*, i.e. the
Python executable which can communicate with Neovim via `pynvim`, but to
the Python the user is editing source files for, which typically
shouldn't even have `pynvim` installed
This patch reimplements the virtualenv check and factors it out into its
own separate function, which is however still kept in
`health/provider.vim` alongside the rest of the Python troubleshooting,
since troubleshooting all Python-related stuff in one place is probably
a good idea in order to alleviate any potential confusion (e.g. users
who run only provider checks might be left wondering whether their
virtualenv Python was properly detected if the report only shows their
global Python as the provider used by Neovim).
|
|
|
|
|
|
| |
Problem: Not recognizing .gv file as dot filetype.
Solution: Add *.gv to dot pattern. (closes vim/vim#5544)
https://github.com/vim/vim/commit/f8ddb25789a6af530e69f499907979dfbff1c1ea
|
|
|
|
|
| |
Problem: Kotlin files are not recognized.
Solution: Detect Kotlin files. (Alkeryn, closes vim/vim#5560)
https://github.com/vim/vim/commit/ab067a21b9622513ed75f4801b001606eeaf2474
|
|
|
|
|
|
| |
Problem: settagstack() cannot truncate at current index.
Solution: Add the "t" action. (Yegappan Lakshmanan, closes vim/vim#5417)
https://github.com/vim/vim/commit/271fa08a35b8d320d3a40db4ddae83b698fdd4fb
|
|
|
|
|
| |
instead of the content of the file at this line.
ref https://github.com/neovim/nvim-lsp/issues/69
|
|\
| |
| | |
vim-patch:8.2.{152,158}
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Triggering CompleteDone earlier is not backwards compatible.
(Daniel Hahler)
Solution: Add CompleteDonePre instead.
https://github.com/vim/vim/commit/3f169ce17e8b779d105c96138a8b4246f2d270b9
|
|/ |
|
|
|
|
|
|
|
|
|
| |
This makes it possible to restore the working directory of :terminal
buffers when reading those buffers from a session file.
Fixes #11288
Co-authored-by: Justin M. Keyes <justinkz@gmail.com>
|
|
|
|
|
| |
Problem: No swift filetype detection.
Solution: Add swift, swiftgyb and sil. (Emir Sarı, closes vim/vim#5517)
https://github.com/vim/vim/commit/0d76683e094c6cac2e879601aff3acf1163cbe0b
|
|\
| |
| | |
make jobstop() return 0 instead of throw error for already stopped job
|
| |
| |
| |
| |
| |
| | |
The return value of jobstop()
@return 1 for valid job id
0 for invalid id, including jobs have exited or stopped
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
Enable 'has("perl")' as an alias for 'g:loaded_perl_provider'.
TODO:
- +perl interface
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
|
| |
- test: reduce verbosity, condense redundancy, improve readability
- auevents.lua: keep events sorted by name. ref afd1d412fa91
|
|
|
|
|
|
| |
- only fire once, just before freeing mem
- trigger when on a different buffer
- avoid recursive calls in another tab
|
|
|
|
|
|
| |
Problem: complete_info() does not work when CompleteDone is triggered.
Solution: Trigger CompleteDone before clearing the info.
https://github.com/vim/vim/commit/17e04781f26c24769e202351c194ee252927eee1
|
| |
|
|
|
|
|
| |
"│" U+2502 BOX DRAWINGS LIGHT VERTICAL
Fallback to old default | if 'ambiwidth' is set.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The old `:Man` implementation would take either the word under
the cursor, or the argument passed in, and load that as a man page.
Since we now use 'tagfunc' and look for all relevant man-pages, if
your system has several (i.e. same name, different sections), we return
several, giving the user an option.
This works for most tag commands except `:tjump`, which will
fail if there's multiple tags to choose from. This just happens to
be what the cscope code uses (it actually attempts to prompt the
user, but this fails).
|
|
|
|
|
|
| |
Problem: The Normal highlight is not defined when compiled with GUI.
Solution: Always define Normal. (Christian Brabandt, closes vim/vim#4072)
https://github.com/vim/vim/commit/f90b6e03a983b62b66564fc449e32724d6456769
|
|
|
|
| |
Make the hover window position itself vertically wherever is the most
space available.
|
|
|
|
|
| |
stderr is needed to get error messages in case of failure, and
job handler expects it to be open.
|
|
|
|
|
|
|
|
|
| |
In a multi-window scenario, it is possible to return focus to the last
accessed window via n_CTRL-W_p. However, in the case of a multi-tab
scenario, there was previously no way to return focus to the last
accessed *tab*. Here, that ability is added via n_g<tab>.
Additionally, the index of the previous tab is exposed via
tabpagenr('#'), mirroring the existing functionality of winnr('#').
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
test_registers.vim can fail even if a clipboard manager is running.
If a clipboard manager is not running, this test always fails with xclip.
Use xsel as a workaround.
https://github.com/astrand/xclip/issues/20 suggests closing stdout
when sending input via stdin.
Environment
- Ubuntu Xenial
- Vim 7.4 (any app with broken clipboard code will do)
- Neovim nightly
Steps to reproduce:
0. Start the clipboard manager.
1. Open a file in Vim on Linux.
Vim should have +clipboard enabled.
'set clipboard='
2. Yank some text to the clipboard register.
3. Quit Vim.
4. Run 'cd /path/to/neovim/repo/'
5. Run 'make oldtest'.
Do not run any individual tests.
They likely pass with or without this fix.
Before fix: test_registers.vim can fail.
After fix: test_registers.vim always passes.
Close https://github.com/neovim/neovim/issues/7958
https://wiki.ubuntu.com/ClipboardPersistence#The_state_of_things
|
|
|
|
|
|
| |
Any uses of `has("python3")` will cause the `g:loaded_python3_provider`
variable to be set if the system path does not have a Python with Neovim
support. Subsequent assignments to `g:python3_host_program` will
therefore not cause the provider to be activated.
|
|\
| |
| | |
metatable for empty dict value
|
| | |
|
|/
|
|
|
|
| |
Problem: Python 3 unicode test someitmes fails.
Solution: Make 'termencoding' empty. Correct number of error message.
https://github.com/vim/vim/commit/4b7cdca23035eacf6cd0e30b90546cf32f7efe9e
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
Reduce API surface. We should not add functions unless they are really
needed. Users should be nudged to use vim.inspect() directly.
|
| |
| |
| |
| |
| |
| | |
Reduce API surface. We don't need so many variations of functions. Too
many functions means verbose, largely redundant documentation, tests,
and cognitive burden.
|
| | |
|
| | |
|
|/ |
|
| |
|