| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
Creating a scratch buffer is a chore/ritual, and would be more
useful/common if formally exposed.
|
|
|
|
|
|
|
|
|
| |
Problem: Session file has problem with single quote in file name. (Jon
Crowe)
Solution: Use a double quoted string. Add a test.
https://github.com/vim/vim/commit/ad36a3588d32985ee27bd11aa97e5195ef623158
Fixes https://github.com/neovim/neovim/issues/9618
|
|\ |
|
| |
| |
| |
| | |
closes #9615
|
|/
|
|
|
|
| |
- Group CMAKE_BUILD_TYPE-related logic together.
- Print the MIN_LOG_LEVEL message (in the build-log) next to the
CMAKE_BUILD_TYPE message.
|
|\ |
|
| | |
|
|/ |
|
|
|
|
|
| |
Problem: findfile() and finddir() are not properly tested.
Solution: Extend the test and add more. (Dominique Pelle, closes vim/vim#3880)
https://github.com/vim/vim/commit/ed71ed37bcd44bcbfcf59beee1248799de3315ec
|
|\
| |
| | |
UI: 'pumblend' for cterm (256-color TUI)
|
| |
| |
| |
| |
| | |
Replace the implementation cargo-culted from Vim's source with something
simpler which "seems to look better" with 'pumblend'.
|
|/
|
|
|
|
| |
hl_rgb2cterm_color, hl_cterm2rgb_color were adapted from Vim 8.1
(color2index, cterm_color2rgb).
ref: https://github.com/vim/vim/commit/c5cd88554f1e0b2e9ff08d9a0748238dd8340ce1
|
|\ |
|
| |
| |
| |
| |
| |
| | |
https://github.com/neovim/neovim/issues/9598#issuecomment-462421302
> On systems other than macOS, terminfo always has them set. It's part
> of the ANSI standard SGR codes
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
tmux users are encouraged to use "tmux-256color" instead of the old
"screen-256color". Put this in your .tmux.conf :
if-shell 'infocmp tmux-256color' 'set -g default-terminal "tmux-256color"' 'set -g default-terminal "screen-256color"'
If default-terminal is "tmux-256color" AND tmux finds its terminfo, THEN
it will enable italics (regardless of whether the terminfo contains
sitm/ritm).
OTHERWISE tmux "emulates screen", which means it emits italics as
"reverse". That's unfortunate, but it's an acceptable compromise that
allows Nvim to support italics in tmux by default in compatible (and
increasingly-common) configurations.
Test case:
tmux
nvim -u NORC +'hi Comment cterm=italic' CMakeLists.txt
ref #9598
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
This is the conservative approach, requiring TERM=nsterm as recommended
at `:help $TERM`. It won't work with Terminal.app's default of
TERM=xterm-256color, nor in tmux.
Test case:
TERM=nsterm nvim -u NORC +'hi Comment cterm=italic' CMakeLists.txt
closes #9598
|
|\ \
| |/
|/| |
highlight: handle blending with gui=reverse and guisp attribute
|
|/ |
|
|\
| |
| | |
ui: implement ext_messages to externalize all messages in msg area
|
|/
|
|
| |
Co-Author: Dongdong Zhou <dzhou121@gmail.com>
|
|\
| |
| | |
api: add nvim_create_buf to create a new empty buffer.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Loading existing files into a buffer is non-trivial and requires a window.
Creating an unnamed emtpy buffer is trivial and safe though, thus worth a
special case.
Change nvim_buf_set_option to use aucmd_prepbuf. This is necessary
to allow some options to be set on a not yet displayed buffer, such
as 'buftype' option.
vim-patch:7.4.1858: Add BLN_NEW to enforce buflist_new creating new buffer
|
|/
|
|
|
| |
This was forgotten in 352811fe5 since the commit was originally meant to only
change 'listchars'.
|
|\
| |
| | |
screen: cleanup allocation and scrolling
|
| |
| |
| |
| |
| |
| | |
grid_xx functions shouldn't randomly be called when the screen is not valid.
Nvim deterministically initializes a default screen early in main(), so the
default grid can be assumed to be allocated.
|
|/
|
|
|
| |
Since the separation between internal screen and TUI, internal scroll
cannot FAIL. Delete the conditions for this.
|
|\
| |
| | |
UI: implement 'pumblend' option for semi-transparent popupmenu
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
Why?
- Because we can.
- Because the TUI is just another GUI™
- Because it looks kinda nice, and provides useful context like 1 out of 100
times
Complies with "don't pay for what you don't use".
Some crashes for resizing were unfolded, add tests for those.
|
|
|
|
| |
closes #9583
|
|\
| |
| | |
UI: always use contrete colors for default_colors_set
|
|/
|
|
|
| |
But add an escape hatch needed for external TUI, so it still can use
terminal emulator defaults.
|
|\ |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On Travis CI, -Wmissing-prototypes gives strange error:
In file included from ../src/nvim/eval.c:5965:
/home/travis/build/neovim/neovim/build/src/nvim/auto/funcs.generated.h.gperf:215:1: error: conflicting types for 'find_internal_func_gperf'
find_internal_func_gperf (register const char *str, register unsigned int len)
^
../src/nvim/eval.c:5962:20: note: previous declaration is here
const VimLFuncDef *find_internal_func_gperf(register const char *str,
^
|
| |
| |
| |
| |
| |
| |
| | |
ref #343
Though I don't see a strong benefit, it isn't too much of a burden, and
maybe avoids confusion in some cases.
|
| |
| |
| |
| | |
- add_definitions() is preferred to CMAKE_C_FLAGS.
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Makes the 'scrollback' option more consistent (same default for all buffers) and future-proof.
- Default to -1 for all buffers, but treat it as an implementation detail.
- Document range of 1 - 100_000.
- New terminal buffer by default sets scrollback=10_000 if the global default is -1.
- Existing terminal buffer: On entering terminal-mode or on refresh, if the user explicitly did `:set[local] scbk=-1`, the local value goes to 100_000 (max). (This is undocumented on purpose. Users should work with explicit values in the range of 1-100_000.)
|
|/
|
|
|
| |
..which gets triggered when SIGUSR1 is sent to the nvim process.
Closes #9562
|
|\
| |
| | |
popupmenu: fix alignment of kind and extra after #9530
|
| | |
|
|\ \ |
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Default for 'iminsert' is annoying.
Solution: Make the default always zero. (Yasuhiro Matsumoto, closes vim/vim#2071)
https://github.com/vim/vim/commit/4cf56bbc85f77846aeb378cfb071677336dfad6d
|
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: No debugger making use of the terminal window.
Solution: Add the term debugger plugin. So far only displays the current
line when stopped.
https://github.com/vim/vim/commit/fe386641b0c56c5de2bca8e1f4cd5e2a1f1aea7e
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: May get an endless loop if 'statusline' changes a highlight.
Solution: Do not let evaluating 'statusline' trigger a redraw.
https://github.com/vim/vim/commit/ba2929b6afd2fc20479912a8dec789be26a38244
|
| | |
| | |
| | |
| | |
| | |
| | | |
Problem: Running tests may pollute shell history. (Manuel Ortega)
Solution: Make $HISTFILE empty.
https://github.com/vim/vim/commit/6a8691d483914606213a24356a9124fa41c93b69
|
| |/
|/| |
|
|\ \
| |/
|/| |
Implement popupmenu as a floating grid internally to reduce flicker
|
| | |
|
| |
| |
| |
| |
| | |
Many of these are handled by the compositor. Check that it causes
no glitches.
|
| | |
|