| Commit message (Collapse) | Author | Age |
|
|
|
| |
Closes #7039
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: Cannot get the number of the current quickfix or location list.
Solution: Use the current list if "nr" in "what" is zero. (Yegappan
Lakshmanan) Remove debug command from test.
https://github.com/vim/vim/commit/890680ca6364386fabb271c85e0755bcaa6a33c1
|
|\ \
| |/
|/|
| |
| |
| | |
Closes #4533
Closes #6389
Closes #4913
Closes #7005
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| | |
sampletext regions no longer supported
make sure tutorExpect is available
don't conceal code region delimiters
|
| |
| |
| |
| | |
tutor: remove movement mappings
|
| | |
|
| | |
|
| |
| |
| |
| | |
this makes 'expect' regions simpler to handle.
|
| | |
|
| |
| |
| |
| |
| |
| | |
TODO: handle errors in the `get`. systemlist() should take an
options dictionary like jobstart(), which may specify a stderr handler.
References #6565
|
| |
| |
| |
| |
| |
| |
| |
| | |
Several people have suggested that the "by Bram" byline is misleading,
it implies that Bram is actively involved with the project. Up to now we
left it as an homage.
Bram agreed that it is misleading, and suggested a mention somewhere
other than the intro.
|
| |
| |
| |
| |
| |
| |
| | |
Closes #7020
Also fix 'iskeyword' setting, which I fumbled in
440133e0d5d576e46bd5ffa555f6a9c534789b48
|
|/
|
|
| |
Fixes https://github.com/neovim/neovim/issues/7009
|
|
|
|
|
|
|
| |
The libvte test was too agressive, and is reduced to only triggering
when it is libvte 0.36 AND a gnome or xterm terminal type is used.
Contrastingly, tmux was not on the list at all and now is.
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| | | |
|