rneovim.git/runtime/lua/vim/_meta/api.lua, branch userregs_2 Neovim fork with Rahm's personal hacks. docs: lsp config/commands #33122 2025-03-30T20:29:36+00:00 Justin M. Keyes justinkz@gmail.com 2025-03-30T20:29:36+00:00 b41e066aa124b5feb428877c7a35776ce4d3035c fix #33075 
fix #33075
 docs: faq, lua packages #33183 2025-03-30T15:18:23+00:00 Phạm Bình An 111893501+brianhuster@users.noreply.github.com 2025-03-30T15:18:23+00:00 87b4469adcf2de5f792ea0d19afd002e9cb96016 Problem: - `health#check()` seems to have been removed for a while, but `:h faq` still refers to it. - `news-0.11.txt` doesn't mention #33044 
Problem:
- `health#check()` seems to have been removed for a while, but `:h faq`
  still refers to it.
- `news-0.11.txt` doesn't mention #33044
 feat(float): add winborder option (#31074) 2025-03-18T21:05:35+00:00 glepnir glephunter@gmail.com 2025-03-18T21:05:35+00:00 62d9fab9af21323e42828748e6761c02020a7aa5 Problem: There is currently no global option to define the default border style for floating windows. This leads to repetitive code when developers need consistent styling across multiple floating windows. Solution: Introduce a global option winborder to specify the default border style for floating windows. When a floating window is created without explicitly specifying a border style, the value of the winborder option will be used. This simplifies configuration and ensures consistency in floating window appearance. Co-authored-by: Gregory Anders <greg@gpanders.com> 
Problem:
There is currently no global option to define the default border style for floating windows. This leads to repetitive code when developers need consistent styling across multiple floating windows.

Solution:
Introduce a global option winborder to specify the default border style for floating windows. When a floating window is created without explicitly specifying a border style, the value of the winborder option will be used. This simplifies configuration and ensures consistency in floating window appearance.

Co-authored-by: Gregory Anders <greg@gpanders.com>
 docs: misc #32959 2025-03-18T13:18:37+00:00 Justin M. Keyes justinkz@gmail.com 2025-03-18T13:18:37+00:00 7333c39e6cc78786289d88c65fbe10e4ce78992b 






docs: misc
2025-03-17T11:31:53+00:00

Justin M. Keyes
justinkz@gmail.com

2025-03-09T22:56:22+00:00

f96606371c13fd10280d737a4e3e2ae9149c2067












docs(api): rename "handle" => "id"
2025-03-17T11:06:38+00:00

Justin M. Keyes
justinkz@gmail.com

2025-03-16T13:13:02+00:00

041a939eeb21dd8a62c479f12cc9334d3d30a832












docs: misc
2025-03-15T14:00:44+00:00

dundargoc
gocdundar@gmail.com

2025-02-20T10:52:03+00:00

026cfa28d0dccb7f1832d6fcca378518a4082fdb

Co-authored-by: Au. <acehinnnqru@gmail.com>
Co-authored-by: Daniel Rainer <daniel.rainer@localhost>
Co-authored-by: Evgeni Chasnovski <evgeni.chasnovski@gmail.com>
Co-authored-by: Lewis Russell <lewis6991@gmail.com>
Co-authored-by: Luuk van Baal <luukvbaal@gmail.com>
Co-authored-by: Pierre Barbin <pierre@heitzsystem.com>
Co-authored-by: Riley Bruins <ribru17@hotmail.com>
Co-authored-by: Yinzuo Jiang <jiangyinzuo@foxmail.com>
Co-authored-by: phanium <91544758+phanen@users.noreply.github.com>
Co-authored-by: zeertzjq <zeertzjq@outlook.com>





Co-authored-by: Au. <acehinnnqru@gmail.com>
Co-authored-by: Daniel Rainer <daniel.rainer@localhost>
Co-authored-by: Evgeni Chasnovski <evgeni.chasnovski@gmail.com>
Co-authored-by: Lewis Russell <lewis6991@gmail.com>
Co-authored-by: Luuk van Baal <luukvbaal@gmail.com>
Co-authored-by: Pierre Barbin <pierre@heitzsystem.com>
Co-authored-by: Riley Bruins <ribru17@hotmail.com>
Co-authored-by: Yinzuo Jiang <jiangyinzuo@foxmail.com>
Co-authored-by: phanium <91544758+phanen@users.noreply.github.com>
Co-authored-by: zeertzjq <zeertzjq@outlook.com>







fix(types): do not mark unstable API as private
2025-03-08T00:08:03+00:00

Lewis Russell
lewis6991@gmail.com

2025-03-07T21:04:50+00:00

b813075b8a55cfb584e442943f04af5d1ce1dcba

These functions are allowed to be used downstream, they are just not API
stable.





These functions are allowed to be used downstream, they are just not API
stable.







docs: misc #31996
2025-03-02T22:27:52+00:00

Justin M. Keyes
justinkz@gmail.com

2025-03-02T22:27:52+00:00

c4a0c1d3b02761626ffced32fe74b0df5b665a5f












doc: clarify window-id, tab-id, nvim_set_current_x #32528
2025-02-27T10:05:00+00:00

David Briscoe
43559+idbrii@users.noreply.github.com

2025-02-27T10:05:00+00:00

6a9555c0faf3fbfc8001244ae2a19da4e92babd7

Problem:
Descriptions are somewhat vague. nvim_set_current_line modifies contents
but nvim_set_current_buf does not, etc.

Solution:
- Make it clear that these functions accept or return a winid/tabid by
  linking to that concept in help.
- Only these few files use the term "handles", so replace them with the
  more conventional terminology.
- Add a new help section for tab-ID. This concept is unique to neovim
  because vim exposes tabnr, but not tab handles. This section is
  modelled after `:h winid`.




Problem:
Descriptions are somewhat vague. nvim_set_current_line modifies contents
but nvim_set_current_buf does not, etc.

Solution:
- Make it clear that these functions accept or return a winid/tabid by
  linking to that concept in help.
- Only these few files use the term "handles", so replace them with the
  more conventional terminology.
- Add a new help section for tab-ID. This concept is unique to neovim
  because vim exposes tabnr, but not tab handles. This section is
  modelled after `:h winid`.