| Commit message (Collapse) | Author | Age |
| |
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update a flawed match pattern for the vimCommand syntax group. To see
the effect of this fix, open a vimscript buffer,
nvim -u NONE foo.vim
configure a couple highlight groups,
:hi! vimIsCommand ctermfg=Green
:hi! vimCommand ctermfg=Red
:syntax enable
and add the following lines to the buffer:
let foo=xFoo
let bar=zBar
You'll notice the "z" in zBar is Red, while xFoo and the rest of Bar are green. This will
be the case as long as the word following `=` starts with the letter "z". This has already
been fixed upstream by adding a "\>" word boundary to the match pattern:
https://github.com/vim/vim/issues/124
https://github.com/vim/vim/commit/e2719096250a19ecdd9a35d13702879f163d2a50#diff-86da060e2153c8ce5dc317a7b4b5a29dR27
This particular match pattern was also mentioned in issue #5491, but in reference to a bug
that was related to the generated part of syntax/vim.vim, whereas this bug lives in the
non-generated part of the file.
|
|\
| |
| |
| |
| |
| |
| | |
Removed these commits (test-suite changes):
e2fba01910e0
7c809c4bc708
18e7cd9e9727
|
| |
| |
| |
| | |
Use a table and adjust cursor-shape a bit.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is a new convention pioneered by tmux. It does not do much for
nvim; since nvim always looks to see whether it should be making up
"setrgbf" and "setrgbb" capabilities. But it is a way for terminfo to
force this, irrespective of the hardwired list in the code, for more
terminal types. On the gripping hand, updating terminfo descriptions to
actually have "setrgbf" and "setrgbb" capabilities so that nvim never
has to try to invent them in the first place, is as good if not better
an approach for overriding what is baked into the code.
|
| | |
|
| |
| |
| |
| |
| |
| | |
The example used &term which is no longer meaningful.
Fortunately, we can change this into a useful example using $TERM that also
shows how to address a common need with termguicolors at the same time.
|
| |
| |
| |
| |
| | |
:help TERM previously pointed to a section that no longer even discussed the
variable.
|
| |
| |
| |
| |
| | |
Also explain more clearly the difference between Vim and Nvim
when it comes to built-in terminfo entries.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The details are in the on-line help under :help true-color .
The brief precis is that nvim is (I hope.) converging with tmux and libvte.
It is taking the same approach with setrgbf and setrgbb terminfo capabilities
that it does with the Ss and Se terminfo capabilities.
|
| | |
|
| |
| |
| |
| | |
Also document better what to do on slow terminals.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The details are in the on-line help under :help cursor-shape .
The brief precis is that nvim is following the lead of tmux, and going
beyond what tmux does to make cursor shape changes work on a broad range of
terminals. This includes on tmux itself, which is no longer bypassed.
|
| |
| |
| |
| |
| |
| |
| |
| | |
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.
|
| | |
|
| |
| |
| |
| |
| | |
This gives libtermkey 50msec to reassemble split multibyte sequences
like DCSes.
|
| | |
|
| |
| |
| |
| | |
Closes #6029
|
|\ \
| | |
| | | |
vim-patch:7.4.2259,7.4.2268,7.4.2318,7.4.2320
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Using CTRL-N and CTRL-P for incsearch shadows completion keys.
Solution: Use CTRL-T and CTRL-G instead.
https://github.com/vim/vim/commit/1195669f9e434fa9ab8b57ee9470bf951e4990b8
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: With 'incsearch' can only see the next match.
Solution: Make CTRL-N/CTRL-P move to the previous/next match. (Christian
Brabandt)
https://github.com/vim/vim/commit/4d6f32cbfbaf324ac4a25c0206a5db0e9f7a48f7
|
|\ \ \
| |/ /
|/| | |
lua: Add paths from &runtimepath to package.path and package.cpath
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This allows users who have per-project Ruby versions (e.g. with `rvm`)
to pin to a particular gem installation.
For example: `let g:ruby_host_prog = 'rvm system do neovim-ruby-host'`
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Sometimes the `gem list` command used for finding the latest version of
the `neovim` gem prints an error, which can throw off the `split()` call
due to extra parenthesis. This locks down the split pattern to make
conflicts less likely.
|
| | | |
|
| | | |
|
|\ \ \ |
|
| | | | |
|
|\| | | |
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Problem: The client-server test may hang when failing.
Solution: Set a timer. Add assert_report()
https://github.com/vim/vim/commit/42205551b140bee8b419b24abe210f56bb80b35e
|
| | |/
| |/|
| | |
| | |
| | |
| | |
| | | |
Problem: Sometimes VimL is used, which is confusing.
Solution: Consistently use "Vim script". (Hirohito Higashi)
https://github.com/vim/vim/commit/b544f3c81f1e6a50322855681ac266ffaa8e313c
|
|/ /
| |
| |
| |
| |
| |
| | |
Problem: Number variables are not 64 bits while they could be.
Solution: Add the num64 feature. (Ken Takata)
https://github.com/vim/vim/commit/22fcfad29276bd5f317faf516637dcd491b96a12
|
|\ \ |
|
| | | |
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Reverts commit 337b6179df852350b52409fd3806e4b47ab2875b
Closes #6716 at the expense of not being able to use a
multi-key 'pastetoggle' manually.
Multi-key 'pastetoggle' can still be used when inserting the entire
option into the typebuffer at once (though the use here is
questionable).
Also remove those tests to do with waiting for the completion of
'pastetoggle' and mention in the documentation that 'pastetoggle'
doesn't wait for timeout.
|
| | |
| | |
| | |
| | | |
Helped-By: oni-link <knil.ino@gmail.com>
|
|\ \ \
| | | |
| | | | |
Use uv_getaddrinfo() for servers
|
| | |/
| |/| |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Showing the 'number' column in terminal buffers is a bit silly because
of 'scrollback'. But it's mostly harmless and technically works as
expected.
The least surprising thing is to leave the user's settings alone. Since
there are tradeoffs in both cases, we choose inertia.
We still disable 'relativenumber' in *terminal-mode* (as opposed to
normal-mode) because it is totally broken: the Nvim cursor (not terminal
cursor) is always on the last line.
|
| |/
|/|
| |
| |
| | |
Different implementations of `man` might be using different
flags for sections.
|
| |
| |
| |
| | |
Closes #6788
|