aboutsummaryrefslogtreecommitdiff
path: root/test/functional
Commit message (Collapse)AuthorAge
...
| * | | | | vim-patch:7.4.1114Jurica Bradaric2016-04-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: delete() does not work well with symbolic links. Solution: Recognize symbolik links. https://github.com/vim/vim/commit/43a34f9f74fdce462fa250baab620264c28b6165
| * | | | | vim-patch:7.4.1107Jurica Bradaric2016-04-20
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: Vim can create a directory but not delete it. Solution: Add an argument to delete() to make it possible to delete a directory, also recursively. https://github.com/vim/vim/commit/da440d21a6b94d7f525fa7be9b1417c78dd9aa4c
* | | | | | Merge #3229 ':tcd'Justin M. Keyes2016-04-21
|\ \ \ \ \ \
| * | | | | | tcd: doc, error messagesJustin M. Keyes2016-04-21
| | | | | | |
| * | | | | | Implement tab-local working directory feature.HiPhish2016-04-20
| |/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | New ex commands: 'tcd', 'tchdir' Changed Vimscript functions: 'haslocaldir', 'getcwd' The ex-commands ':tcd' and ':tchdir' are the tab-local equivalents of ':lcd' and ':lchdir'. There are no new Vimscript functions introduced, instead the functions 'haslocaldir' and 'getcwd' take in optional arguments. See the documentation for details Since there is now different levels of local directory a simple boolean at source level is no longer sufficient; a new enumeration type is used for the scope-level from now on. The documentation has been accommodated for these new commands and functional tests have been written to test the feature.
* / / / / / 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
* | | | | test: remote/define.vim: Add some spice.Justin M. Keyes2016-04-18
| | | | |
* | | | | test: formatCase Nelson2016-04-18
| | | | |
* | | | | test: remote/define.vim: rangeCase Nelson2016-04-18
| | | | |
* | | | | test: convert test_marks.in.Justin M. Keyes2016-04-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | vim-patch:35e7594 https://github.com/vim/vim/commit/35e7594dd429f7a8a06cefd61c3e8d48b9bd74e2 "Add missing test files from 7.4.634 to the repository." The discrepancy between the expected getpos() result of the old test [0, 15, 2, 0] and the converted test [0, 3, 2, 0] is just a matter of how the buffer is constructed: in the old Vim test the buffer has a bunch of junk at the top. The central purpose of the test is to verify that the getpost("'a") does *not* return [0, 0, 0, 0].
* | | | | functests: Make json_functions_spec use new NIL where appropriateZyX2016-04-18
| | | | |
* | | | | eval/encode: Make sure that encoder can encode NULL variablesZyX2016-04-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds two undocumented v: variables: _null_list and _null_dict because I do not know a reproducible way to get such lists (though I think I heard about this) and dictionaries (do not remember hearing about them). NULL strings are obtained using $XXX_UNEXISTENT_VAR_XXX. Fixes crash in json_encode($XXX_UNEXISTENT_VAR_XXX). Other added tests worked fine before this commit.
* | | | | functests: Replace \xXX escapes with \DDD in lua codeZyX2016-04-18
| | | | |
* | | | | eval/encode: Dump FF character correctlyZyX2016-04-18
| | | | |
* | | | | eval: Treat [] and [""] as any other empty stringZyX2016-04-18
| | | | |
* | | | | eval: Fix overflow in error message in f_json_decodeZyX2016-04-18
| | | | |
* | | | | documentation,functests: State that UTF-8-only support is intentionalZyX2016-04-18
| | | | |
* | | | | eval/decode: Accept `\r` as space characterZyX2016-04-18
| | | | |
* | | | | eval/decode: Reject even more numbersZyX2016-04-18
| | | | | | | | | | | | | | | | | | | | Rejects leading zeroes and numbers like 1.e+5 (decimal dot with missing number with signed exponent).
* | | | | eval/decode: Reject more numbers, accept 1e5ZyX2016-04-18
| | | | |
* | | | | eval/decode: Do not loose high surrogates followed by high surrogatesZyX2016-04-18
| | | | |
* | | | | eval/decode: Make sure that error messages do not cause overflowZyX2016-04-18
| | | | |
* | | | | eval/decode: Make sure that blank input does not crash NeovimZyX2016-04-18
| | | | |
* | | | | eval/decode: Make sure that U+00C3 is parsed correctlyZyX2016-04-18
| | | | |
* | | | | functests: Make sure that json functions are tested with C messagesZyX2016-04-18
| | | | |
* | | | | eval/decode: Rename brackets in error messagesZyX2016-04-18
| | | | | | | | | | | | | | | | | | | | | | | | | U+007D is officially RIGHT CURLY BRACKET. U+005D is officially RIGHT SQUARE BRACKET.
* | | | | encode: Handle incomplete surrogates like `\uSURR\uOTHR` properlyZyX2016-04-18
| | | | |
* | | | | encode: Fail to dump NaN and infinityZyX2016-04-18
| | | | | | | | | | | | | | | | | | | | Thanks to vim/vim#654
* | | | | eval: Rename json* functions to json_*ZyX2016-04-18
| | | | |
* | | | | api: Replace set_var(name, NIL) with del_var(name)ZyX2016-04-18
| | | | |
* | | | | eval/encode: Fix invalid UTF-8 strings handling:ZyX2016-04-18
| | | | | | | | | | | | | | | | | | | | 1. Do not allow reading past buffer end when creating error messages. 2. Fix surrogate pairs range, avoid magic constants.
* | | | | eval/encode: Fix non-utf-8 &encoding handling, add testsZyX2016-04-18
| | | | |
* | | | | 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.
* | | | | eval: Port parts of 7.4.1267 that are not already presentZyX2016-04-18
| | | | |
* | | | | eval: Make assert_true and assert_false accept v:true and v:falseZyX2016-04-18
| | | | |
* | | | | eval: Remove v:noneZyX2016-04-18
| | | | | | | | | | | | | | | | | | | | | | | | | To get v:none back just rever this commit. This will not make json*() functions compatible with Vim though.
* | | | | eval/decode: Add support for special mapsZyX2016-04-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Special dictionaries representing map are created when encountering duplicate key or when key is empty or contains NUL. Also checks that values are separated by a comma/colon properly.
* | | | | eval/decode: Parse strings with NUL to special dictionariesZyX2016-04-18
| | | | |
* | | | | eval/decode: Fix surrogate pairs processingZyX2016-04-18
| | | | |
* | | | | eval/decode: Fail on control and invalid unicode charactersZyX2016-04-18
| | | | |
* | | | | eval/decode: Make msgpackparse() function use new v: varsZyX2016-04-18
| | | | |
* | | | | eval: Add jsondecode() functionZyX2016-04-18
| | | | |
* | | | | functests/msgpack: Test dumping special nil and bool dictsZyX2016-04-18
| | | | |
* | | | | runtime/msgpack: Add support for special valuesZyX2016-04-18
| | | | |
* | | | | eval: Add special variables v:false, v:null, v:noneZyX2016-04-18
| | | | |
* | | | | eval: Add special variable typeZyX2016-04-18
| | | | |
* | | | | eval: Add jsonencode() functionZyX2016-04-18
| | | | | | | | | | | | | | | Ref #3471
* | | | | functests(msgpack): Fix location of one of the testsZyX2016-04-18
| | | | |
* | | | | functests(msgpack): Fix test namesZyX2016-04-18
| | | | |
* | | | | Make completion_spec.lua more robustKillTheMule2016-04-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Having a tags file in the calling directory of make test would make this test fail, so disable tag file completion for it. Disable all other options except the current buffer, to, applying the principle of least surprise.
generated by cgit (git 2.34.1) at 2025-07-10 01:23:56 +0000