rneovim.git/runtime/doc, branch usermarks

docs(vim.fs): normalize Windows example was incorrect (#21966)

2023-01-24T22:45:30+00:00

doc(lsp): format arguments to start_client() (#21980)

2023-01-24T18:04:15+00:00

docs(lsp): format arguments to start_client()

feat(highlight): define the concept of altfont as a (c)term rendering attribute

2023-01-24T11:27:50+00:00

feat!: make iconv a non-optional dep

2023-01-23T16:33:45+00:00

build: make generated source files reproducible #21586

2023-01-23T09:26:46+00:00

Problem:
Build is not reproducible, because generated source files (.c/.h/) are not
deterministic, mostly because Lua pairs() is unordered by design (for security).

https://github.com/LuaJIT/LuaJIT/issues/626#issuecomment-707005671
https://www.lua.org/manual/5.1/manual.html#pdf-next
> The order in which the indices are enumerated is not specified [...]
>
>> The hardening of the VM deliberately randomizes string hashes. This in
>> turn randomizes the iteration order of tables with string keys.

Solution:
- Update the code generation scripts to be deterministic.
    - That is only a partial solution: the exported function
      (funcs_metadata.generated.h) and ui event
      (ui_events_metadata.generated.h) metadata have some mpack'ed
      tables, which are not serialized deterministically.
    - As a workaround, introduce `PRG_GEN_LUA` cmake setting, so you can
      inject a modified build of luajit (with LUAJIT_SECURITY_PRN=0)
      that preserves table order.
    - Longer-term we should change the mpack'ed data structure so it no
      longer uses tables keyed by strings.

Closes #20124

Co-Authored-By: dundargoc 
Co-Authored-By: Arnout Engelen

feat(lsp): add triggerKind option for vim.lsp.buf.code_action (#21905)

2023-01-21T07:22:34+00:00

vim-patch:9.0.1223: cannot use setcellwidths() below 0x100 (#21929)

2023-01-21T00:44:14+00:00

Problem:    Cannot use setcellwidths() below 0x100.
Solution:   Also accept characters between 0x80 and 0x100. (Ken Takata,
            closes vim/vim#11834)

https://github.com/vim/vim/commit/7193323b7796c05573f3aa89d422e848feb3a8dc

Co-authored-by: K.Takata

docs: docs: use codeblocks in runtime/doc/options.txt (#21919)

2023-01-20T16:29:15+00:00

ensure correct parsing with tree-sitter

Co-authored-by: zeertzjq

perf(statuscolumn): only fill click defs array once per redraw (#21884)

2023-01-19T23:47:02+00:00

Problem:    'statuscolumn' click definitions are cleared, evaluated,
            allocated and filled each redraw for every row in a window.
            This despite the fact that we only store a single click
            definition array for the entire column as opposed to one
            for each row.
Solution:   Only fill the 'statuscolumn' click definition array once per
            window per redraw.

Resolve https://github.com/neovim/neovim/issues/21767.

vim-patch:8.2.1698: cannot lock a variable in legacy Vim script like in Vim9 (#21883)

2023-01-19T00:03:13+00:00

Problem:    Cannot lock a variable in legacy Vim script like in Vim9.
Solution:   Make ":lockvar 0" work.

https://github.com/vim/vim/commit/a187c43cfe8863d48b2159d695fedcb71f8525c1

Co-authored-by: Bram Moolenaar