| Commit message (Collapse) | Author | Age |
... | |
| |
|
|
|
|
|
|
|
|
|
| |
Problem: In Insert mode, after inserting a newline that inserts a comment
leader, CTRL-O moves to the right. (ZyX) Issue 57.
Solution: Correct the condition for moving the cursor back to the NUL.
(Christian Brabandt)
https://code.google.com/p/vim/source/detail?r=v7-4-492
|
|\
| |
| | |
job.c: Prevent early return from job_wait().
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The primitive C canonicalizer we use to strip out duplicate header
declarations and keep luajit's ffi happy, didn't work properly in this case.
What happened is this (in /usr/include/ctype.h):
__DARWIN_CTYPE_TOP_inline int
isspecial(int _c)
{
return (__istype(_c, _CTYPE_T));
}
Gets preprocessed to something like:
__inline int
isspecial(int _c)
{
return (__istype(_c, _CTYPE_T));
}
On OSX/gcc. The formatter wasn't recognizing this entire function as
something to put on a single line because it naively just checks for
"static" or "inline" for that, but not "__inline".
This error doesn't occur on OSX/clang. Without looking further into it, I
guess that __DARWIN_CTYPE_TOP_inline gets defined to inline on clang, but
__inline on gcc, for some reason.
This helps issue #1572 along.
|
| |
| |
| |
| |
| |
| |
| |
| | |
The second argument to lfs.attributes() serves only to select a specific
part of the normally returned table. It's not a file open flag (e.g.: as for
fopen() in C). Also made the (n)eq checks a bit more idiomatic.
Fixes #1831
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
- emulate gui_running and terminal colors
- scrolling/clearing regions
- mouse wheel scrolling
- setting icon/title
- :stop/:suspend
- screen resize
|
| | |
|
| | |
|
| |
| |
| |
| | |
When set to false, nvim will send cterm color numbers with `highlight_set`.
|
| |
| |
| |
| |
| | |
Ignoring invalid key sequences simplifies input handling in UIs. The only
downside is having to use "<lt>" everytime a "<" is needed on functional tests.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
It is necessary to notify the UI when the default background/foreground colors
change in order to render correctly.
|
| |
| |
| |
| | |
These functions need to operate on the current the scroll region.
|
| | |
|
| |
| |
| |
| |
| |
| | |
- Remove suspend method from the UI protocol
- Handle `:suspend` by disconnecting the last channel that sent a request to
nvim.
|
| |
| |
| |
| | |
When set to false, nvim will send cterm color numbers with `highlight_set`.
|
| |
| |
| |
| |
| | |
Ignoring invalid key sequences simplifies input handling in UIs. The only
downside is having to use "<lt>" everytime a "<" is needed on functional tests.
|
| | |
|
| | |
|
| |
| |
| |
| |
| | |
It is necessary to notify the UI when the default background/foreground colors
change in order to render correctly.
|
|/
|
|
|
| |
It should only clear to the end of the current scroll region(this is the
behavior expected by nvim)
|
|\
| |
| | |
vim-patch:7.4.552
|
| |
| |
| |
| |
| |
| |
| | |
Problem: Langmap applies to Insert mode expression mappings.
Solution: Check for Insert mode. (Daniel Hahler)
https://code.google.com/p/vim/source/detail?r=v7-4-552
|
|\ \
| | |
| | | |
vim-patch:7.4.549
|
| |/
| |
| |
| |
| |
| | |
Add new files for 7.4.549.
https://code.google.com/p/vim/source/detail?r=750a6986aa86a2bb3346631a353913b899d86748
|
|/
|
|
| |
https://code.google.com/p/vim/source/detail?r=6a598be6d4e8
|
|
|
|
|
|
|
| |
Problem: test_mapping fails for some people.
Solution: Set the 'encoding' option. (Ken Takata)
https://code.google.com/p/vim/source/detail?r=v7-4-488
|
|
|
|
|
|
|
| |
Problem: A 0x80 byte is not handled correctly in abbreviations.
Solution: Unescape special characters. Add a test. (Christian Brabandt)
https://code.google.com/p/vim/source/detail?r=v7-4-483
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
- Add screen.lua which implements a remote screen to verify screen state by
tests under functional/ui
- Add some basic screen/highlight tests
|
| |
|
| |
|
|\
| |
| | |
Api: Improve Nul handling
|
| | |
|
| | |
|
| |
| |
| |
| | |
Remove `expandtab` and add a missing trailing space from the legacy test.
|
|/ |
|
| |
|
| |
|
|
|
|
|
| |
Move general initialization functions to early_init, which simplifies
test/unit/helpers.lua, which requires all these functions.
|
|
|
|
| |
- tests for vim_feedkeys and replace_termcodes
|
|
|
|
|
|
|
| |
While we're at, using the slightly more portable `command -v` technique
to detect the executable. Also, there's no need to use `io.popen()` if
we aren't going to record the path. Instead, let's use the simpler
`os.execute()` to detect the presence of xclip.
|
|\
| |
| | |
Fix broken functional test.
|
| |
| |
| |
| |
| |
| | |
In Lua, all math is floating point. We need to coerce the result of a
division into a integer with the `{get,set}_height` and
`{get,set}_width` window_spec functional tests.
|
|/
|
|
|
| |
The new version fixes defunct processes which causes random test failures on
some systems(#1519)
|
|
|
|
|
|
| |
The $GDB env var can be set to run tests under gdbserver. If $VALGRIND is also
set, it will add the --vgdb=yes command-line option to valgrind instead of
starting gdbserver.
|