diff options
| author | zeertzjq <zeertzjq@outlook.com> | 2026-04-10 08:34:05 +0800 |
|---|---|---|
| committer | zeertzjq <zeertzjq@outlook.com> | 2026-04-10 12:30:31 +0800 |
| commit | dc3b49d5a1327a48a23b5b29101fe0adbda466b4 (patch) | |
| tree | 5ed8a17fa4716060d69a1e56703e6ffb0734315c /scripts/lintcommit.lua | |
| parent | 5c8a93001c37c79aa381c7d83a25aac940b4c2ab (diff) | |
| download | rneovim-dc3b49d5a1327a48a23b5b29101fe0adbda466b4.tar.gz rneovim-dc3b49d5a1327a48a23b5b29101fe0adbda466b4.tar.bz2 rneovim-dc3b49d5a1327a48a23b5b29101fe0adbda466b4.zip | |
vim-patch:9.2.0325: runtime(tar): bug in zstd handling
Problem: patch 9.2.0325: runtime(tar): bug in zstd handling
Solution: use correct --zstd argument, separated from other arguments,
rework testing framework (Aaron Burrow).
The tar.vim plugin allows vim to read and manipulate zstd archives,
but it had a bug that caused extraction attempts to fail.
Specifically, if the archive has a .tar.zst or .tzst extension, then
the code was generating invalid extraction commands that looked like
this:
tar --zstdpxf foo.tar.zst foo
When they should be like this:
tar --zstd -pxf foo.tar.zst foo
This patch changes the flag manipulation logic so that --zstd isn't
glued to pxf.
The labor for this change was divided between ChatGPT 5.4 and me.
ChatGPT 5.4 identified the issue (from a code scan?), and I wrote
the patch and tested vim.
related: vim/vim#19930
https://github.com/vim/vim/commit/00285c035aa7d92971bc50b7b124e1408dda53ad
Note: tests need the next patch to pass in Nvim.
Co-authored-by: Aaron Burrow <burrows@fastmail.com>
Diffstat (limited to 'scripts/lintcommit.lua')
0 files changed, 0 insertions, 0 deletions