1. 01 Jan, 2019 1 commit
  2. 20 Nov, 2018 2 commits
  3. 17 Nov, 2018 1 commit
  4. 28 Jul, 2018 2 commits
  5. 24 Jun, 2018 1 commit
  6. 17 Jun, 2018 1 commit
  7. 10 Jun, 2018 1 commit
  8. 30 Apr, 2018 3 commits
  9. 04 Mar, 2018 1 commit
    • Daniel Hahler's avatar
      health/provider: python: warning with correct host prog (#8049) · 1d5eec2c
      Daniel Hahler authored
      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 (20447ba0), 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
      ```
      1d5eec2c
  10. 22 Feb, 2018 3 commits
    • Daniel Hahler's avatar
      health/provider: check Python also with loaded_var (#8047) · 830b5819
      Daniel Hahler authored
      `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.
      830b5819
    • Daniel Hahler's avatar
      checkhealth: python: do not report pythonx_errs twice (#8045) · 1eb4aff5
      Daniel Hahler authored
      They get reported unconditionally as errors below.
      1eb4aff5
    • Daniel Hahler's avatar
      c8074e37
  11. 07 Feb, 2018 1 commit
  12. 31 Jan, 2018 1 commit
  13. 29 Dec, 2017 1 commit
  14. 27 Dec, 2017 1 commit
  15. 17 Dec, 2017 4 commits
  16. 16 Nov, 2017 1 commit
  17. 29 Oct, 2017 1 commit
  18. 09 Sep, 2017 1 commit
    • Greg Anders's avatar
      health.vim: always check pyenv if installed #7219 · 7c00b10d
      Greg Anders authored
      Always check for the presence of pyenv_root if pyenv is installed: if it
      is not set, we don't know if it was intentional. If it wasn't
      intentional, the warning is confusing (see #7176).
      
      closes #7176
      7c00b10d
  19. 20 Aug, 2017 1 commit
    • Justin M. Keyes's avatar
      clipboard: avoid error flood during :redir · 9882e25d
      Justin M. Keyes authored
      redir_write():
      - This is a "batch" operation which was not yet covered by
        start_batch_changes()
      
      adjust_clipboard_name():
      - msg() and friends during :redir will, of course, cause redir_write()
        to try to capture that message, which causes recursion.
      - EMSG() here is trouble: if it interrupts :redir it is a mess.
        Rather than deal with the mess, show a non-error message.
      
      closes #7182
      closes #7184
      closes #7183
      ref #6048
      ref #7032
      9882e25d
  20. 15 Jul, 2017 1 commit
  21. 17 Jun, 2017 1 commit
  22. 11 May, 2017 2 commits
  23. 28 Apr, 2017 2 commits
  24. 20 Apr, 2017 1 commit
  25. 19 Apr, 2017 1 commit
  26. 27 Mar, 2017 1 commit
  27. 13 Feb, 2017 2 commits
  28. 12 Feb, 2017 1 commit