aboutsummaryrefslogtreecommitdiff
path: root/test/functional/viml/completion_spec.lua
Commit message (Collapse)AuthorAge
* test: reorg #15698Justin M. Keyes2021-09-17
| | | | | | | | | | | | | | | | | | | | Problem: Subdirectories like "visual", "insert", "normal" encourage people to separate *related* tests for no good reason. Typically the _mode_ is not the relevant topic of a test (and when it is, _then_ create an appropriate describe() or it()). Solution: - Delete the various `test/functional/<mode>/` subdirectories, move their tests to more meaningful topics. - Rename `…/normal/` to `…/editor/`. - Move or merge `…/visual/*` and `…/insert/*` tests into here where appropriate. - Rename `…/eval/` to `…/vimscript/`. - Move `…/viml/*` into here also. * test(reorg): insert/* => editor/mode_insert_spec.lua * test(reorg): cmdline/* => editor/mode_cmdline_spec.lua * test(reorg): eval core tests => eval_spec.lua
* refactor(tests): use assert_alive() #15546Justin M. Keyes2021-09-01
|
* Don't show entire context when completingTony Chen2021-01-26
|
* feat: add completion to ':lua'TJ DeVries2021-01-26
|
* A Mudholland Dr. RecastBjörn Linse2020-10-19
| | | | | The commit summary maybe does not make sense, but calling a function that does not wait on anything `wait()` makes even less sense.
* vim-patch:8.1.1072: extending sign and foldcolumn below the text is ↵Marco Hinz2019-04-03
| | | | | | | | | | | | confusing (#9816) Problem: Extending sign and foldcolumn below the text is confusing. Solution: Let the sign and foldcolumn stop at the last text line, just like the line number column. Also stop the command line window leader. (Christian Brabandt) https://github.com/vim/vim/commit/8ee4c01b8c79a29065c1af05e5d9c0721069765f Closes https://github.com/neovim/neovim/issues/9613
* autocmd: rename MenuPopupChanged to CompleteChanged #9819Qiming zhao2019-03-31
|
* autocmd: add MenuPopupChanged autocmdchemzqm2019-03-15
| | | | | | Update src/nvim/auevents.lua Co-Authored-By: chemzqm <chemzqm@gmail.com>
* edit.c: Disable indent during completionlePerdu2019-03-03
| | | | closes #8345
* tests: improve robustness of immediate successes in screen testsBjörn Linse2018-10-15
|
* tests: introduce screen:expect{...} formBjörn Linse2018-08-27
|
* Merge #8377 'TextChangedP autocommand'Justin M. Keyes2018-05-19
|\
| * vim-patch:8.0.1494: no autocmd triggered in Insert mode with visible popup menuShougo Matsushita2018-05-14
|/ | | | | | | | | | Problem: No autocmd triggered in Insert mode with visible popup menu. Solution: Add TextChangedP. (Prabir Shrestha, Christian Brabandt, closes vim/vim#2372, closes vim/vim#1691) Fix that the TextChanged autocommands are not always triggered when sourcing a script. https://github.com/vim/vim/commit/5a093437199001a0d60d8e18e2b9539b99a7757c
* vim-patch:8.0.1493: completion items cannot be annotated (#8003)Shougo2018-02-18
| | | | | | | Problem: Completion items cannot be annotated. Solution: Add a "user_data" entry to the completion item. (Ben Jackson, coses vim/vim#2608, closes vim/vim#2508) https://github.com/vim/vim/commit/9b56a57cdae31f7a2c85d440392bf63d3253a158
* win: enable more functional testsJan Edmund Lazo2018-01-06
| | | | | | - plugin/shada_spec.lua: Use \r\n as Windows EOL for tests on BufWriteCmd, FileWriteCmd, FileAppendCmd. Alternative is 'set fileformat=unix'.
* Merge #7454 'ui: ext_wildmenu'Justin M. Keyes2017-10-31
| | | | | closes #6168 ref #5686
* api: nvim_ui_attach(): Flatten ext_* options.Justin M. Keyes2017-04-26
|
* api/ui: externalize tablineJustin M. Keyes2017-04-26
| | | | | | - Work with a bool[] array parallel to the UIWidget enum. - Rename some functions. - Documentation.
* 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.
* completion: fix segfault with ignorecase+infercase (#6452)Justin M. Keyes2017-04-06
| | | | | Helped-by: Matthew Malcomson <hardenedapple@gmail.com> Closes #6451
* *: Move some dictionary functions to typval.h and use char*ZyX2017-03-29
| | | | Also fixes buffer reusage in setmatches() and complete().
* 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.
* vim-patch:8.0.0041Tommy Allen2016-10-22
| | | | | | Problem: When using Insert mode completion but not actually inserting anything an undo item is still created. (Tommy Allen) Solution: Do not call stop_arrow() when not inserting anything.
* Merge pull request #5225 from equalsraf/windows-functionaltestsBjörn Linse2016-08-31
|\ | | | | Enable functional tests in Appveyor
| * Mark some functional tests as pending in WindowsRui Abreu Ferreira2016-08-26
| |
* | api/ui: add tests for popupmenu_external eventsBjörn Linse2016-08-29
|/ | | | update screen.lua to use new style nvim_ui_attach
* tests: don't ignore highlights in completion_specBjörn Linse2016-08-14
|
* 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.
* Testlinting.KillTheMule2016-05-10
| | | | | Missed in https://github.com/neovim/neovim/pull/4644/commits/fd3088b425b8c1f4f41eb715201e429ddd37af32
* Merge pull request #4644 from KillTheMule/vim-7.4.882Justin M. Keyes2016-05-04
|\ | | | | vim-patch:7.4.882
| * Even though the patch is not needed for neovim, add a test for the bugfixKillTheMule2016-04-29
| |
* | Add test for vim-patch 7.4.672KillTheMule2016-05-02
|/
* tests/ui: screen tests for completion popupmenuBjörn Linse2016-04-24
|
* 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.
* complete: noinsert/noselect should not set 'modified'. #4509Shougo Matsushita2016-04-09
|
* edit.c: K_EVENT should not hide the popupmenuBjörn Linse2016-03-17
| | | | Nor should K_FOCUSGAINED and K_FOCUSLOST.
* complete: disable folding when completingAnmol Sethi2016-03-09
| | | | Fixes vim/vim#643
* test: completion_spec: minor editsJustin M. Keyes2016-02-13
|
* tests: add always complete testsolawing2016-01-29
|
* test/functional: clean up according to luacheck (part 1)Marco Hinz2015-11-23
|
* completion: Initialize v:completed_item #2839Shougo Matsushita2015-06-20
| | | | | v:completed_item should always be a dict (not empty string), even before the first completion.
* Add complete() noinsert/noselect support #2792Shougo Matsushita2015-06-11
|
* Add noinsert and noselect features in completeopt #2564Shougo Matsushita2015-06-04
| | | | | | | | | | | | Backported from vim_dev: https://groups.google.com/forum/#!searchin/vim_dev/completeopt/vim_dev/tVsk0pdOGvs/fCzBbPkA4w0J Use case: https://github.com/Shougo/neocomplcache.vim/issues/426 Reviewed-by: Felipe Morales <hel.sheep@gmail.com> Reviewed-by: Scott Prager <splinterofchaos@gmail.com> Reviewed-by: Michael Reed <m.reed@mykolab.com>
* completion: Add v:completed_item feature #2563Shougo Matsushita2015-05-24
Reviewed-by: Michael Reed <m.reed@mykolab.com> Reviewed-by: Luke Andrew <luke.github@la.id.au> Reviewed-by: Justin M. Keyes <justinkz@gmail.com> Reviewed-by: Florian Walch <florian@fwalch.com>