| Commit message (Collapse) | Author | Age |
| ... | |
| |
|
|
|
| |
Closes #4663
References #3310
|
| |\
| |
| | |
Enable functional tests in Appveyor
|
| | | |
|
| |/
|
|
| |
update screen.lua to use new style nvim_ui_attach
|
| |
|
|
|
|
|
|
|
|
|
|
| |
- Links to Search by default
screen.c: Combine CursorLine with QuickFixLine
- HLF_QFL takes priority over HLF_CUL
docs: Updated to mention QuickFixLine
runtime: Added QuickFixLine to nvimHLGroup
tests: QuickFixLine highlight
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
- Use the default buffer text provided by before_each (avoids extra steps and
makes the tests more consistent with each other)
- Indent
- Adjust help doc
|
| | |
|
| |
|
|
|
| |
syntax.c: Added syn_get_concealed_id()
tests: Added tests for mouse clicks on concealed text.
|
| |
|
|
| |
Reference: https://github.com/neovim/neovim/issues/3772#issuecomment-162334005
|
| |
|
|
| |
Also use less "regular" values for cterm colors.
|
| |
|
|
|
|
| |
It is otherwise impossible to determine which test failed sanitizer/valgrind
check. test/functional/helpers.lua module return was changed so that tests which
do not provide after_each function to get new check will automatically fail.
|
| |
|
|
|
|
|
| |
vim-patch:7.4.1603
TODO(bfredl): if we allow events in HITRETURN and ASKMORE states,
we need to add the necessary redraws as well.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |\
| |
| |
| |
| | |
Closes #2040
Closes #3370
|
| | | |
|
| | | |
|
| | |
| |
| |
| | |
Screen.lua needed a little cosmetical adjustment to print out the color nicely.
|
| |/ |
|
| | |
|
| |\
| |
| | |
vim-patch: 7.4.1236
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Problem: When "syntax manual" was used switching between buffers removes
the highlighting.
Solution: Set the syntax option without changing the value. (Anton
Lindqvist)
https://github.com/vim/vim/commit/885f24fbcae2a39ae496ffb3a1e139379be8fae1
Patch applied cleanly to the nvim sources except for version.c.
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
| |
- Code from Vim source.
- Removed the check for 'guioptions'
- mouse_spec.lua: test <ScrollWheelLeft> and <ScrollWheelRight>
- Move horizontal scroll logic to mouse.c
- Remove 'gui_' from the function names
- Renamed variables to be more specific (as opposed to generic p, w).
- Marked some functions as `static`
|
| |
|
|
|
| |
The new version of the lua client uses libmpack as a backend, and some test
scripts had to be updated to reflect that.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds support for:
- api:vim_input("<D-a>")
- ":nnoremap <C-D-S-...>" and permutations thereof
UIs must capture the modifier and send it as "<D-...>" to vim_input().
Note: Before this commit, any arbitrary ":nnoremap <{foo}-{bar}>"
mapping could already be invoked with feedkeys("\<{foo}-{bar}>"). This
commit supports "D-" as a modifier that can be combined with "C-", "A-",
"S-" in any order.
For non-GUI (terminal) support, user must:
:set <D-a>={CSI sequence}
then send the {CSI sequence} from their terminal. But this does not work
yet (regression #2204).
Closes #2190
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Plugins (YCM, dispatch.vim) use gui_running to decide behavior; so do
some colorschemes. Up to now, nvim lied about gui_running for the
benefit of colorschemes and the detriment of all _other_ plugins that
check this condition. That's counterproductive: a user employs at most
_one_ colorscheme but may use many other plugins which expect the Vim
legacy semantics of gui_running.
Moreover, colorschemes usually don't _need_ to check gui_running: they
can instead set cterm{fg,bg} and gui{fg,bg} in the same :highlight call.
It is reasonable for users who want "true color" to modify their
colorscheme once (or request upstream to do so) in order to avoid
running into quirks in any other plugins.
Closes #2782
|
| | |
|
| | |
|
| |
|
|
|
|
| |
This is consistent with VIM behavior. When showing a visual selection,
VIM only extends it past the last character if eol is in listchars (even
if nolist is set).
|
| |
|
|
|
|
|
|
| |
Travis defines[1] $CI for its builds, whereas $CI_TARGET is
a Neovim-specific env var from 6483a198e4bee1e80683ba12e061616c3e6c4090
that lost prominence in d2eb4a934683b5da63000d8b79a0d4c9a314d1c0.
[1] https://docs.travis-ci.com/user/environment-variables/
|
| | |
|
| | |
|