| Commit message (Collapse) | Author | Age |
|\
| |
| |
| |
| | |
jszakmeister/fix-unittest-header-parsing-on-freebsd
unittests: define _Thread_local to be nothing
|
| |
| |
| |
| |
| | |
This helps the LuaJIT ffi module to parse the header correctly.
Otherwise, the whole suite of tests fail.
|
| | |
|
|/
|
|
|
| |
FreeBSD doesn't use bash by default, causing the group id to be print
out in the middle of the test.
|
|
|
|
|
|
|
|
|
|
| |
The systemlist test currently calls the `echo` command which can potentially
complete before being interrupted, causing random test failures.
Use `yes | xargs` instead. A `yes` invocation that is not piped through `xargs`
can produce a huge amount of lines in a very short time, leading memory
starvation when the result is being converted into a list. `xargs` ensures only
one line of output will be produced while allowing interrupt to be tested.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Disable JIT to find cause for random `PANIC: unprotected error in call to Lua API` on Travis (OS X).
|
|
|
|
|
|
|
| |
`job_send` is non-blocking and can potentially fail due to the following
`job_stop` call. Since we can't reliably verify that the "exit" event is only
sent after the "stdout" event, mark the test as pending and fix after we can
get a notification about `job_send` status.
|
|
|
|
|
|
|
| |
The test was hoping to not find a tags file, but didn't actively guard
against it. In my case, I had a tags file present which was causing
different output to be generated. To fix this, let's set the tags
option to look for an unlikely filename.
|
| |
|
|
|
|
|
| |
This test depends on terminal size to work correctly. After migration this
requirement is removed.
|
|
|
|
|
|
| |
While running under valgrind, the screen can take significantly longer to
update(especially on travis) so a higher timeout can be required. Also reduce
the timeout when not running on valgrind.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When a test that fails leaves nvim in a 'Press Enter...' state, the whole suite
will hang because the `qa!` command executed before the next test won't be
processed until '<enter>' is sent.
Now the lua client can send a signal with when `Session:exit()` is called, so
the `qa!` request is no longer necessary.
Also:
- Set noswapfile at startup to prevent tests from leaving .s* swap files(should
also improve test environment determinism)
- Use `assert(false, msg) instead of `error(msg)` to report screen assertion
failures.
|
| |
|
| |
|
|
|
|
|
| |
- shortmess+=I: Remove intro screen
- background=light: Disregard COLORFGBG environment variable
|
|
|
|
| |
Replace the hexadecimal escape sequences, which are only supported by luajit
|
| |
|
|
|
|
|
|
|
|
|
| |
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
|