aboutsummaryrefslogtreecommitdiff
path: root/test/functional
Commit message (Collapse)AuthorAge
...
| * | | | | Merge pull request #6704 from bfredl/luaexecBjörn Linse2017-05-13
| |\ \ \ \ \ | | | | | | | | | | | | | | execute lua directly from the remote API
| | * | | | | api: execute lua directly from the remote apiBjörn Linse2017-05-13
| | | |/ / / | | |/| | |
| * | | | | Merge pull request #6514 from jamessan/gcc-7-fixesJames McCoy2017-05-13
| |\ \ \ \ \ | | | | | | | | | | | | | | Fix GCC 7 issues
| | * | | | | regexp_nfa: Fix invalid fallthrough in character class detectionJames McCoy2017-05-12
| | |/ / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When the end character in a range matches a different standard range (e.g., [0-z]), the range would be incorrectly detected as the class of the end character (CLASS_az). Instead of using a fallthrough, immediately FAIL when the end character doesn't match the expected range.
| * | | | | Merge #6731 from ZyX-I/fix-oneline-script-skipJustin M. Keyes2017-05-13
| |\ \ \ \ \ | | |/ / / / | |/| | | |
| | * | | | functests: Replace check_provider -> missing_provider with err reportZyX2017-05-13
| | | | | |
| | * | | | functests: Test invalid behaviourZyX2017-05-13
| | |/ / / | | | | | | | | | | | | | | | Test correctly fail for oneline ruby, python and python3.
| * / / / api: add metadata for ui eventsBjörn Linse2017-05-10
| |/ / /
| * | | tests: Add tests for vim_strchrZyX2017-05-09
| | | |
| * | | Merge #4411 from ZyX-I/luaviml'/luaJustin M. Keyes2017-05-09
| |\ \ \
| | * | | functests: Fix testsZyX2017-05-08
| | | | |
| | * | | Merge branch 'master' into luaviml'/luaZyX2017-05-08
| | |\ \ \
| | * | | | functests: Check whether it is a problem with an arrayZyX2017-04-11
| | | | | |
| | * | | | functests: Add another check for the similar transformationZyX2017-04-11
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Reasoning is majorly the same: check whether lua has bug or API function has bug, but on the other side: previous commit is checking whether similar bug when using API via msgpack RPC, this commit is checking whether another API function used via lua bindings triggers the same bug. Should additionally give a hint about which lua code contains a bug.
| | * | | | functests: Test for “string cannot contain newline” set_lines errorZyX2017-04-11
| | | | | | | | | | | | | | | | | | | | | | | | Should make me able to determine whether they are lua bindings that contain a bug or set_lines.
| | * | | | functests: Make sure funcs.luaeval receives only one argumentZyX2017-04-11
| | | | | |
| | * | | | Merge branch 'master' into luaviml'/luaZyX2017-04-10
| | |\ \ \ \
| | * | | | | api: Rename _vim_id functions to nvim__idZyX2017-04-08
| | | | | | |
| | * | | | | Merge branch 'master' into luaviml'/luaZyX2017-04-08
| | |\ \ \ \ \
| | * | | | | | eval,functests: Fix linter errorsZyX2017-03-27
| | | | | | | |
| | * | | | | | functests: Add test for debug.debugZyX2017-03-27
| | | | | | | |
| | * | | | | | executor,functests: Add print() tests, some fixesZyX2017-03-27
| | | | | | | |
| | * | | | | | executor: Add :luafile commandZyX2017-03-27
| | | | | | | |
| | * | | | | | executor: Fix some memory leaksZyX2017-03-27
| | | | | | | |
| | * | | | | | executor,functests: Add tests for :luado, also some fixesZyX2017-03-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Fixes: 1. Allocate space for the NUL byte. 2. Do not exclude last line from range. 3. Remove code for sandbox: it is handled earlier. 4. Fix index in new_line_transformed when converting NULs to NLs. 5. Always allocate new_line_transformed, but save allocated value.
| | * | | | | | executor: Add :luado commandZyX2017-03-27
| | | | | | | |
| | * | | | | | doc,functests: Add documentationZyX2017-03-27
| | | | | | | | | | | | | | | | | | | | | | | | Missing: updates to various lists.
| | * | | | | | functests: Add tests for :luaZyX2017-03-27
| | | | | | | |
| | * | | | | | functests: Fix “function has more then 60 upvalues” errorZyX2017-03-27
| | | | | | | |
| | * | | | | | functests: Some more testsZyX2017-03-27
| | | | | | | |
| | * | | | | | functests: Move existing tests from lua_spec to lua/*, fix themZyX2017-03-27
| | | | | | | |
| | * | | | | | functests: Add some testsZyX2017-03-27
| | | | | | | |
| | * | | | | | functests: Test for error conditionsZyX2017-03-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | During testing found the following bugs: 1. msgpack-gen.lua script is completely unprepared for Float values either in return type or in arguments. Specifically: 1. At the time of writing relevant code FLOAT_OBJ did not exist as well as FLOATING_OBJ, but it would be used by msgpack-gen.lua should return type be Float. I added FLOATING_OBJ macros later because did not know that msgpack-gen.lua uses these _OBJ macros, otherwise it would be FLOAT_OBJ. 2. msgpack-gen.lua should use .data.floating in place of .data.float. But it did not expect that .data subattribute may have name different from lowercased type name. 2. vim_replace_termcodes returned its argument as-is if it receives an empty string (as well as _vim_id*() functions did). But if something in returned argument lives in an allocated memory such action will cause double free: once when freeing arguments, then when freeing return value. It did not cause problems yet because msgpack bindings return empty string as {NULL, 0} and nothing was actually allocated. 3. New code in msgpack-gen.lua popped arguments in reversed order, making lua bindings’ signatures be different from API ones.
| | * | | | | | executor/converter: Make it possible to supply `{}` to Dictionary argZyX2017-03-27
| | | | | | | |
| | * | | | | | executor/converter: Make nlua_pop_Object not recursiveZyX2017-03-27
| | | | | | | |
| | * | | | | | executor/converter: Fix how maxidx is determinedZyX2017-03-27
| | | | | | | |
| | * | | | | | executor/converter: Fix conversion of self-containing containersZyX2017-03-27
| | | | | | | |
| | * | | | | | executor: Make sure it works with API valuesZyX2017-03-27
| | | | | | | |
| | * | | | | | viml/executor: Directly generate typval_T valuesZyX2017-03-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Note: this will *still* crash when using API in cases similar to the one described in first commit. Just it needs different code to reproduce.
| * | | | | | | tests: add basic test for 'winhighlight`Björn Linse2017-05-08
| | | | | | | |
| * | | | | | | options: allow different highlights in windowsBjörn Linse2017-05-08
| | |_|_|/ / / | |/| | | | |
| * | | | | | tui: Also fix "linux*" terminfo entries. #6673Jonathan de Boyne Pollard2017-05-04
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The terminfo entry for linux only advertises 8 colours, but nvim tries to make it display 16 colours anyway, resulting in erroneous SGR control sequences for colours 8 and above. The Linux kernel terminal emulator itself has actually understood the 256-colour control sequences since version 4.8 and the 16-colour control sequences since version 4.9. Thus we apply the same terminfo fixup as we apply for *xterm* and *256*, to emit the 16-colour and 256-colour control sequences even if terminfo's setaf and setab do not advertise them.
| * | | | | | Use vim_strchr(s, c) when c may be NUL (#6656)James McCoy2017-05-03
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | As part of the refactoring in #5119, some vim_strchr() were changed to strchr(). However, vim_strchr() behaves differently than strchr() when c is NUL, returning NULL instead of a pointer to the NUL. Revert the strchr() calls where it isn't known whether c is NUL, since this causes a semantic change the surrounding code doesn't expect. In the case of #6650, this led to a heap overrun. Closes #6650
| * | | | | | NVIM v0.2.0v0.2.0Justin M. Keyes2017-05-01
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | |