| Commit message (Collapse) | Author | Age |
| ... | |
| | |
| |
| |
| |
| |
| | |
- Any long symbol is intentional and should never be hardwrapped.
- Vim help tags are often hyphenated, and hardwrapping on hyphens breaks
the Vim help syntax parser.
|
| |/
|
|
|
|
|
|
|
|
|
|
| |
- Lua
- developer guidelines
- MAINTAIN.md
- TUI: cleanup
- TUI: mention Windows terminfo builtins
- cleanup if_pyth, redirect python-bindeval tag
Helped-by: Björn Linse <bjorn.linse@gmail.com>
Helped-by: erw7 <erw7.github@gmail.com>
|
| |
|
|
| |
when send_buffer=true, the first nvim_buf_lines_event will come with
lastline=-1 instead of 0.
|
| | |
|
| |
|
|
|
| |
ref #6580
ref #8677
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
| |
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
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
| |
- CMake features
|
| |
|
|
| |
Closes #8994
|
| |
|
|
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |\
| |
| |
| |
| |
| | |
closes #1466
closes #1007
closes #1391
|
| | |
| |
| |
| |
| |
| |
| | |
Problem: No event triggered after updating diffs.
Solution: Add the DiffUpdated event.
https://github.com/vim/vim/commit/e8fa05b5bc2d6d76bf5af50176a63655d00d1110
|
| |/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
| |
- misc
- doc: `:help config`. closes #9329
- cleanup test/README.md
|
| |
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
| |
Previously, nvim sent a response with invalid request id (UINT64_MAX).
In functionaltests, catch unexpected error notifications in after_each().
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
|
|
| |
input() is functionally equivalent. GUI support for dialogs is implicit
and does not depend on choosing inputdialog() vs input().
|
| |
|
|
|
| |
closes #8788
related #9034
|
| |
|
|
|
|
| |
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
|
| |
|
|
|
|
|
|
|
|
| |
- 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
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
By historical accident, Nvim defaults to background=light. So on a dark
background, `:colorscheme default` looks completely wrong.
The "smart" logic that Vim uses is confusing for anyone who uses Vim on
multiple platforms, so rather than mimic that, pick the (hopefully) most
common default.
- Since Neovim is dark-powered, we assume most users have dark backgrounds.
- Most of the GUIs tend to have a dark background by default.
ref #6289
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- TUI: _never_ rely on BCE for implicit clearing, only explicit commands.
- TUI: use unibi_erase_chars when possible.
- TUI: use end-exclusive ranges for invalid and cleared areas
- screen: scrolling leaves scrolled in aree undefined. This is a
conservative change, a client assuming the old semantics will still
behave correctly.
- screen: factor out vsep handling from line drawing. This is needed
anyway for the multigrid refactor.
- screen: simplifications of win_do_lines
|
| | |
|
| | |
|
| |
|
|
|
|
| |
Also mention how to donate to Nvim.
closes #8603
|
| |
|
|
| |
- update standard-plugin-list. closes #8388
|
| |
|
|
|
|
|
|
| |
Problem: Cannot see what digraph is used to insert a character.
Solution: Show the digraph with the "ga" command. (Christian Brabandt)
https://github.com/vim/vim/commit/5f73ef8d20070cd45c9aea4dc33c2e0657f5515c
close #8190
|
| |
|
|
|
| |
Update runtime files
https://github.com/vim/vim/commit/2c64ca1802b2c99b16d2fdf581b68b5baffb082a
|
| |
|
|
|
| |
Update runtime files.
https://github.com/vim/vim/commit/95bafa296ae97bf420d5c74dd6db517b404c5df7
|
| |
|
|
|
| |
Update runtime files.
https://github.com/vim/vim/commit/93a1df2c205c8399d96c172d9483e0793d32892a
|
| |
|
|
|
| |
Update runtime files.
https://github.com/vim/vim/commit/20aac6c1126988339611576d425965a25a777658
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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)
|
| |
|
|
|
| |
Update runtime files.
https://github.com/vim/vim/commit/d473c8c101262702ea9eeb14907ee20a786942b2
|
| |
|
|
|
| |
Update runtime files.
https://github.com/vim/vim/commit/91f84f6e11cd879d43d651c0903d85bff95f0716
|
| |
|
|
|
| |
Update runtime files.
https://github.com/vim/vim/commit/a9604e61451707b38fdcb088fbfaeea2b922fef6
|
| |
|
|
|
| |
Update runtime files.
https://github.com/vim/vim/commit/b477af2260d9bc7ae7f743f0a14265d7ee12ee09
|
| |
|
|
|
| |
Update runtime files, add Danish translations.
https://github.com/vim/vim/commit/fd35811ca528de7612f9571bce20ef4c392fe5f7
|
| |
|
|
|
| |
Updated runtime and language files.
https://github.com/vim/vim/commit/6dc819b1299e1d9f99303568772ade544d5c1322
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Update runtime files.
https://github.com/vim/vim/commit/675e8d6adb88d5b38087870dfda51c0205070741
---
NA:
vim-patch:ffd112edc6a8
Fix missing patch number.
https://github.com/vim/vim/commit/ffd112edc6a8f72b66c06207bff4431f6aec7b6f
|
| |
|
|
|
| |
Update runtime files.
https://github.com/vim/vim/commit/d2f3a8b8787333abf2300d38836b196955f10c00
|
| |
|
|
|
| |
Update runtime files.
https://github.com/vim/vim/commit/0b0f0992d46ef02fdfc1240744bef91d4299c1df
|
| |
|
|
|
| |
Updated runtime files
https://github.com/vim/vim/commit/eb3dc87f01391bb075d97aef3d00f91b4e08a25c
|