aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* feat: add vim.str_utf_{start,end} (#16129)Michael Lingelbach2021-10-30
| | | | | vim.str_utf_{start,end} return the offset from the current position to the start and end of the current utf-character (nearest codepoint) respectively.
* fix(vim-patch.sh): run nvim with -u NONE -n #16179Sean Dewar2021-10-30
| | | | | | | | | | Problem: Because of -u NORC, vim-patch.sh would hang on my machine due to one of my plugins (start package) waiting for prompt input. Solution: - Use -u NONE instead to disable all plugins. - Also use -n to disable swapfiles. These changes only apply to the --headless nvim instances used to process things.
* feat(lsp): default to botright for setting qflist (#16177)Michael Lingelbach2021-10-30
| | | | | | * Opens quickfix list spanning the entire nvim window in location handlers closes https://github.com/neovim/neovim/issues/12241
* fix(vim.mpack): rename pack/unpack => encode/decode #16175Justin M. Keyes2021-10-30
| | | | | | | | | | | | | | | | | | | | | | | Problem: 1. "unpack" has an unrelated meaning in Lua: https://www.lua.org/manual/5.1/manual.html#pdf-unpack 2. We already have msgpackparse()/msgpackdump() and json_encode()/json_decode(), so introducing another name for the same thing is entropy. Solution: - Rename vim.mpack.pack/unpack => vim.mpack.encode/decode Caveat: This is incongruent with the `Unpacker` and `Packer` functions. - It's probably too invasive to rename those. - They also aren't part of our documented interface. - This commit is "reversible" in the sense that we can always revert it and add `vim.mpack.encode/decode` as _aliases_ to `vim.mpack.pack/unpack`, at any time in the future, if we want stricter fidelity with upstream libmpack. Meanwhile, `vim.mpack.encode/decode` is currently the total _documented_ interface of `vim.mpack`, so this change serves the purpose of consistent naming in the Nvim stdlib.
* fix(build): remove amalg build target for LuaJIT (#16178)Christian Clason2021-10-30
| | | | fixup for #16041 (`amalg` build is recommended by LuaJIT for performance but this way of doing it breaks parallel build with `make -j`)
* refactor(diagnostic): make display handlers generic (#16137)Gregory Anders2021-10-29
| | | | | | | Rather than treating virtual_text, signs, and underline specially, introduce the concept of generic "handlers", of which those three are simply the defaults bundled with Nvim. Handlers are called in `vim.diagnostic.show()` and `vim.diagnostic.hide()` and are used to handle how diagnostics are displayed.
* refactor: uncrustify #16090dundargoc2021-10-29
|
* fix(eval): fix has('wsl') #16153erw72021-10-29
| | | | | | | | Problem: has('wsl') is decided at build-time. Solution: Check os_uname(). Fixes #12642, #16143
* Merge pull request #16154 from bfredl/neoscriptBjörn Linse2021-10-30
|\ | | | | refactor(api): break out Vim script functions to its own file
| * refactor(api): break out Vim script functions to its own fileBjörn Linse2021-10-29
| |
| * refactor(api): break out vim_to_object/object_to_vim to own fileBjörn Linse2021-10-29
| |
* | build(deps): bump luv to 1.42.0-1 (#16113)Christian Clason2021-10-29
| | | | | | | | * Use uv_handle_size/uv_req_size instead of sizeof * LuaJIT: add missing LJ_ENDIAN and LJ_NO_UNWIND checks for DASM [fixes building on aarch64]
* | build(deps): bump luajit to latest commit (#16041)Christian Clason2021-10-29
|/ | | | | bump LuaJIT to https://github.com/LuaJIT/LuaJIT/commit/b4b2dce9fc3ffaaaede39b36d06415311e2aa516 now requires `-funwind-tables` build flag, which conflicts with `-DLUA_USE_ASSERT`
* feat(lsp): track pending+cancel requests on client object #15949jdrouhard2021-10-29
|
* fix(eval): checking for a non-empty string is too strict (#15987)Fabian2021-10-28
| | | | | | Cherry-pick check_for_nonempty_string() from patch vim-8.2.2133 and apply it on the bases of https://github.com/neovim/neovim/pull/13489 https://github.com/vim/vim/commit/2a9d5d386bea8455b37c1accebc45683ec51d6fb
* vim-patch:8.2.3556: filler lines are incorrect for other window in diff mode ↵Jaehwang Jerry Jung2021-10-28
| | | | | | | | (#16164) Problem: Filler lines are incorrect for other window in diff mode after making a change. Solution: Copy filler lines from the current window. (closes vim/vim#8809) https://github.com/vim/vim/commit/841c225b9ef8c5bdf5e02968a0bd62521fff6ca8
* Merge pull request #16141 from dundargoc/ci/split-jobsJames McCoy2021-10-28
|\
| * ci: run functionaltest-lua on drafts as wellDundar Göc2021-10-28
|/
* test(vim_spec): fix MSVC_32 skip for nvim_parse_expression test (#16161)Sean Dewar2021-10-27
| | | | | | "works with &opt" is flaky; now it always fails after #15999 for some reason. This test was skipped in #10773 due to previous flakiness, but after the switch away from appveyor the check no longer works. Just skip for any CI running the MSVC_32 job.
* ci: add newly added api file extmark.c to gen-vimdoc (#16158)dundargoc2021-10-27
|
* Merge pull request #16125 from dundargoc/refactor/lua/split-executorBjörn Linse2021-10-26
|\ | | | | refactor: split lua/executor.c into two files
| * refactor: split executor.c into two filesDundar Göc2021-10-26
| |
* | feat(ci): add backport PR action (#14766)Michael Lingelbach2021-10-26
| | | | | | Trigger the backport action upon merge by marking a PR with the label `backport <branchname>` or after merge by applying the label and writing a comment containing `/backport`.
* | Merge pull request #16149 from zeertzjq/man-cleanJames McCoy2021-10-26
|\ \
| * | docs(manpage): update description of --cleanzeertzjq2021-10-26
| |/
* | Merge pull request #16147 from bfredl/neomarkBjörn Linse2021-10-26
|\ \ | |/ |/| refactor(api): move extmark API to its own file
| * refactor(api): move extmark API to its own fileBjörn Linse2021-10-25
|/
* Merge pull request #16124 from mjlbach/feat/bjorn-baitBjörn Linse2021-10-24
|\ | | | | feat: add vim.str_utf_pos
| * feat: add vim.str_utf_pos functionMichael Lingelbach2021-10-24
| | | | | | | | | | vim.str_utf_pos returns the codepoints for all utf-8 chars (only, currently) in a string
* | vim-patch:8.2.3547: opening the quickfix window triggers BufWinEnter twice ↵Yorick Peterse2021-10-23
| | | | | | | | | | | | | | | | (#16108) Problem: Opening the quickfix window triggers BufWinEnter twice. (Yorick Peterse) Solution: Only trigger BufWinEnter with "quickfix". (closes vim/vim#9022) https://github.com/vim/vim/commit/1d30fde3c989a962e0e1af4cbcf90e1ea483f1f4
* | vim-patch:partial 079ba76ae7a7 (#16126)Christian Clason2021-10-23
| | | | | | | | | | | | | | | | Update runtime files https://github.com/vim/vim/commit/079ba76ae7a7d0ef404cb9b41dff2663ff41f51b skip optwin.vim (needs 8.2.3520) skip doc/options.txt (needs 8.2.1535) skip doc/insert.txt (needs 8.2.3528)
* | Merge pull request #16128 from bfredl/vluapackBjörn Linse2021-10-23
|\ \ | | | | | | feat(lua): document support of packages with v:lua syntax
| * | feat(lua): document support of packages with v:lua syntaxBjörn Linse2021-10-23
| | | | | | | | | | | | this already worked in 0.5 but was not properly documented or tested
* | | vim-patch:8.2.3542: too many comments are old style (#16096)dundargoc2021-10-23
| | | | | | | | | | | | | | | Problem: Too many comments are old style. Solution: Change comments to // style. (closes vim/vim#9021) https://github.com/vim/vim/commit/c5935a859ee31d56a565878d7a231fc59b7ddc01
* | | vim-patch:8.2.0026: still some /* */ comments (#16088)dundargoc2021-10-23
| | | | | | | | | | | | | | | Problem: Still some /* */ comments. Solution: Convert to // comments. https://github.com/vim/vim/commit/85a2002adb0eda9a9309c2fab4a79edaa91fb834
* | | Merge pull request #16111 from dundargoc/vim-patch/commentsJan Edmund Lazo2021-10-23
|\ \ \ | |/ / |/| | vim-patch:8.1.2368,8.1.2378,8.1.2379,8.1.2380,8.1.2387,8.1.2388,8.1.2392,8.1.2394,8.1.2395,8.1.2396
| * | vim-patch:8.1.2396: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/e38eab22c1fb950127f0307a9904de6d4561dc70
| * | vim-patch:8.1.2395: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/0d6f5d9740dbad1b0207f3ab257de806169dd905
| * | vim-patch:8.1.2394: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/63d9e730f726341bf41ee4f4b829253cb9879110
| * | vim-patch:8.1.2392: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/6e0ce171e19d0118ecd7c2b16e2a1bd50aa76013
| * | vim-patch:8.1.2388: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/4ba37b5833de99db9e9afe8928b31c864182405c
| * | vim-patch:8.1.2387: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/2ab2e8608f9b2c85432715bb9a7f226fdbf8cd35
| * | vim-patch:8.1.2380: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/306139005c31ea7e6f892dd119beba3c94dcb982
| * | vim-patch:8.1.2379: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/217e1b8359447f5550dcb0d1ee43380a90c253c5
| * | vim-patch:8.1.2378: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/5d18efecfd6c45d69f55268948a22cd0465bb955
| * | vim-patch:8.1.2368: using old C style commentsDundar Göc2021-10-21
| | | | | | | | | | | | | | | | | | Problem: Using old C style comments. Solution: Use // comments where appropriate. https://github.com/vim/vim/commit/c667da5185ce5dce914d2006d62da2be0cedb384
* | | Merge pull request #16029 from bfredl/multilineBjörn Linse2021-10-23
|\ \ \ | |_|/ |/| | feat(decorations): support more than one virt_lines block
| * | feat(decorations): support more than one virt_lines blockBjörn Linse2021-10-23
| | |
| * | refactor(decorations): mark decorations directly on the marktreeBjörn Linse2021-10-23
| |/ | | | | | | | | | | | | | | | | | | | | | | | | This allows to more quickly skip though regions which has non-decorative marks when redrawing. This might seem like a gratuitous micro-optimization in isolation. But! Soon decorations are gonna crop into other hot inner-loop paths, including the plines.c code for calculating the horizontal and vertical space of text. Then we want to quickly skip over regions with "only" overlaying decorations (which do not affect text size)
* | fix(lsp): cleanup progress messages for the correct client (#16110)Folke Lemaitre2021-10-21
| |
generated by cgit (git 2.34.1) at 2025-08-09 14:26:36 +0000