| Commit message (Collapse) | Author | Age |
|\
| |
| | |
Vim 7.4.2250
|
| | |
|
|/
|
|
|
|
|
| |
Problem: Some error message cannot be translated.
Solution: Enclose them in _() and N_(). (Dominique Pelle)
https://github.com/vim/vim/commit/5b30291785e6b9be1a607504c14bd03c601b59a6
|
|\
| |
| | |
doc: rewrite job-control example
|
|/
|
|
| |
Fixes https://github.com/neovim/neovim/issues/7009
|
|\
| |
| |
| | |
vim-patch:7.4.2354
|
|/
|
|
|
|
|
|
| |
Problem: The example that explains nested backreferences does not work
properly with the new regexp engine. (Harm te Hennepe)
Solution: Also save the end position when adding a state. (closes vim/vim#990)
https://github.com/vim/vim/commit/d563883a1fb5ec6cf4a2758c5e36ac1ff4e9bb3d
|
|\
| |
| | |
third-party: Bump libtermkey to 0.20
|
| | |
|
|\ \
| | |
| | | |
Fix #6982
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
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.
|
| |
| |
| |
| |
| |
| |
| |
| | |
This is a refactoring typo from #6947.
Fixes #6985
Combined with #6947 where typo was made it also fixes vim/vim#1827 which was
present in Neovim.
|
| |
| |
| |
| |
| |
| |
| |
| | |
During a preview, we can stop looking for matches after we got enough
lines for the preview buffer.
Because of this perf improvement, the 'redrawtime' test needs to be
slowed down in a different way: _long_ lines instead of just many lines.
|
|\ \
| |/
|/| |
|
| | |
|
| | |
|
| |
| |
| |
| | |
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.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The gchar_cursor() == NUL check is already done in ins_ctrl_o.
ins_esc changes gchar_cursor() so this if block is probably never
entered.
Issue:
Pressing CTRL-O in insert mode at the end of the line and typing
:startinsert moves the cursor 1 column back, when I expect the cursor
to remain at the end of the line
This is a regression from Vim behavior. Since at least Vim version 7.0,
Vim returns you to insert mode at the end of the line.
091e7d033cbf0f4da068292ce4ac934f1c3dd91e is the first bad neovim commit
Steps to reproduce using `nvim -u NORC`:
`aaaa<C-o>:startinsert<CR>`
Fixes #6962
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|\
| |
| | |
Prefer the static jemalloc library by default on OSX
|
|/
|
|
|
| |
When neovim is dynamically linked against jemalloc on OSX, users are
hitting the deadlock described in jemalloc/jemalloc#895.
|
|\
| |
| | |
fix SIGTERM/SIGHUP for jobs
|
| |
| |
| |
| |
| | |
This reverts the revert of #6644 (7c1a5d1d4), and handles it properly
now (with tests).
|
|/ |
|
|\
| |
| |
| |
| |
| |
| | |
Removed these commits (test-suite changes):
e2fba01910e0
7c809c4bc708
18e7cd9e9727
|
| | |
|
| |
| |
| |
| | |
Per warnings about house style from automated tools.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The terminfo doco explicitly states that it covers the case where the
terminal is in application cursor/keypad (i.e. "keypad transmit") mode,
and not where it is in normal cursor/keypad (i.e. "keypad local") mode.
Full screen applications like nvim must switch to and from keypad
transmit mode when expecting the control sequences given by terminfo.
|
| |
| |
| |
| | |
Per warnings about house style from automated tools.
|
| |
| |
| |
| |
| |
| | |
This fixes a test failure caused by dfaecb25f6a9a94f29a38d9f2d24a579b3dff5f
not tracking what the current visibility is and whether it matches the
current business state.
|
| |
| |
| |
| |
| |
| | |
When higher layers flush the TUI layer output buffer, but there is
nothing in the buffer to flush, no longer does the TUI layer write out
unnecessary cnorm/civis sequences surrounding that nothing.
|
| |
| |
| |
| |
| | |
For the linux terminal type apply the same fixup to the terminfo civis
string that is applied to the cnorm string.
|
| |
| |
| |
| | |
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.
|
| |
| |
| |
| |
| | |
Use the terminfo set_attribute capability to set multiple attributes in one
control sequence, if it is available.
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
From observation, there are several different possible behaviours:
1. Deferred wrap like a real DEC VT. The cursor stays visible in the last
column, and CUB is calculated relative to that column.
Examples: xterm, Unicode rxvt, PuTTY, nosh console-terminal-emulator,
FreeBSD kernel's built-in emulator, Linux's built-in emulator
2. Deferred wrap like a real DEC VT. CUB is calculated relative to the last
column. But the cursor is invisible.
Examples: emulators using newer libvte
3. Non-deferred wrap. The cursor has already wrapped to the next line and CUB
does not wrap back.
Examples: cygwin, Interix
4. Non-deferred wrap that acts like deferred wrap. The cursor has already
visibly wrapped to the next line, but CUB can wrap back around the left
margin.
Examples: Konsole
5. Deferred wrap with visibly out of bounds cursor. The cursor visibly moves
outwith the screen boundaries. CUB is calculated relative to a cursor
column that has overflowed the end of the screen grid array.
Examples: iTerm2
6. Deferred wrap with invisibly out of bounds cursor. CUB is calculated
relative to a cursor column that has overflowed the end of the screen grid
array. And the cursor is invisible.
Examples: emulators using older libvte
In many cases, nvim does not have enough information to know which behaviour
the terminal will exhibit, and thus the correct amount of CUB to issue.
|
| |
| |
| |
| | |
Alongside interix.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
Also enable italics on Konsole when it is falsely claiming to be xterm.
Also note the reasons for some of the patcher terminfo patches.
|
| | |
|
| |
| |
| |
| |
| |
| | |
Partly undo 8ab08a65ba3bc9a44741a2ec9aa81fbcc77467fb. Further testing
by Enrico Ghirardi suggests limiting the non-deferred automatic wrap to
only the bottom line, whose rightmost column is not printed for iTerm.
|
| |
| |
| |
| | |
This "trick" is not conditional upon the type of UI.
|
| |
| |
| |
| |
| | |
* Don't use &data->grid when we already have grid .
* Consolidate into a single assignment to the default_attr flag.
|