| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
ref #7383
reverts d1874ab2821d076397290cc154d87ec2dc352c79
ref #6380
|
| |
|
| |
|
| |
|
|\ |
|
| |\
| |/
|/| |
|
| |\ |
|
| |\ \ |
|
| | | | |
|
| |_|/
|/| |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
- Prefer "TUI" where possible to refer to the host terminal.
- Remove obsolete tags and ancient TTY exposition.
- Establish "terminal" to consistently mean "terminal emulator" in all
Nvim documentation. This removes the need for verbose qualifiers in
tags and prose.
References #6280
References #6803
|
| |/
|/|
| | |
Closes #6763
|
| | |
|
|/ |
|
|
|
|
| |
Also expand the example in term-dependent-settings.
|
|
|
|
| |
Closes #6937 "nvim_get_keymap output is unreliable"
|
|
|
|
|
| |
This was already removed in 3baba1e7bc66, except the documentation and
CPO_VI entry. find_term_bykeys() is irrelevant to Nvim.
|
|\
| |
| |
| |
| |
| |
| | |
Removed these commits (test-suite changes):
e2fba01910e0
7c809c4bc708
18e7cd9e9727
|
| |
| |
| |
| |
| | |
Also explain more clearly the difference between Vim and Nvim
when it comes to built-in terminfo entries.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This documents 256-colour and true colour handling, cursor shapes,
and scrolling regions.
Almost all of these headings are taken from the Vim doco, so that
the :help commands that people learn are a transferable skill.
|
| | |
|
|/ |
|
| |
|
|\ |
|
| | |
|
|\ \
| |/
|/| |
|
| | |
|
|/
|
| |
Closes #6705
|
|\ |
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Closes #4482
TODO: revisit find_key_option_len()
|
|\| |
|
| | |
|
| |
| |
| |
| | |
Also: update default 'guicursor' to match the documentation.
|
| | |
|
| | |
|
|/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
- Vim "unix default" of 'noshowcmd' is serving few users. And it's
inconsistent.
- 'ruler' and 'belloff=all' improve the out-of-the-box experience.
- Continue to use 'noshowcmd' and 'noruler' by default in the functional
tests to keep them fast.
TODO: Add a "disable slow stuff" command or mapping to address the
use-case of a very slow terminal connection.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
`cw` and `cW` behave like `ce` and `cE` respectively. This is
inconsistent compared to `dw` and `dW`.
Introduce a new cpoptions flag "_" to toggle the Vi behavior.
Closes #6234
Patch-by: Christian Brabandt <cblists@256bit.org>
References:
https://github.com/chrisbra/vim-mq-patches/blob/master/cpo_changeword
https://groups.google.com/d/msg/vim_use/aaBqT6ECkA4/ALf4odKzEDgJ
https://groups.google.com/d/msg/vim_dev/Dpn3xtUF16I/T6JcOPKN6usJ
http://www.reddit.com/r/vim/comments/26nut8/why_does_cw_work_like_ce/
|
|\
| |
| | |
cmdline: CTRL-R: Omit trailing ^M character
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The "technically correct" interpretation is to execute the first line
that is seen (and this is what happens on middle-click paste in Vim).
^M is only intended to "defuse" the newline, so the user can review it.
The parent commit changed the behavior to insert <Space> between lines,
but that's a higher-risk change: it is arguably possible that some user
*wants* the literal ^M chars when e.g. assigning to a register:
:let @a='<C-R>b'
To avoid that risk, keep the old behavior and only omit the last ^M.
This makes `yy:<C-R>0` nicer at no cost.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
^M isn't any more "correct" than space: the "technically correct"
interpretation is to execute the first line that is seen (and this is
what happens on middle-click paste in Vim). ^M is only intended to
defuse the newline, so that the user can review the command. We can do
that with a space instead, and then the command can be executed without
having to fix it up first.
|
|/
|
| |
This was never supported and it does not make sense for Nvim.
|
| |
|