aboutsummaryrefslogtreecommitdiff
path: root/src
Commit message (Collapse)AuthorAge
...
* | | refactor: saner options for uncrustify #16196dundargoc2021-10-31
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * refactor: general good option changes sp_deref = remove sp_not = remove sp_inv = remove sp_inside_paren_cast = remove mod_remove_duplicate_include = true sp_after_semi = add sp_after_semi_for = force sp_sizeof_paren = remove nl_return_expr = remove nl_else_brace = remove nl_else_if = remove * refactor: mod_remove_extra_semicolon = true * refactor: nl_max = 3 * refactor: sp_bool = force * refactor: sp_compare = force * refactor: sp_inside_paren = remove * refactor: sp_paren_paren = remove * refactor: sp_inside_sparen = remove * refactor: sp_before_sparen = force * refactor: sp_sign = remove * refactor: sp_addr = remove * refactor: sp_member = remove * refactor: nl_struct_brace = remove * refactor: nl_before_if_closing_paren = remove * refactor: nl_fdef_brace = force * refactor: sp_paren_comma = force * refactor: mod_full_brace_do = add
* | | fix(runtime): fix missing packpath entriesBjörn Linse2021-10-31
| | |
* | | 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.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.
* | | 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
* | | 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
| | |
* | | 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 #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
| | |
* | | 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: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)
* / / vim-patch:8.2.3550: completion() does not work properly (#16112)Christian Clason2021-10-21
|/ / | | | | | | | | | | | | | | | | | | * vim-patch:8.2.3550: completion() does not work properly Problem: completion() does not work properly. Solution: Set xp_line and add WILD_HOME_REPLACE. (Shougo Matsushita, closes vim/vim#9016) https://github.com/vim/vim/commit/ae38a9db7770b38889fbf06908cc69d42b463a73 Co-authored-by: Sean Dewar <seandewar@users.noreply.github.com>
* | vim-patch:8.1.2243: typos in comments (#16104)dundargoc2021-10-20
| | | | | | | | | | | | Problem: Typos in comments. Solution: Fix the typos. (Dominique Pelle, closes vim/vim#5160) Also adjust formatting a bit. https://github.com/vim/vim/commit/32aa10203bd0b4b270def03311a4599f9ffdecc4
* | Merge pull request #16086 from bfredl/termpipe_inputBjörn Linse2021-10-20
|\ \ | | | | | | feat(nvim_open_term): support input callback in lua
| * | feat(nvim_open_term): support input callback in luaBjörn Linse2021-10-20
| | |
* | | build: update cmake min version to 3.10 #16065Jakub Łuczyński2021-10-19
| | | | | | | | | | | | | | | | | | * build(cmake): update cmake min version to 3.10 * ci: test cmake minimum required version * build(cmake): remove some legacy includes * Since version 3.5 cmake_parse_arguments is implemented natively.
* | | Merge pull request #15767 from lewis6991/lua_var_indexBjörn Linse2021-10-19
|\ \ \ | | | | | | | | feat(lua): allow passing handles to `vim.b/w/t`
| * | | feat(lua): allow passing handles to vim.b/w/tLewis Russell2021-10-19
| | |/ | |/| | | | | | | | | | | | | vim.bo can target a specific buffer by indexing with a number, e.g: `vim.bo[2].filetype` can get/set the filetype for buffer 2. This change replicates that behaviour for the variable namespace.
* / | fix(gen_vimdoc.py): spacing around inline elements #16092Gregory Anders2021-10-19
|/ / | | | | | | | | The spacing fix drew attention to a couple of places that were using incorrect formatting such as the key listing for `nvim_open_win`, so those were fixed too.
* | vim-patch:8.2.3537: wrong mode() during 'operatorfunc' #16087zeertzjq2021-10-19
| | | | | | | | | | Problem: mode() does not return the right value in 'operatorfunc'. Solution: Reset finish_op while calling 'operatorfunc'. https://github.com/vim/vim/commit/75c30e96cf280a8cc01ac01c41a9252db3e503cc
* | fix(api/nvim_eval_statusline): allow maxwidth=0 #16080Famiu Haque2021-10-19
| | | | | | | | Allows disabling statusline truncation by allowing maxwidth to be set to 0 in `nvim_eval_statusline`.
* | refactor: remove space after starDundar Göc2021-10-19
| |
* | refactor: make commas trail in enumsDundar Göc2021-10-19
| |
* | refactor: enable formatting for files under libDundar Göc2021-10-19
|/
* feat(api): evaluate statusline string #16020Famiu Haque2021-10-18
| | | | | | Adds API function `nvim_eval_statusline` to allow evaluating a statusline string and obtaining information regarding it. Closes https://github.com/neovim/neovim/issues/15849
* refactor: convert to doxygen-style comments #16013dundargoc2021-10-17
|
* fix(PVS/V1028): prevent possible overflow #16023dundargoc2021-10-17
| | | | | | Full warning: "Possible overflow. Consider casting operands, not the result." https://pvs-studio.com/en/docs/warnings/v1028/
* Merge pull request #15999 from famiu/fix/build/export-windows-symbolsBjörn Linse2021-10-17
|\ | | | | fix(build): export symbols on Windows
| * fix(build): export symbols on WindowsFamiu Haque2021-10-17
| | | | | | | | | | | | Closes https://github.com/neovim/neovim/issues/15063 Allows using Neovim core functions using LuaJIT FFI on Windows.
generated by cgit (git 2.34.1) at 2025-06-26 07:02:17 +0000