aboutsummaryrefslogtreecommitdiff
path: root/runtime/autoload
Commit message (Collapse)AuthorAge
...
* vim-patch:20aac6c11269Justin M. Keyes2018-10-29
| | | | | Update runtime files. https://github.com/vim/vim/commit/20aac6c1126988339611576d425965a25a777658
* vim-patch:fc65cabb15d0Justin M. Keyes2018-10-29
| | | | | | | | | | | | Update runtime files. https://github.com/vim/vim/commit/fc65cabb15d0236bce001ad78e12a40511caf941 --- vim-patch:8.0.1279: initializing menus can be slow Problem: Initializing menus can be slow, especially when there are many keymaps, color schemes, etc. Solution: Do the globbing for runtime files lazlily. (Ken Takata)
* vim-patch:91f84f6e11cdJustin M. Keyes2018-10-29
| | | | | Update runtime files. https://github.com/vim/vim/commit/91f84f6e11cd879d43d651c0903d85bff95f0716
* vim-patch:a9604e614517Justin M. Keyes2018-10-29
| | | | | Update runtime files. https://github.com/vim/vim/commit/a9604e61451707b38fdcb088fbfaeea2b922fef6
* vim-patch:6dc819b1299eJustin M. Keyes2018-10-29
| | | | | Updated runtime and language files. https://github.com/vim/vim/commit/6dc819b1299e1d9f99303568772ade544d5c1322
* vim-patch:0b0f0992d46eJustin M. Keyes2018-10-29
| | | | | Update runtime files. https://github.com/vim/vim/commit/0b0f0992d46ef02fdfc1240744bef91d4299c1df
* vim-patch:7db25fed5de1Justin M. Keyes2018-10-29
| | | | | Update runtime files. https://github.com/vim/vim/commit/7db25fed5de1be922b8cbb0328149469606a0424
* vim-patch:f0b03c4e98f8Justin M. Keyes2018-10-28
| | | | | | | Update runtime files https://github.com/vim/vim/commit/f0b03c4e98f8a7184d8b4a5d702cbcd602426923 Note: haskell changes were included in 942f3587c38a83cf6486a0b779765b54a1648493
* man.vim: lowercase title when invoked as $MANPAGERJustin M. Keyes2018-10-26
| | | | | | | | man#init_pager() guesses the ref by the heading, which is usually uppercase, so we don't know the correct casing. But lowercase is more common, so use that for the buffer name instead of uppercase. ref #9156
* man.vim: avoid duplicate buffers, E95Justin M. Keyes2018-10-25
| | | | | | | | | | | | | | | | | | | | Before this commit, man#init_pager() always tries to scrape the manpage name and set the buffer name. That's much less important than avoiding duplicate buffers and E95. And it doesn't seem to be necessary, usually. Steps to reproduce: $ export MANPAGER="nvim -c 'set ft=man' -" $ man sleep :Man sleep Error detected while processing function man#init_pager: line 15: E95: Buffer with this name already exists :ls! 1 h- "man://SLEEP(1)" line 4 2 %a- "man://sleep(1)" line 1
* provider/nodejs: fix npm,yarn detectionJan Edmund Lazo2018-10-22
| | | | | | | | | | For each package manager, 1. Check if they are executable before starting a job. 2. Check if the job opts are set before checking the job status TODO: Validate the job id. Prioritize npm because it's faster than yarn. Reindent the code to 2-space indent.
* provider/nodejs: Simultaneously query npm and yarn #9054Mahmoud Al-Qudsi2018-10-18
| | | | | | ref #9001 Instead of serially querying npm and yarn for neovim, start both as a job and then wait for a successful result from either.
* man.vim: set $MANWIDTH=999Justin M. Keyes2018-09-30
| | | | | | | | On some systems, mandoc disallows $MANWIDTH greater than 1000. E.g. FreeBSD: https://github.com/freebsd/freebsd/blob/b7d613ae8a2fc1530d33aff53a1a678d284bfeec/contrib/mandoc/manpath.c#L312 closes #9065
* man.vim: Start at the top #9023Justin M. Keyes2018-09-27
| | | | fixes #9057
* man.vim: Fix very long justified lines #9023Justin M. Keyes2018-09-21
| | | | | | | | | | | When nroff justifies a line, it fills the line with whitespace to meet $MANWIDTH. With $MANWIDTH=9999, that of course results in nonsense (and behaves poorly with 'cursorline' option). To work around that, instead of trying to hard-justify the lines, just replace the mega-whitespace with a fixed size of 10 spaces. Perhaps N/Vim needs a "soft justify" feature?
* man.vim: Ignore $MANWIDTH, use soft wrap #9023Doron Behar2018-09-21
| | | | | fix #9017 close #9023
* runtime/msgpack: Fix inf/nan regexpZyX2018-09-06
| | | | | Not making minus sign optional as inf/nan without optional minus should’ve already been handled by the very first case.
* man.vim: guard against reload (#8940)dm1try2018-09-01
| | | | | | Some plugins attempt to reload autoloaded scripts. Use a guard to prevent this. fix #8939
* health.vim: Detect missing init.vimJustin M. Keyes2018-08-27
| | | | closes #4877
* remote/host.vim: specify {nosuf} for globpath() (#8882)Justin M. Keyes2018-08-24
|
* tutor: don't set statusline (#8844)Felipe Morales2018-08-10
| | | | | also, remove unused function tutor#InfoText() fixes #8842
* ruby: detect rbenv shims for other versions (#8733)Marco Hinz2018-08-09
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When rbenv is used for managing Ruby installations, just checking for an executable called "neovim-ruby-host" is not enough. It has to be run as well. If it does not return 0, then neovim-ruby-host is merely a shim for another Ruby installation. $ rbenv versions 2.5.0 * 2.5.1 (set by /Users/mhi/.rbenv/version) $ rbenv whence neovim-ruby-host 2.5.0 $ which neovim-ruby-host /Users/mhi/.rbenv/shims/neovim-ruby-host $ neovim-ruby-host rbenv: neovim-ruby-host: command not found The `neovim-ruby-host' command exists in these Ruby versions: 2.5.0 $ echo $? 127 Additionally, the detection logic was moved from provider#ruby#Detect() to s:detect(), because the former is run in the sandbox which forbids calling system().
* checkhealth: always report stderr with errors (#8783)Daniel Hahler2018-07-29
| | | This also reports the exit code (e.g. 127 for when pyenv-which fails).
* checkhealth: do not use exepath with host_prog (#8784)Daniel Hahler2018-07-29
| | | | | | | | | | This would need to get `expand`ed to not become empty, and is being handled by s:check_bin already. `s:check_bin` will also complain about e.g. "~/.pyenv/versions/3.6.6/bin/python" not being executable, but that reflects that the host will fail to start with it. Fixes #8778
* man.vim: fix for mandoc (#8698)Brayden Banks2018-07-08
| | | | | When giving a section, the first candidate selection was not performed. followup/fixup #8341
* provider/node: npm --loglevel silent (#8682)Takuya Matsuyama2018-07-04
| | | | closes #8674 npm log level may cause unexpected output.
* checkhealth: Python: fix VIRTUAL_ENV check (#8628)Daniel Hahler2018-06-24
| | | | | Compare `$VIRTUAL_ENV` to `python_bin`. This is necessary when `g:python_host_prog` is set to an absolute path, and looking up `pyname` in `$PATH` yields another result.
* checkhealth: node.js: also search yarn #8528Ahmed El Gabri2018-06-17
| | | | | - "neovim" package may be installed with yarn. Check yarn if npm fails. - Use filereadable() instead of glob(). closes #8552
* checkhealth: fix nodejs provider advice (#8522)Colin Yates2018-06-10
| | | closes #8515
* Merge #8371 'API: more reliable/descriptive VimL errors'Justin M. Keyes2018-05-10
|\
| * msgpack.vim: require python3 on WindowsJustin M. Keyes2018-05-10
| | | | | | | | | | | | timestamp.strftime('%s') workaround only works on unix. ref: https://github.com/neovim/neovim/pull/8371#discussion_r186311766
| * msgpack.vim: fix syntax errors, python2 errorsJustin M. Keyes2018-05-09
| |
* | man.vim: s:get_path(): trim newline in all casesJustin M. Keyes2018-05-10
| | | | | | | | ref #8372
* | man.vim: get() first item if -w returns multiple paths #8372Jon Bernard2018-05-10
|/ | | | | | | | | OpenBSD's man returns all candidates when searching with -w instead of the first one it finds. So this patch takes the first one if multiple entries are found. closes #8372 closes #8341
* health#provider: fix sys.path for PythonDaniel Hahler2018-04-30
| | | | | | | 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 reportingDaniel Hahler2018-04-30
| | | | | - quote command, so that e.g. markdown handling is not applied to `__init__.py` - include cwd
* health#provider: fix logic with s:shellifyDaniel Hahler2018-04-30
| | | | | It should be quoted if there is any character that needs escaping, but not if there is a character that does not need escaping.
* vim-patch:8.0.1285Justin M. Keyes2018-04-02
| | | | | | https://github.com/vim/vim/commit/d09a206ee94ccb653707ce9b6e536d4d58886e04 vim-patch:8.0.0564: cannot detect Bazel BUILD files on some systems
* vim-patch:8.0.1282Justin M. Keyes2018-04-02
| | | | | | | Problem: script-local variable defined in the wrong script Solution: Move variable to autoload/filetype.vim. https://github.com/vim/vim/commit/cef7322d8a902b4655ed861489c4e798672074f0
* vim-patch:8.0.1281Justin M. Keyes2018-04-02
| | | | | | | | | | | | Problem: Loading file type detection slows down startup. Solution: Move functions to an autoload script. https://github.com/vim/vim/commit/851ee6c3da5fd726d92e1e3300d7e5e2e8b907c5 --- vim-patch:8.0.0635 Problem: When 'ignorecase' is set script detection is inaccurate. Solution: Enforce matching case for text. (closes #1753)
* node/provider: support g:node_host_prog #8135chemzqm2018-03-15
|
* health/provider: python: warning with correct host prog (#8049)Daniel Hahler2018-03-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.vim: minor cleanup (#8046)Daniel Hahler2018-02-22
|
* health/provider: check Python also with loaded_var (#8047)Daniel Hahler2018-02-22
| | | | | | | | | | | | | | | `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)Daniel Hahler2018-02-22
| | | They get reported unconditionally as errors below.
* runtime/autoload/health/*.vim: fix vint warning (#8048)Daniel Hahler2018-02-22
|
* Add provider#Poll() to handle starting and polling the providerJames McCoy2018-02-16
|
* provider: Safely access job.stderr in #RequireJames McCoy2018-02-16
| | | | | | | | | | | | If `jobstart()` fails, then the subsequent `rpcrequest()` will throw due to an invalid channel id. This causes `job.stderr` not to exist, so we throw another exception when trying to dump the job's stderr. Error detected while processing function remote#define#AutocmdBootstrap[1]..remote#host#Require[10]..provider#pythonx#Require: line 22: E716: Key not present in Dictionary: stderr This obfuscates the actual problem.
* provider: ruby: Use stderr_buffered to collect stderrJames McCoy2018-02-16
|
* macOS: Use `pbpaste` to detect a working clipboard (#7983)Marco Hinz2018-02-08
| | | `pbcopy` writes to the clipboard, it should not be used to sanity-check the clipboard.
generated by cgit (git 2.34.1) at 2025-06-25 15:01:15 +0000