- Fix the problem that chanclose() does not work for channel created by
nvim_open_term().
- Fix the problem that the loopback channel is not released.
- Fix the error message when sending raw data to the loopback channel.
Problem: Using freed memory when defining a user command from a user
command.
Solution: Do not use the command pointer after executing the command.
(closesvim/vim#9318)
205f29c3e9
Problem: The regexp.c file is too big.
Solution: Move the backtracking engine to a separate file. (Yegappan
Lakshmanan, closesvim/vim#4905)
6d7d7cf750
vim-patch:8.1.2010: new file uses old style comments
Problem: New file uses old style comments.
Solution: Change to new style comments. (Yegappan Lakshmanan, closesvim/vim#4910)
9490b9a61c
Problem: Use register one too often and not properly tested.
Solution: Do not always use register one when specifying a register.
(closesvim/vim#4085) Add more tests.
9d7fdd403a
Problem: Using sprintf() instead of semsg().
Solution: Use semsg(). Fix bug with E888. (Ozaki Kiichi, closesvim/vim#3801)
1be45b2ea7
vim-patch:8.1.0136: Lua tests don't cover new features
Problem: Lua tests don't cover new features.
Solution: Add more tests. (Dominique Pelle, closesvim/vim#3130)
2f362bf7f9
vim-patch:8.1.0139: Lua tests fail on some platforms
Problem: Lua tests fail on some platforms.
Solution: Accept a hex number with and without "0x". (Ken Takata,
closesvim/vim#3137)
a8a60d0c6b
vim-patch:8.1.0164: luaeval('vim.buffer().name') returns an error
Problem: luaeval('vim.buffer().name') returns an error.
Solution: Return an empty string. (Dominique Pelle, closesvim/vim#3167)
fe08df452a
vim-patch:8.1.0300: the old window title might be freed twice
Problem: The old window title might be freed twice. (Dominique Pelle)
Solution: Do not free "oldtitle" in a signal handler but set a flag to have
it freed later.
d8f0cef2bd
vim-patch:8.1.0672: the Lua interface doesn't know about v:null
Problem: The Lua interface doesn't know about v:null.
Solution: Add Lua support for v:null. (Uji, closesvim/vim#3744)
9067cd6cdf
Problem: Cannot execute a register containing line continuation.
Solution: Concatenate lines where needed. (Yegappan Lakshmanan,
closesvim/vim#6272)
856c1110c1
According to #2542 the "Future:" part was removed intentionally.
Use size_t in more places to reduce type casts.
Don't add sign extmarks to state->active. Instead when drawing signs,
perform a full line scan for sign marks. This allows decor_redraw_line
to be moved back inside the `!number_only` block in screen.c, which
prevents decor scans when redrawing the number column when
'relativenumber' is set.
Fixes: #17638
* feat(api): `group` can be either string or int
This affects the following API functions:
- `vim.api.nvim_create_autocmd`
- `vim.api.nvim_get_autocmds`
- `vim.api.nvim_do_autocmd`
closes#17552
* refactor: add two maps for fast lookups
* fix: delete augroup info from id->name map
When in "stupid_legacy_mode", the value in name->id map would be updated
to `AUGROUP_DELETED`, but the entry would still remain in id->name. This
would create a problem in `augroup_name` function which would return the
name of the augroup instead of `--DELETED--`.
The id->name map is only used for fast loopup in `augroup_name` function
so there's no point in keeping the entry of deleted augroup in it.
Co-authored-by: TJ DeVries <devries.timothyj@gmail.com>
