| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
- After _spec suffix was added so busted could find the test, it failed.
- The original legacy test wrote to a "test.out", but the new test uses
register @A.
- Original test did not contain 1d and new test shouldn't either.
ref c152cdd0f34c10b3d3a8007838561556578685c6
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Migrate legacy test 77 which tests mf_hash_grow() to lua/busted.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
- The syntax `gui=` is invalid when setting properties of highlight group.
- Wait for the initial "-- More --" prompt before continuing. Required to avoid
a race condition
|
| |
|
|
|
| |
Now the attrentry_T structure will store all attributes in separate fields for
cterm and rgb UIs.
|
| |
|
|
|
| |
This test depends on terminal size to work correctly. After migration this
requirement is removed.
|
| |
|
|
|
|
|
|
|
| |
Problem: In Insert mode, after inserting a newline that inserts a comment
leader, CTRL-O moves to the right. (ZyX) Issue 57.
Solution: Correct the condition for moving the cursor back to the NUL.
(Christian Brabandt)
https://code.google.com/p/vim/source/detail?r=v7-4-492
|
| |
|
|
|
| |
Ignoring invalid key sequences simplifies input handling in UIs. The only
downside is having to use "<lt>" everytime a "<" is needed on functional tests.
|
| | |
|
| |
|
|
|
| |
Ignoring invalid key sequences simplifies input handling in UIs. The only
downside is having to use "<lt>" everytime a "<" is needed on functional tests.
|
| |\
| |
| | |
vim-patch:7.4.552
|
| | |
| |
| |
| |
| |
| |
| | |
Problem: Langmap applies to Insert mode expression mappings.
Solution: Check for Insert mode. (Daniel Hahler)
https://code.google.com/p/vim/source/detail?r=v7-4-552
|
| |\ \
| | |
| | | |
vim-patch:7.4.549
|
| | |/
| |
| |
| |
| |
| | |
Add new files for 7.4.549.
https://code.google.com/p/vim/source/detail?r=750a6986aa86a2bb3346631a353913b899d86748
|
| |/
|
|
| |
https://code.google.com/p/vim/source/detail?r=6a598be6d4e8
|
| |
|
|
|
|
|
| |
Problem: test_mapping fails for some people.
Solution: Set the 'encoding' option. (Ken Takata)
https://code.google.com/p/vim/source/detail?r=v7-4-488
|
| |
|
|
|
|
|
| |
Problem: A 0x80 byte is not handled correctly in abbreviations.
Solution: Unescape special characters. Add a test. (Christian Brabandt)
https://code.google.com/p/vim/source/detail?r=v7-4-483
|
| | |
|
| | |
|
| |
|
|
| |
Remove `expandtab` and add a missing trailing space from the legacy test.
|
| |
|
|
|
|
|
|
|
| |
See https://github.com/neovim/neovim/issues/1519 for failure report.
Cause : In OSX, /tmp is a symbolic link to /private/tmp, which causes
expected and got results different because of implicit
resolution.
Solution : Resolve path before setting expected value.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The vim_input function accepts raw terminal input and so is better to emulate
real user, especially because it is not deferred as vim_feedkeys.
Using this function required a number of changes:
- expect() was refactored to use curbuf_contents()
- The vim_eval function in request() was moved to curbuf_contents(). For most
cases this is enough(we only care for synchronizing api calls with user input
when verifying buffer contents).
- <C-@>(NUL) is preprocessed before being passed to replace_termcodes.
- Legacy test 4 had a bug that only became visible when using vim_input, it is
fixed now.
- An extra blank line deletion was required for test 101
The last two items show that vim_feedkeys because it is not 100% equivalent to
receiving terminal input.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
