aboutsummaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAge
* test: luacheck updateJustin M. Keyes2017-03-01
| | | | | We pull luacheck HEAD, so this is a "catch up" commit to fix newly-discovered errors.
* terminal: Keep cursor position.Justin M. Keyes2017-03-01
| | | | | | Let the terminal dictate the normal-mode cursor position. This will be disorienting sometimes, but it is closer to what users expect vs always going to the last line.
* Merge #6191 from jamessan/vim-42ebd06Justin M. Keyes2017-02-28
|\ | | | | vim-patch:42ebd06,7.4.2098,6f1d9a0,7.4.2095
| * vim-patch:7.4.2095James McCoy2017-02-27
| | | | | | | | | | | | | | | | | | | | Problem: Man test fails when run with the GUI. Solution: Adjust for different behavior of GUI. Add assert_inrange(). https://github.com/vim/vim/commit/61c04493b00f85d0b97436260a9ef9ab82143b78 Only changes related to assert_inrange() were included, since we have a distinct man plugin.
* | test: Refactor fold tests (#5993)Matthieu Coudron2017-02-28
|/
* edit.c: CTRL-SPC: Insert previously-inserted text. #6090Matthew Malcomson2017-02-28
| | | | | | | | | | | | | Default Vim behavior of i_CTRL-<Space> is to insert the last-inserted text and exit insert mode. :help i_CTRL-@ Before this commit that did not happen because insert_handle_key() checks for NUL instead of checking for ' ' with a CTRL `mod_mask`. I'm leaving the check for NUL despite the fact that at the moment that key is never seen when using the terminal UI (not for C-Space, nor C-@). This is because I assume it's still allowed for other front-ends to pass NUL, but at the moment the terminal UI isn't.
* vim-patch:7.4.2200James McCoy2017-02-27
| | | | | | | | Problem: Cannot get all information about a quickfix list. Solution: Add an optional argument to get/set loc/qf list(). (Yegappan Lakshmanan) https://github.com/vim/vim/commit/d823fa910cca43fec3c31c030ee908a14c272640
* Merge #6112 from ZyX-I/split-eval'/buf_get_changedtickJustin M. Keyes2017-02-27
|\ | | | | Better b:changedtick support
| * buffer: Hide one of the asserts from lua parserZyX2017-02-25
| |
| * *: Fix linter errorsZyX2017-02-23
| |
| * api: Make sure dict_set_var doesn’t edit read-only valuesZyX2017-02-23
| | | | | | Fixes #6147
| * functests: Destroy accidental folds in api/vim_specZyX2017-02-23
| |
| * eval: Forbid (un)locking b:changedtickZyX2017-02-23
| | | | | | Port of vim-patch:8.0.0343
| * eval: Make sure `islocked('b:.changedtick')` does not error outZyX2017-02-23
| | | | | | Port of vim-patch:8.0.0345
| * eval: Specify more precise len for var_check_ro in get_lvalZyX2017-02-23
| |
| * functests: Add some more testsZyX2017-02-23
| |
| * buffer: Forbid unletting b:changedtickZyX2017-02-23
| |
| * eval: Refactor item_lockZyX2017-02-23
| | | | | | If I am not mistaking, this commit should not change any functionality.
| * eval: Make sure that b:changedtick may not be unlocked via :unlo b:varZyX2017-02-23
| | | | | | It still may be unlocked by `:unlock b:.var`.
| * functests: Add testsZyX2017-02-23
| | | | | | Contains a number of FIXMEs.
| * buffer: Bind b:changedtick to b:['changedtick'], remove special casesZyX2017-02-23
| |
| * api/buffer: Add nvim_buf_get_changedtick methodZyX2017-02-23
| |
* | Merge #6111 from ZyX-I/split-eval'/os-fileioJustin M. Keyes2017-02-27
|\ \ | | | | | | Refactor writefile() and create more tests for it
| * | eval: Fix error messages from writefileZyX2017-02-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 1. When calling writefile(list, fname, []) do not show error message twice. 2. Do not allow file name to be overwritten for writefile([1], 2). 3. Do not show “Can’t open file with an empty name” error after error like “using Float as a String” when type of the second argument is not correct. 4. Do not give multiple error messages and still continue for code like `writefile(["test", [], [], [], "tset"])`. Note that to fix 4. ideally I need tv_check_str_or_nr which is currently present in two PRs: #6114 and #5119. I would want to avoid copying this function into a yet another PR. Ref vim/vim#1476.
| * | eval: writefile: Give more adequate IO errors and do not call putc()ZyX2017-02-14
| | |
* | | test: screen_setup(): Detect spawn failures, usage errors.Justin M. Keyes2017-02-26
| | |
* | | test: screen_setup(): Support `cols` parameter.Justin M. Keyes2017-02-26
| | |
* | | test/window_split_tab_spec.lua: fixupJustin M. Keyes2017-02-26
| | | | | | | | | | | | | | | Make the test work after the "follows cursor" changes. This "auto-resize" feature is going away soon, anyways.
* | | terminal: Follow output only if cursor is at end.Justin M. Keyes2017-02-26
| | | | | | | | | | | | | | | | | | Closes #2257 Closes #2636 References #2683
* | | terminal: 'scrollback'Justin M. Keyes2017-02-26
| | | | | | | | | | | | Closes #2637
* | | terminal: Don't redraw the entire screen when resizing (#6167)Tommy Allen2017-02-26
| |/ |/|
* | win: test: Fix closure jobs test on WindowsJames McCoy2017-02-23
| |
* | Merge remote-tracking branch 'origin/master' into lambdaJames McCoy2017-02-22
|\ \
| * \ Merge #6137 from justinmk/cmdline-ctrl-rJustin M. Keyes2017-02-19
| |\ \ | | | | | | | | cmdline: CTRL-R: Omit trailing ^M character
| | * | cmdline: CTRL-R: Omit trailing <CR>.Justin M. Keyes2017-02-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The "technically correct" interpretation is to execute the first line that is seen (and this is what happens on middle-click paste in Vim). ^M is only intended to "defuse" the newline, so the user can review it. The parent commit changed the behavior to insert <Space> between lines, but that's a higher-risk change: it is arguably possible that some user *wants* the literal ^M chars when e.g. assigning to a register: :let @a='<C-R>b' To avoid that risk, keep the old behavior and only omit the last ^M. This makes `yy:<C-R>0` nicer at no cost.
| | * | cmdline: CTRL-R: <Space> instead of CR between lines.Justin M. Keyes2017-02-18
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | ^M isn't any more "correct" than space: the "technically correct" interpretation is to execute the first line that is seen (and this is what happens on middle-click paste in Vim). ^M is only intended to defuse the newline, so that the user can review the command. We can do that with a space instead, and then the command can be executed without having to fix it up first.
| * | | eval.c: has("unnamedplus"). (#6136)Kurt Bonatz2017-02-18
| |/ / | | | | | | | | | | | | Return 1 for UNIX with a functioning clipboard provider. Closes #6103
| * | Merge #6114 'Partial string handling refactoring'.Justin M. Keyes2017-02-17
| |\ \
| | * | *: Partial string handling refactoringZyX2017-02-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Main points: - Replace `char_u` with `char` in some cases. - Remove `str[len] = NUL` hack in some cases when `str` may be considered `const`.
| * | | ex_docmd.c: Allow unescaped spaces in :edit filename (#6119)Kurt Bonatz2017-02-15
| | | | | | | | | | | | | | | | | | | | | | | | This makes :edit consistent on all platforms. Also affects :argedit, et al. Wild (tab) completion doesn't work, though. Closes #6010
* | | | Allow lambdas to be used with jobs, timers and dictwatchers.Michael Ennen2017-02-14
|/ / /
* / / unittest: Filter out standard defines so that they do not spam stderr (#6113)Nikolai Aleksandrovich Pavlov2017-02-15
|/ /
* | ci: Make sure core* is the last component of pathZyX2017-02-14
| |
* | ci: Better core dump checkingZyX2017-02-14
|/ | | | | | | | | | | | | | | | - Do not exclude any directories from `find` search, remove dumps before tests instead. - Install `apport` on travis so that linux tests should produce core dumps (based on information from travis-ci/travis-ci#3754, not sure whether it still applies). - Check cores in lua so that one has an idea which test is failing exactly. Do this only 10% of time on linux because traversing the file system is slow. Unit tests are still not touched, though it is what `app` argument in `check_cores` is for. TODO? consider using `find`, it may be faster. Consider retiring `os.execute`, dealing with escaping is bad.
* build: `oldtest` target: TEST_FILE, NVIM_PRG (#6098)Justin M. Keyes2017-02-12
| | | | | | | | | | | | | | | | | | | | | | - Add support for TEST_FILE to the `oldtest` target, for consistency with the busted/lua tests. Caveat: with the busted/lua tests TEST_FILE takes a full path, whereas for `oldtest` it must be "test_foo.res". - Add support for NVIM_PRG, again so that all test-related targets are consistent. - Use consistent name for NVIM_PRG. But still need to support NVIM_PROG for QuickBuild CI. Note: The `oldtest` target is driven by the top-level Makefile, because it requires a TTY. CMake 3.2 added a USES_TERMINAL flag to add_custom_target(). But we support CMake 2.8... add_custom_target(oldtest COMMAND make clean COMMAND make NVIM_PRG=$<TARGET_FILE:nvim> $ENV{MAKEOVERRIDES} DEPENDS nvim WORKING_DIRECTORY "${CMAKE_CURRENT_SOURCE_DIR}/src/nvim/testdir" USES_TERMINAL true )
* eval: Add id() function and make printf("%p") return something useful (#6095)Nikolai Aleksandrovich Pavlov2017-02-11
|
* test: executable(): AppVeyor: Ignore "sibling" failureJustin M. Keyes2017-02-04
| | | | | This test sometimes fails on AppVeyor, but we still want to exercise the code path and get at least a "soft" notification in the pending list.
* win: executable(): full path without extensionJustin M. Keyes2017-02-04
| | | | Absolute path is considered executable even *without* an extension.
* vim-patch:8.0.0280Justin M. Keyes2017-02-04
| | | | | | | | | | patch 8.0.0280: problem setting multi-byte environment var on MS-Windows Problem: On MS-Windows setting an environment variable with multi-byte strings does not work well. Solution: Use wputenv when possible. (Taro Muraoka, Ken Takata) 7c23d1d9d9cc
* test: helpers.clear(): Set common env vars only if not passed.Justin M. Keyes2017-02-04
|
generated by cgit (git 2.34.1) at 2025-12-11 00:22:29 +0000