| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
| |
fixes: vim/vim#5630
fixes: vim/vim#9807
fixes: vim/vim#14623
closes: vim/vim#15996
https://github.com/vim/vim/commit/64a536d4fa17ec176f574a01543e483a163622eb
Co-authored-by: Tom Benham <tom.benham13@gmail.com>
|
|
|
|
|
|
| |
https://github.com/vim/vim/commit/a063b22b3bbc1c7ad9d985b14d6e3c5b7c6e3eca
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem:
There are three different ways of marking an option as hidden, `enable_if
= false`, `hidden = true` and `immutable = true`. These also have different
behaviors. Options hidden with `enable_if = false` can't have their value
fetched using Vim script or the API, but options hidden with `hidden = true` or
`immutable = true` can. On the other hand, options with `hidden = true` do not
error when trying to set their value, but options with `immutable = true` do.
Solution:
Remove `enable_if = false`, remove the `hidden` property for options, and use
`immutable = true` to mark an option as hidden instead. Also make hidden option
variable pointers always point to the default value, which allows fetching the
value of every hidden option using Vim script and the API. This does also mean
that trying to set a hidden option will now give an error instead of just being
ignored.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
typst.vim
2 commits included from the upstream:
- https://github.com/kaarmu/typst.vim/commit/2a4a0e0662f2f882403af7200b4249c564a621ab
- https://github.com/kaarmu/typst.vim/commit/50e89f481102d5c9ef6990b9f8086c0c7d64bff6
https://github.com/vim/vim/commit/d181bafd0bb53f3caaf15a95a329a31d8208206b
Co-authored-by: Yinzuo Jiang <jiangyinzuo@foxmail.com>
|
|
|
|
|
|
|
|
|
|
| |
which contains `~` character
closes: vim/vim#15964
https://github.com/vim/vim/commit/4d618006ecfd2557806d8af488f70b3e46878d70
Co-authored-by: Tom Benham <tom.benham13@gmail.com>
|
|
|
|
|
|
|
|
|
|
| |
fixes: vim/vim#15959
closes: vim/vim#15962
https://github.com/vim/vim/commit/8b0fa7a565d8aec306e5755307d182fa7d81e65f
Co-authored-by: Christian Brabandt <cb@256bit.org>
Co-authored-by: Aliaksei Budavei <0x000c70@gmail.com>
|
|
|
|
|
|
|
|
|
| |
related: vim/vim#13687
https://github.com/vim/vim/commit/9f32069b8c4f74aa6af47e2f0ec07f2745feac57
Co-authored-by: Christian Brabandt <cb@256bit.org>
Co-authored-by: K.Takata <kentkt@csc.jp>
|
|
|
|
|
|
|
|
|
|
|
| |
fixes: vim/vim#15961
while at it, remove the Decho comments in the s:NetrwOptionsRestore()
function
https://github.com/vim/vim/commit/aa2ce6f58005bc3b81be2bf42f84ffd01ce22d57
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
It did not work very well, at least on Debian 12, and I am not sure Git
Bash and WSL, for example, were taken care of as maintenance stalled.
The whole logic was somewhat convoluted with some parts repeatedly invoking
failed commands.
The file handling was outdated, for example, nowadays Netscape is rarely
used, and also opinionated, for example mainly Microsoft Paint and Gimp for
Image files.
Instead, let's use (xdg-)open and similar commands on other systems
which respects the user's preferences.
closes: vim/vim#15721
https://github.com/vim/vim/commit/3d7e567ea7392e43a90a6ffb3cd49b71a7b59d1a
Co-authored-by: Konfekt <Konfekt@users.noreply.github.com>
Co-authored-by: Luca Saccarola <96259932+saccarosium@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
| |
netrwFileHandlers#Invoke()
closes: vim/vim#15895
https://github.com/vim/vim/commit/a7d456191de0c9092151e5c64f1a3b5a6714509b
Co-authored-by: Luca Saccarola <github.e41mv@aleeas.com>
Co-authored-by: Konfekt <Konfekt@users.noreply.github.com>
|
|
|
|
|
|
|
|
| |
closes: vim/vim#15897
https://github.com/vim/vim/commit/421ed14b8a0f50e0d2d9247dda49feb69352bd0d
Co-authored-by: Luca Saccarola <github.e41mv@aleeas.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: Some runtime files no longer spark joy.
Solution: Kondo the place up.
Still sparks _some_ joy (moved to new `runtime/scripts` folder):
* `macros/less.*`
* `mswin.vim`
* `tools/emoji_list.lua`
No longer sparks joy (removed):
* `macmap.vim` (gvimrc file; not useful in Nvim)
* `tools/check_colors.vim` (no longer useful with new default colorscheme and treesitter)
* `macros/editexisting.vim` (throws error on current Nvim)
* `macros/justify.vim` (obsolete shim for `packadd! justify`)
* `macros/matchit.vim` (same)
* `macros/shellmenu.vim` (same)
* `macros/swapmous.vim` (same)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Javadoc comments
Complement "g:java_ignore_javadoc" with "g:java_ignore_html"
and "g:java_ignore_markdown" to allow selectively disabling
the recognition of HTML and CommonMark respectively.
(Note that this is not a preview feature.)
======================== LIMITATION ========================
According to the syntactical details of JEP 467:
> Any leading whitespace and the three initial / characters
> are removed from each line.
>
> The lines are shifted left, by removing leading whitespace
> characters, until the non-blank line with the least
> leading whitespace has no remaining leading whitespace.
>
> Additional leading whitespace and any trailing whitespace
> in each line is preserved, because it may be significant.
the following example:
------------------------------------------------------------
/// A summary sentence.
/// A list:
/// - Item A.
/// - Item B.
///
/// Some code span, starting here `
/// 1 + 2 ` and ending at the previous \`.
------------------------------------------------------------
should be interpreted as if it were written thus:
------------------------------------------------------------
///A summary sentence.
/// A list:
/// - Item A.
/// - Item B.
///
/// Some code span, starting here `
/// 1 + 2 ` and ending at the previous \`.
------------------------------------------------------------
Since automatic line rewriting will not be pursued, parts of
such comments having significant whitespace may be ‘wrongly’
highlighted. For convenience, a &fex function is defined to
‘correct’ it: g:javaformat#RemoveCommonMarkdownWhitespace()
(:help ft-java-plugin).
References:
https://openjdk.org/jeps/467
https://spec.commonmark.org/0.31.2
closes: vim/vim#15740
https://github.com/vim/vim/commit/85f054aa3f0fb9530712d0897e3c8ba29946fad4
Co-authored-by: Aliaksei Budavei <0x000c70@gmail.com>
Co-authored-by: Tim Pope <code@tpope.net>
|
|
|
|
|
|
|
|
|
| |
fixes: vim/vim#15717
closes: vim/vim#15718
https://github.com/vim/vim/commit/be551dacb87a0542afd8b5c17b89e6749f2dc355
Co-authored-by: Peter Aronoff <peter@aronoff.org>
|
|
|
|
|
|
|
|
|
| |
not found (#30451)
closes: vim/vim#15705
https://github.com/vim/vim/commit/e6b01cfe01a2722ec55a011ae04c4c404e88f924
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
|
|
|
| |
Fixes E872 too many '(' in highlight pattern for `mf` selection
fixup for vim/vim#15551
closes: vim/vim#15700
https://github.com/vim/vim/commit/c18a9d5835456e0e47e943b673d631caaebdbea3
Co-authored-by: yasuda <yasuda@kyoto-sr.co.jp>
|
|
|
|
|
|
|
|
| |
fixes: vim/vim#15680
https://github.com/vim/vim/commit/0f5effbd1fb58128be677aa577d3d0ab2fc9527a
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
| |
Terraform (#30266)
closes: vim/vim#15618
https://github.com/vim/vim/commit/150b5078ac886519083576124090489c3a21bd3b
|
| |
|
|
|
|
|
|
|
|
| |
closes: vim/vim#15550
https://github.com/vim/vim/commit/c75dad017726ae78d6d2a68d1d6cfa12e7bd29f3
Co-authored-by: yasuda <yasuda@kyoto-sr.co.jp>
|
|
|
|
|
|
|
|
| |
closes: vim/vim#15551
https://github.com/vim/vim/commit/38cfa2b6623c64e748be17739799da36ca2d76bf
Co-authored-by: yasuda <yasuda@kyoto-sr.co.jp>
|
|
|
|
|
|
|
|
|
| |
(#30115)
related: vim/vim#15519
https://github.com/vim/vim/commit/bc29ea62861052b35781031173a67d7d577be068
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: zip-plugin has problems with special characters
(user202729)
Solution: escape '*?[\' on Unix and handle those chars
a bit differently on MS-Windows, add a test, check
before overwriting files
runtime(zip): small fixes for zip plugin
This does the following:
- verify the unzip plugin is executable when loading the autoload plugin
- handle extracting file names with '[*?\' in its name correctly by
escaping those characters for the unzip command (and handle those
characters a bit differently on MS-Windows, since the quoting is different)
- verify, that the extract plugin is not overwriting a file (could cause
a hang, because unzip asking for confirmation)
- add a test zip file which contains those special file names
fixes: vim/vim#15505
closes: vim/vim#15519
https://github.com/vim/vim/commit/7790ea0c680a9f951a86066e5940ec16b2333c9a
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Otherwise, if the executable to be verified does not exist,
this would cause a false-positive in the 'IsSafeExecutable()' check,
because 'exepath(executable)' returns an empty string and
'fnamemodify('', ':p:h')' returns the current directory and as a result
the 'IsSafeExecutable()' returns false (for the wrong reason).
https://github.com/vim/vim/commit/8e25d91cb7bb4dc171cb4e95b1bb79a39400a13a
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
| |
closes: vim/vim#15501
https://github.com/vim/vim/commit/1fbccc1e9694e5e6162dff112b49a093eac770ee
Co-authored-by: Damien <141588647+xrandomname@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: g:netrw_use_errorwindow=2 does not work
without +balloon_eval.
Solution: Check for popup_atcursor().
related: vim/vim#15501
https://github.com/vim/vim/commit/b4d11644254ec6e29aed93a9fdcde2160163aefd
Co-authored-by: Damien <141588647+xrandomname@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
| |
Move variables declaration
related: vim/vim#15501
https://github.com/vim/vim/commit/7c754110ff8e0d666d422f1644bc356c8fee7392
Co-authored-by: Damien <141588647+xrandomname@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
| |
Problem: RestoreOpts() plugin called too often
Solution: use :defer to have the RestoreOpts() function
called when the function returns automatically
https://github.com/vim/vim/commit/afea6b946827e964271eb19579946a7f88d2f329
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
|
|
| |
Problem: the zip plugin duplicates a lot of code for displaying
warnings/errors
Solution: refactor common code into a generic Mess() function
https://github.com/vim/vim/commit/8d52926857ec7f08a9bee8f96470748cecf58002
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
|
| |
Problem: the zip plugin version is still v33
Solution: increment the version to v34
https://github.com/vim/vim/commit/a336d8f21e4cce877e23d47db238801a5a406992
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: zip plugin has no way to set/restore option values
Solution: Add the SetSaneOpts() and RestoreOpts() functions,
so options that cause issues are set to sane values
and restored back to their initial values later on.
(this affects the 'shellslash' option on windows, which also
changes how the shellescape() function works)
https://github.com/vim/vim/commit/19636be55e023cb726389107e9e7d62049b6fd58
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
|
|
| |
Problem: zip plugin tests for fnameescape() function
Solution: Remove the check, fnameescape() has been available since
7.1.299, it should nowadays always be available
https://github.com/vim/vim/commit/33836d38b82aa926a2a2b3f945a0139f373f7e56
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
|
|
| |
Problem: zip plugin uses :echo which does not store messages
Solution: use :echomsg instead of :echo so that messages are stored in
the message history
https://github.com/vim/vim/commit/120c0dd815fa3b44df0fa477f7f3313e4a69c652
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
|
| |
Problem: zip plugin contains a lot of comments from the decho plugin
Solution: Clean up and remove un-used comments
https://github.com/vim/vim/commit/a63f66e953d811bb6d044e92fe338e533ad94ff5
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: Cannot browse zipfiles with the unzip program found
on FreeBSD.
Solution: Adjust command arguments.
Unzip found on FreeBSD complain about missing argument with the
zipinfo modifier '-Z -1'. Joining arguments seems to work
for both implementations.
Also change `:sil!` to `:sil` so that error messages are properly
reported (per review of Christian Brabandt).
related: vim/vim#15411
https://github.com/vim/vim/commit/f0e9b72c8fdd47b9b410a11edf7479953cb2aed9
Co-authored-by: Damien <141588647+xrandomname@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: After 6f1cbfc9ab483a09877e153ad130164875c40b1d fnameescape()
is no longer called on the name of the file to be extracted.
However, while spaces indeed don't need to be escaped, unzip
treats '[' as a wildcard character, so it need to be escaped.
Solution: Escape '[' on both MS-Windows and Unix.
From the docs it seems '*' and '?' also need escaping, but they seem to
actually work without escaping.
fixes: neovim/neovim#29977
closes: vim/vim#15427
https://github.com/vim/vim/commit/c5bdd66558b14f04424a22d9714a9b7d0c277dac
Co-authored-by: zeertzjq <zeertzjq@outlook.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
`:{S,H,V}explore`
Make `:Sexplore` / `:Hexplore` / `:Vexplore` commands honor the user
`&split{right,below}` settings (or netrw-specific `g:netrw_alt{o,v}`)
instead of hardcoding a split direction. Similarly, update banged
variants of the two latter commands to follow the inverted preference.
closes: vim/vim#15417
https://github.com/vim/vim/commit/c527d90fae7210d6dc5cbdf7507f26a32455149b
Co-authored-by: Ivan Shapovalov <intelfx@intelfx.name>
|
|
|
|
|
|
|
|
|
|
| |
files in same directory
closes: vim/vim#14756
https://github.com/vim/vim/commit/e34d0e37e397419636ae5d27d4b236b193efef07
Co-authored-by: Travis Shelton <tshelton.mail@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: Opening a zipfile from HTTP gives an empty buffer.
Solution: Ensure that the magic bytes check does not
skip protocol processing.
Also use readblob() and remove commented out lines.
closes: vim/vim#15396
https://github.com/vim/vim/commit/c4be066817d560c870f67f1593630cfb5b39dfc8
Co-authored-by: Damien <141588647+xrandomname@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
| |
This is safer because we don't invoke the shell.
closes: vim/vim#15335
https://github.com/vim/vim/commit/2cad941dc0cb57bca577160eb3a349de2e667bcd
Co-authored-by: Damien <141588647+xrandomname@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: Enter 'x' in zip browser fail with E121
Solution: Fix typo in zip#Extract()
closes: vim/vim#15321
https://github.com/vim/vim/commit/38ce71c1c323716cc4b130dbb3e8837a8b9a710b
Co-authored-by: Damien <141588647+xrandomname@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
| |
it (#29838)
fixes: vim/vim#15330
https://github.com/vim/vim/commit/581d4a7b356395bcb8606c1717ded65d47d26c68
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Problem: ':E /etc BOOM' give E132 error.
Solution: Avoid recursion call with same arguments.
fixes: vim/vim#5723
closes: vim/vim#15318
https://github.com/vim/vim/commit/9d57ea5cd3a23af02c72c0e86fe24b7bba57189a
Co-authored-by: Damien <141588647+xrandomname@users.noreply.github.com>
|
|
|
|
|
|
|
|
| |
closes: vim/vim#15234
https://github.com/vim/vim/commit/1cc4cae961a7b49608ef7bd56837cc723d49db4d
Co-authored-by: Gregory Anders <greg@gpanders.com>
|
|
|
|
|
|
|
|
|
|
| |
complements 62f7b55c1a4564f8744af9446bc7af47fe16a245
closes: vim/vim#15114
https://github.com/vim/vim/commit/3146d63267664e0a0afdbe14be0cec30e7168a04
Co-authored-by: Enno <Konfekt@users.noreply.github.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a breaking change which will make refactor of typval and shada
code a lot easier. In particular, code that would use or check for
v:msgpack_types.binary in the wild would be broken. This appears to be
rarely used in existing plugins.
Also some cases where v:msgpack_type.string would be used to represent a
binary string of "string" type, we use a BLOB instead, which is
vimscripts native type for binary blobs, and already was used for BIN
formats when necessary.
msgpackdump(msgpackparse(data)) no longer preserves the distinction
of BIN and STR strings. This is very common behavior for
language-specific msgpack bindings. Nvim uses msgpack as a tool to
serialize its data. Nvim is not a tool to bit-perfectly manipulate
arbitrary msgpack data out in the wild.
The changed tests should indicate how behavior changes in various edge
cases.
|
|
|
|
|
|
|
|
|
| |
unnamed (#29479)
fixes: vim/vim#15077
https://github.com/vim/vim/commit/62f7b55c1a4564f8744af9446bc7af47fe16a245
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
|
| |
This was wrongly included as of patch 1c6734291295bf8aa39577840b40bb
because apparently I messed up the use of git apply :/
https://github.com/vim/vim/commit/52f2ff03636fe120f3c9d00e9b3cdc1da251bd73
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change does the following 3 things:
1) non need to quote the file to be extracted
The zipfile plugin used to quote and fnameescape() the path to the
file to be extracted. However testing with unzip showed, that while this
works on Linux on Windows you shall not escape the blanks in filenames.
As long as the pathname is properly quoted, this words on Linux and
Windows.
2) reset shellslash (MS-Windows only)
When shellslash is set, filenames to the zip archive will be forward
quoted. However since the filename is eventually handed over to the
unzip command, we need to make sure to use native paths so that the
command will understand what file to open. Therefore, if shellslash is
set (and the shell is cmd.exe), replace any forward slashes by the
expected backslashes
3) style:
Use tabs for the Header, remove a few comments in the s:Escape() and
zip#read() functions
fixes: vim/vim#14998
https://github.com/vim/vim/commit/1c6734291295bf8aa39577840b40bb21a7f27120
Co-authored-by: Christian Brabandt <cb@256bit.org>
|
|
|
|
|
|
|
|
|
|
| |
(#29330)
use has("win32") instead of has("win64") otherwise it
won't work on x86 systems.
https://github.com/vim/vim/commit/440746158ce0fec2880ccacc03f39dbc954c5543
Co-authored-by: Christian Brabandt <cb@256bit.org>
|