rneovim.git/test/functional/shada, branch v0.1.6

vim-patch:7.4.2212

2016-10-22T21:43:14+00:00

Problem:    Mark " is not set when closing a window in another tab. (Guraga)
Solution:   Check all tabs for the window to be valid. (based on patch by
            Hirohito Higashi, closes vim/vim#974)

https://github.com/vim/vim/commit/e59215c7dcae17b03daf39517560cfaa03314f5a

shada: Fix non-writeable ShaDa directory handling

2016-09-05T01:45:48+00:00

Before this change,

    nvim -i /etc/shada

segfaults on exit if the file does not exist and user does not have
permissions to create the file at /etc/shada.

Closes #5296
Reported in #5277
https://github.com/neovim/neovim/issues/5277#issuecomment-243937255

api: consistently use nvim_ prefix and update documentation

2016-08-31T19:57:06+00:00

functionaltest: Create lua helper for os.tmpname()

2016-08-31T10:32:28+00:00

In Windows Lua's os.tmpname() returns relative paths starting with \s,
prepend them with $TEMP to generate a valid path.

In OS X os.tmpname() returns paths in '/tmp' but they should be in
'/private/tmp'. We cannot use os_name() for platform detection because
some tests use tempname() before nvim is spawned, instead use one of the
following:

1. Set SYSTEM_NAME environment variable before calling the tests, it
   is set from CMAKE_SYSTEM_NAME(i.e. uname -s or 'Windows')
2. Call uname -s
3. Assume windows

Mark some functional tests as pending in Windows

2016-08-26T07:21:41+00:00

functests: Check logs in lua code

2016-06-10T18:50:49+00:00

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.

eval: let getreg() return valid list for an undefined register

2016-04-21T16:11:06+00:00

vim-patch:7.4.1755
this prevents a crash when the list is used in setreg() later

shada: Make sure that NIL and EXT values can also be parsed back

2016-04-17T23:46:34+00:00

Note: currently they are both *dumped*, but parsing them produces an error. This
is inappropriate: variables should either be skipped with error message when
dumping or should be read back properly.

It also appears that I did not have test for “has wrong variable value type”
error, so nothing got removed from errors_spec.

Update lua client to 0.0.1-24

2016-04-13T12:21:32+00:00

The new version of the lua client uses libmpack as a backend, and some test
scripts had to be updated to reflect that.

Synchronize shada reset helper with other functional tests

2016-04-12T02:07:52+00:00