aboutsummaryrefslogtreecommitdiff
path: root/test/functional/ex_cmds/menu_spec.lua
Commit message (Collapse)AuthorAge
* test: avoid redundant clear() #7340Justin M. Keyes2017-10-16
|
* More testsKillTheMule2017-10-02
|
* menu_get: adjust tests for prettyprintingKillTheMule2017-10-01
| | | | ... and add a bit of new testing
* menu_get(): docJustin M. Keyes2017-07-28
|
* viml: introduce menu_get() function #6322Matthieu Coudron2017-07-28
| | | | menu_get({path}, {modes}). See :h menu_get.
* functests: Fix linter errorsZyX2017-04-09
|
* functests: Replace execute with either command or feed_commandZyX2017-04-09
| | | | | | | | | | Hope this will make people using feed_command less likely: this hides bugs. Already found at least two: 1. msgpackparse() will show internal error: hash_add() in case of duplicate keys, though it will still work correctly. Currently silenced. 2. ttimeoutlen was spelled incorrectly, resulting in option not being set when expected. Test was still functioning somehow though. Currently fixed.
* test: functional: Remove unnecessary use of clipboard registerJames McCoy2016-06-15
| | | | | | | | | menu_spec.lua yanks to the clipboard, but never pastes from it. This can leave a child xsel process waiting around for something to paste the content, causing the test process to hang. Since the test isn't explicitly trying to exercise the clipboard, simply use the default register.
* 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.
* test: menu_spec: avoid screen test.Justin M. Keyes2015-10-04
| | | | | Redraw can be flaky especially when remote commands happen during command-mode. Assert the state directly instead of using Screen.
* menu: support :emenu invoked by cmenu map.bambu2015-10-03
|
* menu: Fix :emenu mode detection #2992Robin Allen2015-07-22
A menu item can have separate bindings for each Vim mode. :emenu checks to see which binding it should execute. But, it assumes it can only be called from Normal mode, so its mode detection is based on some guesswork. For instance, it detects if you've just used C-O and, if so, uses the Insert mode binding. Now that :emenu can be called from any mode (via vim_command), this commit has it check the actual mode we're in, and simply use the binding for that mode if we aren't in Normal mode.