| Commit message (Collapse) | Author | Age |
|
|
|
| |
Instead, a note was added to `:h man.vim` on how 'fileignorecase'
controls the case sensitivity of completion.
|
|
|
|
|
|
| |
- Improves compatibility with shell=tcsh.
- man.vim: split read_page into get_page, put_page. Do not split the
window until we know there is going to be output.
|
| |
|
| |
|
| |
|
| |
|
|
|
| |
Closes #5763.
|
|
|
|
| |
Closes #5751
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- By re-enabling code blocks (every line that doesn't begin with a "-" and is
indented by at least 4 spaces), we prevent the Markdown syntax to evaluate "_"
as beginning for italic text.
That's the case for `:CheckHealth deoplete` for instance. It would output:
$ cat /tmp/log_{PID}
Since the deoplete check gets run first, almost all of the following
`:CheckHealth` output would be italic.
- Since we re-enable code blocks, we now have to tell our custom syntax that it
can be part of markdownCodeBlock as well. Otherwise there would be no
highlithing for our keywords ERROR, INFO, etc. after 4 spaces of indent.
- Since we do the above anyway, we make it work for mkdListItemLine as well.
That's a highlight group from `plasticboy/vim-markdown` opposed to the shipped
markdown syntax (which essentially is `tpope/vim-markdown`). Before this patch
there was no highlighting at all in the `:CheckHealth` output.
|
|
|
|
| |
This prevents the string "error" within error messages to be highlighted as
healthError.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This option simplifies the configuration options:
1) `g:python{,3}_host_prog` is not set.
Neovim tries its best to find a suitable interpreter. This means calling
exepath(), potentially multiple times, and a system('python -c ...') with
the first found interpreter, to get the Python version.
2) `g:python{,3}_host_prog` is set.
Avoids everything of the above. No safety checks, no training wheels. Fast
host startup time!
|
| |
|
|
|
|
| |
Fixes #5574
|
|
|
|
| |
Fixes #5628
|
|
|
|
| |
Compare numbers instead of strings.
|
|
|
|
|
|
|
|
|
|
| |
* health.vim: Include v:throwpoint in error message
* health/provider.vim: Check for ruby executable
* health/provider.vim: Combine subprocess stdout and stderr
* test: Updated CheckHealth test
|
|
|
|
|
|
|
|
| |
People using [1] would experience an error, because their markdown syntax
doesn't define the markdownCodeBlock group.
[1]: https://github.com/plasticboy/vim-markdown
Closes #5569
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We can now use help links like in normal help pages. The bars around them will
be concealed as well.
* Health: link string "SUCCESS" to ModeMsg
So far we linked "SUCCESS" to the Function highlight group.
The newly introduced healthHelp group links to Idenfifier as it does for links
in normal help pages.
Now the problem is that the Function group links again to Identifier as well, so
both, "SUCCESS" and help links, would use the same colors.
* Health: don't use Markdown code blocks
Every line indented by more than 4 spaces would lose its highlighting otherwise.
* Health: add helper health#help_to_link()
|
|
|
|
|
|
| |
Never throw an error when provider/clipboard.vim is sourced for the first time.
Save the error instead and expose it via `provider#clipboard#Error()`, mimicking
provider/python.vim.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
`:CheckHealth nvim` would always report an outdated manifest if symlinks were
used, because the manifest file contains unresolved paths that get compared
against resolved paths.
Now we resolve paths before they get written to the manifest file.
|
| |
|
| |
|
| |
|
|
|
|
| |
Closes #5435
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If multiple versions of a package are installed, the provider health check could
choose a wrong path:
/usr/local/lib/python3.5/site-packages/neovim-0.1.10-py3.5.egg-info/PKG-INFO
/usr/local/lib/python3.5/site-packages/neovim-0.1.9-py3.5.egg-info/PKG-INFO
Prior to this change :CheckHealth could falsely show 0.1.9 as the installed
version, since glob() doesn't enforce any predictable order.
Now we sort all potential paths numerically in descending order and just look at
the first path instead.
|
| |
|
|
|
|
|
| |
It's the same as the declaration above it, but hardcoded to use python3
and does not redirect stderr.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Also:
- improve precision of "No healthcheck found"
- fix SUGGESTIONS syntax group definition
- fix indentation of SUGGESTIONS
|
| |
|
|
|
|
|
|
|
|
| |
Compare current version number to that of the latest released neovim
rubygem, rather than a hard-coded version.
Note: The `gem list` command introduced here adds about 4 seconds to the
execution time of the CheckHealth command.
|
|
|
|
|
|
| |
- :Man with no arguments opens the manapage for the
<cWORD> (man buffers) or <cword> (non-man buffers).
- remove now irrelevent comment about -P flag
|
|
|
|
| |
Use system() instead of :read to avoid a hard redraw.
|
|
|
|
|
|
|
|
|
|
|
| |
- fix synopsis highlighting in other locales. Cannot always rely on the first
line for the section in some locales; instead, use the file path and
explicitly set b:man_sect to the actual section.
- eliminate separate s:man_args function
- simplify logic: do not reuse buffer content
- introduce b:man_default_sects Fixes #5233
- introduce <Plug>(man_vsplit), <Plug>(man_tab)
- simplify regexps
|
|\ |
|
| |
| |
| |
| |
| | |
The commit that added support for modifiers regressed #5168
causing #5172. This commit fixes it again.
|
| |
| |
| |
| | |
Addresses problem one in #5240
|
| |
| |
| |
| |
| |
| | |
This is necessary incase the buffer was previously opened in a different
tab, in which the window options there do not carry over. It is not
explicitly documented in ':help local-options' but that is how it works.
|
|/
|
|
| |
Closes #5235
|
|
|
|
|
|
|
| |
:silent does not silence this message, even :redir does not consume it.
But execute() _does_ consume it, which interferes with the current
implementation of health.vim. It's prudent to avoid it in any case, even
if the implementation of health.vim changes in the future.
|
|
|
|
|
|
|
|
|
| |
We can add this later if it is proven necessary, but it should not be
because:
1. User can run a subset of checkers via `:CheckHealth plugin1, ...,`
2. Healthcheck is a very rare operation. Optimizing it is not worth the
code/API complexity.
|