Groups
Sign in
Groups
vim_dev
Conversations
About
Send feedback
Help
vim_dev
Contact owners and managers
1–30 of 41747
Vim developers maillist
For an overview of all the Vim maillists see:
http://www.vim.org/maillist.
php
Mark all as read
Report group
0 selected
glepnir
44
6:02 AM
[vim/vim] feat(completion): add two highlight groups PmenuMatch and PmenuMatchSel (PR #14694)
@glepnir pushed 1 commit. ebc886b feat(completion): add text matched highlight in candidate words —
unread,
[vim/vim] feat(completion): add two highlight groups PmenuMatch and PmenuMatchSel (PR #14694)
@glepnir pushed 1 commit. ebc886b feat(completion): add text matched highlight in candidate words —
6:02 AM
Anton Samokat
12
5:52 AM
[vim/vim] "Ctrl+o u" in Insert mode is performed with a about 3 seconds delay (Issue #14947)
@chrisbra I see, thanks — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] "Ctrl+o u" in Insert mode is performed with a about 3 seconds delay (Issue #14947)
@chrisbra I see, thanks — Reply to this email directly, view it on GitHub. You are receiving this
5:52 AM
errael
3
4:51 AM
[vim/vim] [termdebug vim9script] problems with saving/restoring string options (Issue #14957)
Done as commented in #14951. — Reply to this email directly, view it on GitHub. You are receiving
unread,
[vim/vim] [termdebug vim9script] problems with saving/restoring string options (Issue #14957)
Done as commented in #14951. — Reply to this email directly, view it on GitHub. You are receiving
4:51 AM
errael
8
4:51 AM
[vim/vim] Fix the mousemodel restoration fix. (PR #14951)
I took a look at if the issue appears to other variables initialized as empty strings and apparently
unread,
[vim/vim] Fix the mousemodel restoration fix. (PR #14951)
I took a look at if the issue appears to other variables initialized as empty strings and apparently
4:51 AM
Rolf Vidar Mazunki Hoksaas
16
3:29 AM
[vim/vim] runtime: add .vim8 as vim filetype (PR #14950)
Closed #14950. — Reply to this email directly, view it on GitHub. You are receiving this because you
unread,
[vim/vim] runtime: add .vim8 as vim filetype (PR #14950)
Closed #14950. — Reply to this email directly, view it on GitHub. You are receiving this because you
3:29 AM
arĉi
7
2:49 AM
[vim/vim] filetype: djot files not recognized (PR #14963)
Closed #14963. — Reply to this email directly, view it on GitHub. You are receiving this because you
unread,
[vim/vim] filetype: djot files not recognized (PR #14963)
Closed #14963. — Reply to this email directly, view it on GitHub. You are receiving this because you
2:49 AM
Christian Brabandt
5
2:35 AM
[vim/vim] fix Test_ColonEight_MultiByte() failure (PR #14958)
Anyhow, the marking the test as flaky has been removed as part of commit d03882b Ah, somehow I missed
unread,
[vim/vim] fix Test_ColonEight_MultiByte() failure (PR #14958)
Anyhow, the marking the test as flaky has been removed as part of commit d03882b Ah, somehow I missed
2:35 AM
Ali Rizvi-Santiago
4
2:22 AM
[vim/vim] E342, unsigned integer underflow in op_change when in visual-block mode (Issue #14960)
Closed #14960 as not planned. — Reply to this email directly, view it on GitHub. You are receiving
unread,
[vim/vim] E342, unsigned integer underflow in op_change when in visual-block mode (Issue #14960)
Closed #14960 as not planned. — Reply to this email directly, view it on GitHub. You are receiving
2:22 AM
K.Takata
2:13 AM
Re: [vim/vim] runtime(doc): Fix small style issues (9c4389a)
typos --- a/runtime/doc/syntax.txt +++ b/runtime/doc/syntax.txt @@ -937,10 +937,10 @@ Configuration
unread,
Re: [vim/vim] runtime(doc): Fix small style issues (9c4389a)
typos --- a/runtime/doc/syntax.txt +++ b/runtime/doc/syntax.txt @@ -937,10 +937,10 @@ Configuration
2:13 AM
glepnir
3
1:31 AM
[vim/vim] fix(completion): compl_shown_match not update when fuzzy with complete (PR #14955)
Nope. that pr has two questions: first he want the fuzzy can works like menuone when only one result
unread,
[vim/vim] fix(completion): compl_shown_match not update when fuzzy with complete (PR #14955)
Nope. that pr has two questions: first he want the fuzzy can works like menuone when only one result
1:31 AM
Yinzuo Jiang
2
Jun 10
[vim/vim] runtime(kdl): use shiftwidth() instead of &tabstop (PR #14962)
@dkearns thinks we should use shiftwidth() rather than &tabstop , so do I. #14956 (comment) —
unread,
[vim/vim] runtime(kdl): use shiftwidth() instead of &tabstop (PR #14962)
@dkearns thinks we should use shiftwidth() rather than &tabstop , so do I. #14956 (comment) —
Jun 10
Yegappan Lakshmanan
Jun 10
[vim/vim] Remove the line continuation character used in termdebug (PR #14961)
In term_start(), clear the WSP_VERT flag only if it is not already set in cmdmod.cmod_split. You can
unread,
[vim/vim] Remove the line continuation character used in termdebug (PR #14961)
In term_start(), clear the WSP_VERT flag only if it is not already set in cmdmod.cmod_split. You can
Jun 10
Peter Aronoff
Jun 10
[vim/vim] fix: clarify documentation for "v" position (PR #14959)
Problem: the previous documentation falsely states that "v" always refers to the start of a
unread,
[vim/vim] fix: clarify documentation for "v" position (PR #14959)
Problem: the previous documentation falsely states that "v" always refers to the start of a
Jun 10
lkintact
2
Jun 10
[vim/vim] Netrw incorrectly handles folders containing [] in their names (Issue #14952)
ah, one of the famous differences between how filenames are handled differently on Windows and Unix :
unread,
[vim/vim] Netrw incorrectly handles folders containing [] in their names (Issue #14952)
ah, one of the famous differences between how filenames are handled differently on Windows and Unix :
Jun 10
James Cherti
9
Jun 10
[vim/vim] Netrw Tree Style Listing moves the cursor to a different position. (PR #10001)
Closed #10001. — Reply to this email directly, view it on GitHub. You are receiving this because you
unread,
[vim/vim] Netrw Tree Style Listing moves the cursor to a different position. (PR #10001)
Closed #10001. — Reply to this email directly, view it on GitHub. You are receiving this because you
Jun 10
Vivian De Smedt
5
Jun 10
[vim/vim] Vimscript colorization doesn't support non matching parenthesis in the pattern section (Issue #14920)
I confirm that it solve the reported problem :-). Thanks for the support! — Reply to this email
unread,
[vim/vim] Vimscript colorization doesn't support non matching parenthesis in the pattern section (Issue #14920)
I confirm that it solve the reported problem :-). Thanks for the support! — Reply to this email
Jun 10
Scott Mcdermott
,
Yegappan Lakshmanan
11
Jun 10
[vim/vim] Make indentexpr evaluate from older vim scripts (PR #14936)
Hm, it seems like those autoloaded functions are automatically translated into autoloadable form, in
unread,
[vim/vim] Make indentexpr evaluate from older vim scripts (PR #14936)
Hm, it seems like those autoloaded functions are automatically translated into autoloadable form, in
Jun 10
Yinzuo Jiang
5
Jun 10
[vim/vim] runtime(kdl): Add syntax, indent and ftplugin files (PR #14956)
@dkearns commented on this pull request. In runtime/indent/kdl.vim: > +" Only load this
unread,
[vim/vim] runtime(kdl): Add syntax, indent and ftplugin files (PR #14956)
@dkearns commented on this pull request. In runtime/indent/kdl.vim: > +" Only load this
Jun 10
Aliaksei Budavei
12
Jun 10
[vim/vim] Screen dumps may omit lines for test files with lines longer than 75 columns (Issue #14245)
The above Vim files are likely outdated duplicates, but not vim_ex_func_*, and can be removed, can
unread,
[vim/vim] Screen dumps may omit lines for test files with lines longer than 75 columns (Issue #14245)
The above Vim files are likely outdated duplicates, but not vim_ex_func_*, and can be removed, can
Jun 10
dkearns
6
Jun 10
[vim/vim] runtime(vim): Update base-syntax, configurable comment string highlighting (PR #14931)
@zzzyxwvut commented on this pull request. In runtime/doc/syntax.txt: > @@ -3834,7 +3833,11 @@ By
unread,
[vim/vim] runtime(vim): Update base-syntax, configurable comment string highlighting (PR #14931)
@zzzyxwvut commented on this pull request. In runtime/doc/syntax.txt: > @@ -3834,7 +3833,11 @@ By
Jun 10
Christian Brabandt
Jun 10
Commit: runtime(kdl): include syntax, indent and ftplugin files
runtime(kdl): include syntax, indent and ftplugin files Commit: https://github.com/vim/vim/commit/
unread,
Commit: runtime(kdl): include syntax, indent and ftplugin files
runtime(kdl): include syntax, indent and ftplugin files Commit: https://github.com/vim/vim/commit/
Jun 10
Christian Brabandt
5
Jun 10
[vim/vim] runtime(vim): correctly handle ! attribute for augroup/doautocmd/doautoall (PR #14906)
I can take it if you're not in a hurry for the intermediate fix. — Reply to this email directly,
unread,
[vim/vim] runtime(vim): correctly handle ! attribute for augroup/doautocmd/doautoall (PR #14906)
I can take it if you're not in a hurry for the intermediate fix. — Reply to this email directly,
Jun 10
Christian Brabandt
Jun 10
Commit: patch 9.1.0474: CI: Test_ColonEight() fails on github runners
patch 9.1.0474: CI: Test_ColonEight() fails on github runners Commit: https://github.com/vim/vim/
unread,
Commit: patch 9.1.0474: CI: Test_ColonEight() fails on github runners
patch 9.1.0474: CI: Test_ColonEight() fails on github runners Commit: https://github.com/vim/vim/
Jun 10
K.Takata
4
Jun 10
[vim/vim] CI: Test_ColonEight_MultiByte() fails with the latest GHA image (Issue #14954)
Closed #14954 as completed via d03882b. — Reply to this email directly, view it on GitHub. You are
unread,
[vim/vim] CI: Test_ColonEight_MultiByte() fails with the latest GHA image (Issue #14954)
Closed #14954 as completed via d03882b. — Reply to this email directly, view it on GitHub. You are
Jun 10
Farid Cheraghi
4
Jun 10
[vim/vim] zero width non-joiner (ZWNJ) renders as its Unicode codepoint <200c> (#7932)
duplicate of #204 — Reply to this email directly, view it on GitHub. You are receiving this because
unread,
[vim/vim] zero width non-joiner (ZWNJ) renders as its Unicode codepoint <200c> (#7932)
duplicate of #204 — Reply to this email directly, view it on GitHub. You are receiving this because
Jun 10
Xcess
15
Jun 10
Re: [vim/vim] Please add BiDi support to Vim (#204)
I had a quick look, but completely hiding probably doesn't make sense (and we don't do this
unread,
Re: [vim/vim] Please add BiDi support to Vim (#204)
I had a quick look, but completely hiding probably doesn't make sense (and we don't do this
Jun 10
Igor Lacerda
4
Jun 10
[vim/vim] runtime(svelte): basic svelte ftplugin file (PR #14949)
Any thoughts @towry? — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] runtime(svelte): basic svelte ftplugin file (PR #14949)
Any thoughts @towry? — Reply to this email directly, view it on GitHub. You are receiving this
Jun 10
Christian Brabandt
Jun 10
Commit: runtime(svelte): basic svelte ftplugin file
runtime(svelte): basic svelte ftplugin file Commit: https://github.com/vim/vim/commit/
unread,
Commit: runtime(svelte): basic svelte ftplugin file
runtime(svelte): basic svelte ftplugin file Commit: https://github.com/vim/vim/commit/
Jun 10
Christian Brabandt
Jun 10
Commit: runtime(deb822sources): add missing Enabled field in syntax script
runtime(deb822sources): add missing Enabled field in syntax script Commit: https://github.com/vim/vim
unread,
Commit: runtime(deb822sources): add missing Enabled field in syntax script
runtime(deb822sources): add missing Enabled field in syntax script Commit: https://github.com/vim/vim
Jun 10
Christian Brabandt
Jun 10
Commit: patch 9.1.0473: term_start() does not clear vertical modifier
patch 9.1.0473: term_start() does not clear vertical modifier Commit: https://github.com/vim/vim/
unread,
Commit: patch 9.1.0473: term_start() does not clear vertical modifier
patch 9.1.0473: term_start() does not clear vertical modifier Commit: https://github.com/vim/vim/
Jun 10