rneovim.git/runtime/lua/vim/_defaults.lua, branch rahm

docs: misc

2025-01-30T12:46:06+00:00

Co-authored-by: Dustin S. 
Co-authored-by: Ferenc Fejes 
Co-authored-by: Maria José Solano 
Co-authored-by: Yochem van Rosmalen 
Co-authored-by: brianhuster 
Co-authored-by: zeertzjq

refactor: use nvim.foo.bar format for autocommand groups

2025-01-15T05:25:25+00:00

feat(api): deprecate nvim_out/err_write(ln)

2025-01-09T12:35:42+00:00

feat(jobs): jobstart(…,{term=true}), deprecate termopen() #31343

2024-12-19T15:07:04+00:00

Problem:
`termopen` has long been a superficial wrapper around `jobstart`, and
has no real purpose. Also, `vim.system` and `nvim_open_term` presumably
will replace all features of `jobstart` and `termopen`, so centralizing
the logic will help with that.

Solution:
- Introduce `eval/deprecated.c`, where all deprecated eval funcs will live.
- Introduce "term" flag of `jobstart`.
- Deprecate `termopen`.

feat(defaults): disable 'foldcolumn' in terminal buffers (#31480)

2024-12-06T16:19:24+00:00

fix(defaults): don't replace keycodes in Visual search mappings (#31460)

2024-12-05T11:03:58+00:00

Also remove "silent" to be more consistent with Normal mode search.

defaults: disable 'number', 'relativenumber', and 'signcolumn' in terminal buffers (#31443)

2024-12-04T14:40:01+00:00

feat(tui): update 'background' on theme change events (#31350)

2024-11-26T20:22:01+00:00

Enabling private DEC mode 2031 tells the terminal to notify Nvim
whenever the OS theme changes (i.e. light mode to dark mode or vice
versa) or the terminal emulator's palette changes. When we receive one
of these notifications we query the terminal color's background color
again to see if it has changed and update the value of 'background' if
it has.

We only do this though if the user has not explicitly set the value of
'bg' themselves. The help text is updated slightly to hint to users that
they probably shouldn't set this value: on modern terminal emulators
Nvim is able to completely determine this automatically.

fix(defaults): omit empty line from unimpaired mapping messages (#31347)

2024-11-25T22:33:11+00:00

Problem:
The default unimpaired mappings display an empty line after the
command's output. This results (with default configuration) in the
`Press ENTER or type command to continue` prompt to be displayed, like
so:
```
(2 of 16): item2

Press ENTER or type command to continue
```

Solution:
The cause is that we're checking the second return value from
`pcall(vim.api.nvim_cmd, opts, {})` to determine whether the call was
successful. `nvim_cmd` returns an empty string on success, so this value
is an empty string in the successful path which we then display.

The fix is simple: check the first return value instead which is the
"status code" of the call.

feat(defaults): dot-repeat [ #31186

2024-11-17T21:31:24+00:00

Problem: `[` and `]` do not support repetition.

Solution: use `operatorfunc` and `g@l` to make these mappings dot
repeatable.