aboutsummaryrefslogtreecommitdiff
path: root/runtime
Commit message (Collapse)AuthorAge
* checkhealth: validate locale (#9548)Justin M. Keyes2019-01-26
| | | | | | Test case: LANG= LC_ALL= LC_CTYPE= tmux nvim -u NORC +'checkhealth nvim'
* Fix api doc nvim_buf_lines_event exampleChen Mulong2019-01-22
| | | | when send_buffer=true, the first nvim_buf_lines_event will come with lastline=-1 instead of 0.
* ui: multigrid mouse supportBjörn Linse2019-01-20
|
* lua/stdlib: Load runtime modules on-demandJustin M. Keyes2019-01-14
| | | | | | | | | | Instead of eager-loading during plugin/* sourcing, define runtime modules such as `vim.inspect` as lazy builtins. Otherwise non-builtin Lua modules such as `vim.inspect` would not be available during startup (init.vim, `-c`, `--cmd`, …). ref #6580 ref #8677
* lua/stdlib: vim.inspect, string functionsKillTheMule2019-01-14
| | | | | ref #6580 ref #8677
* Merge #9468 'checkhealth: detect broken pip"'Justin M. Keyes2019-01-11
|\
| * health/pythonx: handle "pip upgrade failure"Marco Hinz2019-01-07
| | | | | | | | Reference: https://github.com/neovim/neovim/wiki/Following-HEAD#20181118
| * health/pythonx: refactor #Detect()Marco Hinz2019-01-07
| |
| * health/pythonx: refactor pyenv checkMarco Hinz2019-01-07
| |
* | clipboard/macOS: assume that pbcopy works #9480Marco Hinz2019-01-10
| | | | | | Avoids ~30-60 ms startup cost for users of clipboard=unnamed.
* | vim-patch:8.1.0648: custom operators can't act upon forced motionPedro L. Ramos2019-01-10
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Custom operators can't act upon a forced motion. (Christian Wellenbrock) Solution: Add the forced motion to the mode() result. (Christian Brabandt, closes vim/vim#3490) https://github.com/vim/vim/commit/5976f8ff00efcb3e155a89346e44f2ad43d2405a closes #8667 closes #9476 Christian Wellenbrock: > For (most) built in text objects it's possible to force operation on > them to be linewise, for example by using `dVab` (`:h o_V`, > `motion_force`). When using custom text objects (defined as mappings > by plugins for example), this doesn't currently work. > > Example: > > onoremap x viw > > Open a file with a few lines each containing some words. With the > cursor on any word, try: > > 1. `dw` (builtin) deletes some characters > 2. `dVw` (builtin) deletes linewise > 3. `dx` (from mapping) deletes some characters > 4. `dVx` (from mapping) deletes some characters, but should delete > linewise ref: https://github.com/wellle/targets.vim/issues/214 ref: https://gitter.im/neovim/neovim?at=5b379ff7f1664406610e7483
* | build: fix `doc_html` targetJustin M. Keyes2019-01-04
| | | | | | | | ref 24f2cc55a83d #9430
* | Visual: highlight char-at-cursorJustin M. Keyes2019-01-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Decide whether to highlight the visual-selected character under the cursor, depending on 'guicursor' style: - Highlight if cursor is blinking or non-block (vertical, horiz). - Do NOT highlight if cursor is non-blinking block. Traditionally Vim's visual selection does "reverse mode", which perhaps conflicts with the non-blinking block cursor. But 'guicursor' defaults to a vertical bar for selection=exclusive, and this confuses users who expect to see the text highlighted. closes #8983
* | Merge pull request #9438 from jamessan/revert-pynvimJames McCoy2019-01-02
|\| | | | | Rework Python provider/health check to use neovim module again
| * health/provider: Check for available pynvim when neovim module missingJames McCoy2019-01-01
| | | | | | | | | | Adapt the checks so we can still report when the pynvim module is present but the neovim module is missing.
| * python#CheckForModule: Use the given module string instead of hard-coding pynvimJames McCoy2019-01-01
| |
| * {health,provider}/python: Import the neovim, rather than pynvim, moduleJames McCoy2019-01-01
| | | | | | | | | | | | | | | | The neovim module is available for backwards compatibility. We should not yet force the use of the pynvim module, since there's no other major reason to bump the minimum supported Python client module. Closes #9426
* | vim-patch:8.0.0251: not easy to select Python 2 or 3 (#9173)David Jimenez2019-01-02
| | | | | | | | | | | | Problem: It is not so easy to write a script that works with both Python 2 and Python 3, even when the Python code works with both. Solution: Add 'pyxversion', :pyx, etc. (Marc Weber, Ken Takata) https://github.com/vim/vim/commit/f42dd3c3901ea0ba38e67a616aea9953cae81b8d
* | cmake: runtime: use add_custom_command for tags directly (#9430)Daniel Hahler2019-01-01
| | | | | | | | | | | | | | | | | | | | This avoids generating the tags files all the time, and makes `make install` with `CMAKE_INSTALL_MESSAGE=LAZY` much more silent in general. Using `copy_if_different` instead of `remove` + `copy_directory` might be good on top, but is a) not really necessary anymore and b) would not sync removed files. For this `file(COPY` could be used, but would require to re-run cmake on changed input files then.
* | multigrid: doc updateBjörn Linse2018-12-31
| |
* | multigrid: Add multigrid documentationUtkarsh Maheshwari2018-12-31
|/
* appimage: Include metadata #9320pierre2018-12-30
| | | | | closes #9320 closes #9128
* syntax/vim.vim: highlight <cmd> keyJustin M. Keyes2018-12-30
|
* help: Do not highlight "Nvim."Justin M. Keyes2018-12-30
| | | | | This was added in 549311db7d400 for some reason, it usually just looks weird.
* doc: Remove {Nvim} tagJustin M. Keyes2018-12-30
| | | | | | | | | | | | The purpose of the {Nvim} hint was not well-defined, and its usage inconsistent. It's also unnecessary. Nvim-Vim differences are centralized at: :help vim-differences Removed things are centralized at: :help deprecated Developer guidelines for documentation are listed at: :help dev-doc
* docJustin M. Keyes2018-12-30
| | | | - CMake features
* rplugin.vim: Add migration support for Windows, nvim/ -> nvim-data/James McCoy2018-12-27
|
* Use stdpath() to determine rplugin manifest pathJames McCoy2018-12-20
|
* lintJustin M. Keyes2018-12-20
|
* runtime/lua/vim/compat.luaJustin M. Keyes2018-12-20
| | | | | | | | | | | | | | | | | | | | | ref #9280 Introduce the `vim.compat` module, to help environments with system Lua 5.2+ run the build/tests. Include the module implicitly in all tests. ref #8677 legacy `vim` module: beep buffer command dict eval firstline lastline line list open type window
* test: Lua 5.2/5.3 compat #9280Matěj Cepl2018-12-20
| | | | | Make the code run both on Lua 5.1 (which is the default for Neovim, and is what LuaJIT provides) and Lua 5.2+.
* startup: Use $XDG_CONFIG_DIRS/nvim/sysinit.vim if it existsJames McCoy2018-12-16
| | | | Closes #8994
* vim-patch:8.0.1445: cannot act on edits in the command lineBjörn Linse2018-12-12
| | | | | | | | Problem: Cannot act on edits in the command line. Solution: Add the CmdlineChanged autocommand event. (xtal8, closes vim/vim#2603, closes vim/vim#2524) https://github.com/vim/vim/commit/153b704e20f9c269450a7d3ea8cafcf942579ab7
* provider: repurpose E319Justin M. Keyes2018-12-12
| | | | | | | | | | | | | | In Vim (and some vestigial parts of Nvim) E319 was a placeholder for ex_ni commands, i.e. commands that are only available in certain builds of Vim. That is obviously counter to Nvim's goals: all Nvim commands are available on all platforms and build types (the remaining ex_ni commands are actually just missing providers). We need an error id for "missing provider", so it makes sense to use E319 for that purpose. ref #9344 ref #3577
* Merge #9306 'vim-patch: integrate xdiff library'Justin M. Keyes2018-12-09
|\ | | | | | | | | | | closes #1466 closes #1007 closes #1391
| * vim-patch:8.1.0397: no event triggered after updating diffsAnatolii Sakhnik2018-12-09
| | | | | | | | | | | | | | Problem: No event triggered after updating diffs. Solution: Add the DiffUpdated event. https://github.com/vim/vim/commit/e8fa05b5bc2d6d76bf5af50176a63655d00d1110
| * vim-patch:8.1.0360: using an external diff program is slow and inflexibleAnatolii Sakhnik2018-12-09
|/ | | | | | | | | | | | | | | | | | Problem: Using an external diff program is slow and inflexible. Solution: Include the xdiff library. (Christian Brabandt) Use it by default. https://github.com/vim/vim/commit/e828b7621cf9065a3582be0c4dd1e0e846e335bf vim-patch:8.1.0360 vim-patch:8.1.0364 vim-patch:8.1.0366 vim-patch:8.1.0370 vim-patch:8.1.0377 vim-patch:8.1.0378 vim-patch:8.1.0381 vim-patch:8.1.0396 vim-patch:8.1.0432
* doc (#9288)Justin M. Keyes2018-12-09
| | | | | - misc - doc: `:help config`. closes #9329 - cleanup test/README.md
* provider/lang: expand() g:foo_host_prog (#9312)Justin M. Keyes2018-12-05
| | | | | | | | | | Before this commit, if user does this: let g:node_host_prog = '~/.nvm/versions/node/v11.3.0/bin/neovim-node-host' the "~/" is not expanded to user's home directory. `:help g:ruby_host_prog` suggests a path with "~/" so technically we already claimed to support this. closes https://github.com/neovim/node-client/issues/102
* clipboard: Revert unused check #9309@equalsraf2018-12-04
| | | | | | | | | | | | | | | | PR #9304 added support for functions in clipboard providers. As part of the PR I meant to move two checks in the provider code out of an if statement into separate statements and adding additional checks for g:clipboard attributes - as it turns out the code is wrong and it does not implement additional checks while it adds two conditions that make very little sense type(g:clipboard['copy']) #isnot# v:t_func what would make sense would be something along the lines of type(g:clipboard['copy']['+']) #isnot# v:t_func but might not be what we want either, so I'm reverting this.
* RPC: turn errors from async calls into notificationsBjörn Linse2018-12-03
| | | | | Previously, nvim sent a response with invalid request id (UINT64_MAX). In functionaltests, catch unexpected error notifications in after_each().
* clipboard: Support custom VimL functions #9304Rui Abreu Ferreira2018-12-03
| | | | | | | | | | | | Up to now g:clipboard["copy"] only supported string values invoked as system commands. This commit enables the use of VimL functions instead. The function signatures are the same as in provider/clipboard.vim. A clipboard provider is expected to store and return a list of lines (i.e. the text) and a register type (as seen in setreg()). cache_enabled is ignored if "copy" is provided by a VimL function.
* clipboard: Prefer xclip (#9302)Justin M. Keyes2018-12-01
| | | | | | | | | | | The order was swapped in #4150 to prefer `xsel` but there wasn't a clear explanation. Meanwhile, `xsel` has been neglected upstream. Let's trying preferring `xclip` again, we've had a few reports of problems with `xsel`. closes #7237 ref #5853 ref #7449
* doc: deprecate inputdialog()Justin M. Keyes2018-12-01
| | | | | input() is functionally equivalent. GUI support for dialogs is implicit and does not depend on choosing inputdialog() vs input().
* VimL/confirm(): Show dialog even if :silentJustin M. Keyes2018-12-01
| | | | | closes #8788 related #9034
* vim-patch:8.1.0553: it is not easy to edit a script that was sourced (#9298)Jan Edmund Lazo2018-12-01
| | | | | | Problem: It is not easy to edit a script that was sourced. Solution: Add a count to ":scriptnames", so that ":script 40" edits the script with script ID 40. https://github.com/vim/vim/commit/07dc18ffa4e7ed202f219fe2fd3d6f58246f71f9
* matchit.vim: s:MultiMatch(): return DictJustin M. Keyes2018-11-28
|
* docJustin M. Keyes2018-11-28
| | | | | | | | | | - develop.txt is for design/guidelines; architecture/concepts should live elsewhere (currently src/nvim/README.md) - move dev-jargon to intro.txt - replace https://neovim.io/community (deprecated) with https://neovim.io/#chat - <Cmd> avoids CmdlineEnter/Leave https://github.com/vim/vim/issues/2889
* clipboard.vim: check for win32yank.exe #9263Bjorn Neergaard2018-11-21
| | | Win32 allows omitting the `.exe` extension, but WSL does not.
* Merge #9257 'health/python: warn if pynvim upgrade failed'Marco Hinz2018-11-20
|\ | | | | Reference: https://github.com/neovim/neovim/wiki/Following-HEAD#20181118