aboutsummaryrefslogtreecommitdiff
path: root/test/functional/shada
Commit message (Collapse)AuthorAge
* tests: stderr output contains `cp` noiseJustin M. Keyes2018-01-05
| | | | closes #7811
* mark: Make sure that jumplist item will not have zero lnumZyX2017-12-24
| | | | Fixes #7169
* test/shada: fixup for Windows backslashes #7287Ignas Anikevicius2017-10-02
|
* shada: Make sure that code does not attempt to read too long itemsZyX2017-07-04
| | | Fixes #6957
* test: Fix and add cases for unnamed registerAdnoC2017-05-31
| | | | | | | | Also: Add ru to shada tests with all keys Add test for unset unnamed and register 0
* eval/shada: Add testing for unnamed register with setreg and startupAdnoC2017-05-31
|
* shada: Remember whether "0 or "1 was the unnamed registerJames McCoy2017-05-24
| | | | Ref #4645
* eval: Fix len argument to xstrlcatZyX2017-03-29
|
* test: Windows: Re-enable shada functional testsRui Abreu Ferreira2017-01-08
| | | | | One of the tests remains disabled until we figure out the expected behaviour of mkdir() on Windows when `prot` is passed.
* shada: Save current cursor position before saving jumpsZyX2017-01-04
|
* shada: Respect the optional buffer count for shada-%James McCoy2016-12-12
| | | | Closes #5759
* build: Target luacheck HEAD.Justin M. Keyes2016-11-17
| | | | | | | | | | | | https://github.com/mpeterv/luacheck/pull/81#issuecomment-261099606 > If you really want to use bleeding-edge version you should get the > rockspec from master branch, not a fixed commit ... > The correct way to install from a specific commit is cloning that > commit and running "luarocks make" from project directory. The reason > is that running "install" or "build" on an scm rockspec fetches > sources from master but uses build description from the rockspec > itself, which may be outdated.
* Bump all nvim-specific error codes above E5000James McCoy2016-11-15
| | | | | | | | | | In order to not conflict with new error codes that Vim adds, all Neovim error codes should be above 5000. The three existing sub-5000 error codes (E926, E951, and E952) are now E50003, E5004, and E5005 respectively. E953 was removed in 6167ce6df2753d5474ad49aea19f5957128ab015, so just remove it from the help.
* encoding: update testsBjörn Linse2016-11-05
| | | | | | | Change shada reencoding tests to check for correct handling of UTF-8 and binary strings. Delete enc=latin1 json tests.
* test: Fix shada/marks_spec.lua failureJames McCoy2016-10-28
| | | | | | The 'dump and read back mark " from a closed tab' test needs to actually create a second tab. Since it wasn't doing so, the 'q!' command caused nvim to exit and the subsequent 'qall' command fails.
* vim-patch:7.4.2212Grzegorz Milka2016-10-22
| | | | | | | | 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 handlingZyX2016-09-04
| | | | | | | | | | | | | 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 documentationBjörn Linse2016-08-31
|
* functionaltest: Create lua helper for os.tmpname()Rui Abreu Ferreira2016-08-31
| | | | | | | | | | | | | | | 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 WindowsRui Abreu Ferreira2016-08-26
|
* functests: Check logs in lua codeZyX2016-06-10
| | | | | | 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 registerBjörn Linse2016-04-21
| | | | | 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 backZyX2016-04-18
| | | | | | | | | 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-24Thiago de Arruda2016-04-13
| | | | | 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 testsThiago de Arruda2016-04-11
|
* test: shada_spec: resolve symlinkJun T2016-02-12
| | | | | | If the build directory path has symlinks in it, 'make functionaltest' fails at shada_spec.lua:177 because readme_fname has symlink but nvim resolves the symlink when writing it into the shada file.
* functests: Update testsZyX2016-01-07
|
* shada: Continue dumping when variables failed to dumpZyX2015-12-18
| | | | Closes #3721
* Merge pull request #3724 from ZyX-I/fix-3635Justin M. Keyes2015-11-27
|\ | | | | shada: Do not save unlisted and quickfix buffers
| * shada: Do not save unlisted and quickfix buffersZyX2015-11-23
| | | | | | Fixes #3635
* | Merge pull request #3581 from ZyX-I/fix-shadaFelipe Morales2015-11-23
|\ \ | | | | | | Store last search direction when writing ShaDa files
| * | shada: Also store last search directionZyX2015-11-23
| |/ | | | | | | | | | | | | | | | | | | Note: it looks like viminfo files do not store search direction intentionally. After reading viminfo file search direction was considered to be “forward”. Note 2: all files created on earlier Neovim version will automatically receive “forward” direction. Fixes #3580
* / test/functional: clean up according to luacheck (part 1)Marco Hinz2015-11-23
|/
* Sort oldfiles in the marks_spec tests to avoid random ordering errors.John Szakmeister2015-11-06
| | | | | According to @ZyX-I in #3594, ordering is not important so let's use @tarruda's fix by sorting the results.
* functests: Add test to check expected behaviour (failing)ZyX2015-10-23
|
* shada: Fix memory leak and double free when setting both &vi and &sdZyX2015-10-08
|
* functests: Refactor tests:ZyX2015-10-08
| | | | | | | | - Remove unused variables. - Do not use helpers.nvim_feed in most cases. - Do not use helpers.nvim and helpers.nvim_eval at all. - Add helpers.funcs and helpers.\*meths special tables. Indexing such table creates functions which call helpers.call or helpers.nvim (and similar) with first argument equal to table index.
* shada: Fix jump/change list merging codeZyX2015-10-08
| | | | | | Errors happens under following conditions: 1. Jump/change list is full. 2. New jump/change list item should go between some of the old ones.
* shada: Make sure that shada-r option correctly ignores caseZyX2015-10-08
|
* shada: When using shada-r normalize option pathZyX2015-10-08
|
* functests: Move exc_exec to test.functional.helpersZyX2015-10-08
|
* functests: Do not disable pattern testsZyX2015-10-08
| | | | | Problem that led to this skip was fixed in [#3309][1]. [1]: https://github.com/neovim/neovim/commit/0a116c828debc6192a6bfb6bceb8cf020e867db0
* shada: Fix out-of-bounds array accessZyX2015-10-08
| | | | It leads to a memory leak as well. May overwrite wms->jumps_size.
* shada: Fix v:hlsearch save/restore and do not write empty patternsZyX2015-10-08
|
* shada,functests: Fix v:hlsearch saving/restoring handlingZyX2015-10-08
|
* documentation/functests: Replace NeoVim with NeovimZyX2015-10-08
|
* shada: Refuse to write ShaDa file when ShaDa was disabledZyX2015-10-08
|
* functests: Make one recover_spec test also use gdb or valgrindZyX2015-10-08
|
* eval,functests: Reference all additional_* items created by ShaDaZyX2015-10-08
|
* shada: Fix crash in hmll_insertZyX2015-10-08
| | | | | | | | | | | | | | | | | This problem made test64 to crash. Description of the bug: when removing entry from history when removed entry is not the last one it puts one element to free_entries list, but ignores free entries starting from last_free_element. Possible solutions: 1. First working: simply populate free_entries list with entries which are still free, starting from last_free_element. 2. Better (wastes less CPU): after free_entries list size goes to zero (which is the initial value) continue using last_free_element. 3. Even better (less memory): note that element from the list is *only* removed before adding another one. So replace free_entries array with one item. Also renamed last_free_element to last_free_entry: in any case most of the lines which mention it were altered.
generated by cgit (git 2.34.1) at 2025-06-24 13:23:22 +0000