rneovim.git/runtime/autoload/health, branch v0.3.0

checkhealth: fix nodejs provider advice (#8522)

2018-06-10T18:09:10+00:00

closes #8515

health#provider: fix sys.path for Python

2018-04-30T14:54:35+00:00

Remove "" from sys.path (typically the first entry), which could cause
e.g. "logging" to be added from the current directory.
This gets done already for loading the host in
runtime/autoload/provider/pythonx.vim.

health#provider: improve error reporting

2018-04-30T14:50:01+00:00

- quote command, so that e.g. markdown handling is not applied to `__init__.py`
- include cwd

health#provider: fix logic with s:shellify

2018-04-30T14:48:32+00:00

It should be quoted if there is any character that needs escaping, but
not if there is a character that does not need escaping.

health/provider: python: warning with correct host prog (#8049)

2018-03-04T19:04:52+00:00

I have `g:python3_host_prog` set to the system Python, where a package
is also installed to provide the "neovim" module.

`:checkhealth provider` however displays a warning for this:

> Your virtualenv is not set up optimally.

This is because /usr/bin/python is not in /home/user/.pyenv.

I think this warning should not get displayed if host_prog_var exists.

It goes back to the initial commit (20447ba09), and is maybe only
missing the `!` there as with the previous commit.

Full output:
```
  - INFO: pyenv: /home/user/.pyenv/libexec/pyenv
  - INFO: pyenv root: /home/user/.pyenv
  - INFO: Using: g:python3_host_prog = "/usr/bin/python"
  - WARNING: Your virtualenv is not set up optimally (/usr/bin/python is not in /home/user/.pyenv).
    - ADVICE:
      - Create a virtualenv specifically for Neovim and use `g:python3_host_prog`.  This will avoid the need to install Neovim's Python module in each virtualenv.
  - WARNING: $VIRTUAL_ENV exists but appears to be inactive. This could lead to unexpected results.
    - ADVICE:
      - If you are using Zsh, see: http://vi.stackexchange.com/a/7654
  - INFO: Executable: /usr/bin/python
  - INFO: Python3 version: 3.6.4
  - INFO: python-neovim version: 0.2.1
  - OK: Latest python-neovim is installed: 0.2.1
```

health/provider: check Python also with loaded_var (#8047)

2018-02-22T01:38:00+00:00

`g:loaded_python3_provider` gets set when the autoload file is sourced,
but this might error out, e.g. with deoplete:

    [deoplete] Failed to load python3 host. You can try to see what happened by starting nvim with $NVIM_PYTHON_LOG_FILE set and opening the generated log file. Also, the host stderr is available in messages.
    [deoplete] function remote#define#FunctionBootstrap[1]..remote#host#Require[10]..provider#pythonx#Require[13]..provider#Poll, line 14
    [deoplete] deoplete requires Python3 support("+python3").
    [deoplete] deoplete failed to load. Try the :UpdateRemotePlugins command and restart Neovim.  See also :checkhealth.

It refers to `:checkhealth` from there explicitly, which would then
(without this patch) say that Python 3 is disabled.

This patch changes the reported info to include that it might have been
disabled due to some error, and keeps on going.

checkhealth: python: do not report pythonx_errs twice (#8045)

2018-02-22T01:37:23+00:00

They get reported unconditionally as errors below.

runtime/autoload/health/*.vim: fix vint warning (#8048)

2018-02-22T01:30:39+00:00

macOS: Use `pbpaste` to detect a working clipboard (#7983)

2018-02-07T23:27:54+00:00

`pbcopy` writes to the clipboard, it should not be used to sanity-check the clipboard.

clipboard: macOS: fallback to tmux if pbcopy is broken #7940

2018-01-31T10:37:05+00:00

On some versions of macOS, pbcopy doesn't work in tmux <2.6
https://superuser.com/q/231130
Fallback to tmux in that case.

Add a healthcheck for this scenario.