aboutsummaryrefslogtreecommitdiff
path: root/test
Commit message (Collapse)AuthorAge
...
| * | | | test: remove 003_cindent_spec.luazeertzjq2022-01-31
| | | | | | | | | | | | | | | | | | | | This no longer needed as Vim patch 8.1.1434 has been ported.
* | | | | [RFC] fix: has('python') error (#17252)Shougo2022-01-31
|/ / / / | | | | | | | | | | | | | | | | * fix: has('python') error * fix: functional tests
* | | | chore: typo fixes (#16921)dundargoc2022-01-29
| | | | | | | | | | | | Co-authored-by: zeertzjq <zeertzjq@outlook.com>
* | | | vim-patch:8.2.3917: the eval.txt help file is way too bigDaniel Steinberg2022-01-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: The eval.txt help file is way too big. Solution: Move the builtin function details to a separate file. https://github.com/vim/vim/commit/1cae5a0a034d0545360387407a7a409310f1efe2 Note: Neovim-specific references to |functions| were changed to |builtin-functions|. This included updates to: 1. test/functional/vimscript/functions_spec.lua 2. test/functional/vimscript/eval_spec.lua 3. runtime/doc/lua.txt
* | | | Merge pull request #17222 from bfredl/babajpy2bfredl2022-01-29
|\ \ \ \ | | | | | | | | | | feat(provider)!: remove support for python2 and python3.[3-6]
| * | | | feat(provider)!: remove support for python2 and python3.[3-5]Björn Linse2022-01-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | These versions of python has reached End-of-life. getting rid of python2 support removes a lot of logic to support two incompatible python versions in the same version.
* | | | | Merge pull request #17192 from zeertzjq/aucmd-redrawingdisabledbfredl2022-01-29
|\ \ \ \ \ | |/ / / / |/| | | | fix: set RedrawingDisabled before entering aucmd_win
| * | | | fix: set RedrawingDisabled before entering aucmd_winzeertzjq2022-01-25
| | |/ / | |/| |
* | | | vim-patch:8.2.4090: after restoring a session buffer order can be quite ↵Evgeni Chasnovski2022-01-29
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | different (#17112) Problem: After restoring a session buffer order can be quite different. Solution: Create buffers first. (Evgeni Chasnovski, closes vim/vim#9520) https://github.com/vim/vim/commit/26ebf1f036517ebeacf571c333a83cca7e13bbe2 --------------- As in Vim, this basically reverts 8.1.0829 providing different solution (see vim/vim#9520). Regarding Neovim, this basically reverts changes from #15062. Test about restoring same terminals was a bit too restrictive with using actual buffer ids, which changed with this patch (now they should be in the same order as at `mksession` call), so I tweaked it.
* | | | Merge pull request #17209 from bb010g/patch-1bfredl2022-01-29
|\ \ \ \ | | | | | | | | | | fix(eval): v:lua support for `-` in module names
| * | | | fix(eval): v:lua support for `-` in module namesbb010g2022-01-28
| | | | |
* | | | | fix(input): remove reinterpreted ALT/META chords from recorded macrozeertzjq2022-01-29
|/ / / /
* | | | Merge pull request #17183 from notomo/expose-extmark-right-gravitybfredl2022-01-28
|\ \ \ \ | | | | | | | | | | feat(api): expose extmark right_gravity and end_right_gravity
| * | | | feat(api): expose extmark right_gravity and end_right_gravitynotomo2022-01-24
| | | | |
* | | | | fix(completion): update submode message when selecting from API (#17022)zeertzjq2022-01-28
| | | | |
* | | | | Merge pull request #17175 from zeertzjq/vim-8.2.3095bfredl2022-01-27
|\ \ \ \ \ | | | | | | | | | | | | vim-patch:8.2.3095: with 'virtualedit' set to "block" block selection is wrong
| * | | | | vim-patch:8.2.3095: with 'virtualedit' set to "block" block selection is wrongzeertzjq2022-01-27
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: With 'virtualedit' set to "block" block selection is wrong after using "$". (Marco Trosi) Solution: Compute the longest selected line. (closes vim/vim#8495) https://github.com/vim/vim/commit/b17ab86e7b8712206aa9ea7198c28db969e25936
* | | | | | fix(ts): escape lang when loading parsers (#16668)Lewis Russell2022-01-27
|/ / / / / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | When trying to load a language parser, escape the value of the language. With language injection, the language might be picked up from the buffer. If this value is erroneous it can cause `nvim_get_runtime_file` to hard error. E.g., the markdown expression `~~~{` will extract '{' as a language and then try to get the parser using `parser/{*` as the pattern.
* | | | | Merge pull request #17191 from zeertzjq/vim-8.2.4203bfredl2022-01-27
|\ \ \ \ \ | | | | | | | | | | | | vim-patch:8.2.4203: entering a character with CTRL-V may include modifiers
| * | | | | test: add more tests for Insert mode Ctrl-Vzeertzjq2022-01-25
| | |/ / / | |/| | |
* | | | | Merge pull request #17155 from zeertzjq/vim-8.2.3121bfredl2022-01-27
|\ \ \ \ \ | | | | | | | | | | | | vim-patch:8.2.{3121,3410}: two 'listchars' fixes
| * | | | | vim-patch:8.2.3121: 'listchars' "exceeds" character appears in foldcolumnzeertzjq2022-01-21
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: 'listchars' "exceeds" character appears in foldcolumn. Window separator is missing. (Leonid V. Fedorenchik) Solution: Only draw the "exceeds" character in the text area. Break the loop when not drawing the text. (closes vim/vim#8524) https://github.com/vim/vim/commit/41fb723ee97baa2f095cde601a5a144b168b7a6b
* | | | | | Merge pull request #17174 from zeertzjq/vim-8.2.3153bfredl2022-01-27
|\ \ \ \ \ \ | | | | | | | | | | | | | | vim-patch:8.2.3153: URLs with a dash in the scheme are not recognized
| * | | | | | test(unit): add unit tests for path_with_urlzeertzjq2022-01-24
| | |_|/ / / | |/| | | |
* | | | | | Merge pull request #17102 from zeertzjq/vim-8.2.1762bfredl2022-01-27
|\ \ \ \ \ \ | |_|_|/ / / |/| | | | | vim-patch:8.2.1762: when a timer uses :stopinsert completion isn't stopped
| * | | | | vim-patch:8.2.1762: when a timer uses :stopinsert completion isn't stoppedzeertzjq2022-01-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: When a timer uses :stopinsert Insert mode completion isn't stopped. (Stanley Chan) Solution: Call ins_compl_prep(ESC). https://github.com/vim/vim/commit/d0e1b7103c14eb0d175c6b245b4b6ed93a204da9
* | | | | | Merge pull request #15910 from glacambre/silent_stdioopenbfredl2022-01-24
|\ \ \ \ \ \ | |_|/ / / / |/| | | | | feat(--headless): do not print anything when stdioopen() has been used
| * | | | | feat(--headless): add on_print callback to stdioopenglacambre2022-01-24
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This commit adds an on_print callback to stdioopen's dictionary argument which lets the caller specify a function called each time neovim will try to output something to stdout (e.g. on "echo" or "echoerr" in --headless mode).
* | | | | | Merge pull request #17156 from zeertzjq/vim-8.2.3584bfredl2022-01-23
|\ \ \ \ \ \ | | | | | | | | | | | | | | vim-patch:8.2.{3584,3586,3587}: :command "-keepscript" argument
| * | | | | | vim-patch:8.2.3584: "verbose set efm" reports location of the :compiler commandzeertzjq2022-01-21
| | |_|/ / / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Problem: "verbose set efm" reports the location of the :compiler command. (Gary Johnson) Solution: Add the "-keepscript" argument to :command and use it when defining CompilerSet. https://github.com/vim/vim/commit/58ef8a31d7087d495ab1582be5b7a22796ac2451
* | | | | | test(input): add more tests for K_SPECIAL escaping in ins_char_typebuf()zeertzjq2022-01-23
| | | | | |
* | | | | | fix(input): put modifiers back into typeahead buffer when neededzeertzjq2022-01-23
| | | | | |
* | | | | | Merge pull request #16936 from zeertzjq/no-escape-csibfredl2022-01-21
|\ \ \ \ \ \ | | | | | | | | | | | | | | input: never escape CSI bytes and clean up related names and comments
| * | | | | | refactor: remove CSI unescaping and clean up related names and commentszeertzjq2022-01-21
| | | | | | |
| * | | | | | fix(input): never escape CSI byteszeertzjq2022-01-21
| |/ / / / /
* | | | | | Merge pull request #17076 from notomo/expose-extmark-more-detailsbfredl2022-01-21
|\ \ \ \ \ \ | |/ / / / / |/| | | | | feat(api): expose extmark more details
| * | | | | feat(api): expose extmark more detailsnotomo2022-01-20
| | |_|/ / | |/| | |
* / | | | test(put_spec): correctly order parameters to eq() (#17134)zeertzjq2022-01-19
|/ / / / | | | | | | | | | | | | The first parameter to eq() should be the expected value, and the second parameter should be the actual value.
* | | | Merge pull request #16836 from bfredl/mark2bfredl2022-01-15
|\ \ \ \ | | | | | | | | | | refactor(marks): use a more efficient representation with less pointer indirection
| * | | | refactor(extmarks): use a more efficient representationBjörn Linse2022-01-15
| | |/ / | |/| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | marktree.c was originally constructed as a "generic" datatype, to make the prototyping of its internal logic as simple as possible and also as the usecases for various kinds of extmarks/decorations was not yet decided. As a consequence of this, various extra indirections and allocations was needed to use marktree to implement extmarks (ns/id pairs) and decorations of different kinds (some which is just a single highlight id, other an allocated list of virtual text/lines) This change removes a lot of indirection, by making Marktree specialized for the usecase. In particular, the namespace id and mark id is stored directly, instead of the 64-bit global id particular to the Marktree struct. This removes the two maps needed to convert between global and per-ns ids. Also, "small" decorations are stored inline, i.e. those who doesn't refer to external heap memory anyway. That is highlights (with priority+flags) are stored inline, while virtual text, which anyway occurs a lot of heap allocations, do not. (previously a hack was used to elide heap allocations for highlights with standard prio+flags) TODO(bfredl): the functionaltest-lua CI version of gcc is having severe issues with uint16_t bitfields, so splitting up compound assignments and redundant casts are needed. Clean this up once we switch to a working compiler version.
* | | | feat: use nvim_buf_set_extmark for vim.highlight (#16963)Michael Lingelbach2022-01-15
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Closes https://github.com/neovim/neovim/issues/13647 This allows customizing the priority of the highlights. * Add default priority of 50 * Use priority of 200 for highlight on yank * use priority of 40 for highlight references (LSP)
* | | | Merge pull request #17001 from mjlbach/feat/non-strict-extmarksbfredl2022-01-15
|\ \ \ \ | |/ / / |/| | | feat(extmarks): add strict option
| * | | Hopefully last attemptMichael Lingelbach2022-01-15
| | | |
| * | | Address review r3Michael Lingelbach2022-01-15
| | | |
* | | | fix(filetype): expand tildes in filetype patterns (#17091)Gregory Anders2022-01-14
| | | | | | | | | | | | | | | | | | | | | | | | | | | | This allows patterns like ["~/.config/foo"] = "fooscript" to work.
* | | | Merge pull request #16998 from zeertzjq/lua-vim-var-funcrefbfredl2022-01-14
|\ \ \ \ | | | | | | | | | | feat(api, lua): more conversions between LuaRef and Vim Funcref
| * | | | feat(api, lua): more conversions between LuaRef and Vim Funcrefzeertzjq2022-01-13
| | | | |
* | | | | Merge pull request #17034 from zeertzjq/compl-lua-selectbfredl2022-01-13
|\ \ \ \ \ | | | | | | | | | | | | feat(completion): support selecting item via API from Lua mapping
| * | | | | feat(completion): support selecting item via API from Lua mappingzeertzjq2022-01-11
| | | | | |
* | | | | | fix(lsp): strictly enforce passing offset encoding (#17049)Michael Lingelbach2022-01-13
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This removes the "fallback" to utf-16 in many of our helper functions. We should always explicitly pass these around when possible except in two locations: * generating params with help utilities called by buf.lua functions * the buf.lua functions themselves Anything that is called by the handler should be passed the offset encoding.
generated by cgit (git 2.34.1) at 2025-06-24 13:23:18 +0000