Groups

vim_dev

1–30 of 48208

Vim developers maillist

For an overview of all the Vim maillists see: http://www.vim.org/maillist.php

0 selected

6:27 PM

[vim/vim] ft: add j2 as jinja (PR #18612)

Recognizes .j2 files as Jinja templates by adding a "j2": "jinja" mapping in vim/

unread,

[vim/vim] ft: add j2 as jinja (PR #18612)

Recognizes .j2 files as Jinja templates by adding a "j2": "jinja" mapping in vim/

6:27 PM

5:54 PM

[vim/vim] Add jinja2 filetype for .j2 files (PR #18609)

Closed #18609. — Reply to this email directly, view it on GitHub. You are receiving this because you

unread,

[vim/vim] Add jinja2 filetype for .j2 files (PR #18609)

Closed #18609. — Reply to this email directly, view it on GitHub. You are receiving this because you

5:54 PM

4:52 PM

[vim/vim] runtime/doc/vim9.txt - Section 4 updated (PR #18610)

kennypete left a comment (vim/vim#18610) So this error code should not be removed. Thanks, that error

unread,

[vim/vim] runtime/doc/vim9.txt - Section 4 updated (PR #18610)

kennypete left a comment (vim/vim#18610) So this error code should not be removed. Thanks, that error

4:52 PM

4:35 PM

[vim/vim] Java ftplugin does not change the 'include' option to match Java import statements (#2663)

zzzyxwvut left a comment (vim/vim#2663) This request has been fulfilled (see #17281). — Reply to this

unread,

[vim/vim] Java ftplugin does not change the 'include' option to match Java import statements (#2663)

zzzyxwvut left a comment (vim/vim#2663) This request has been fulfilled (see #17281). — Reply to this

4:35 PM

Václav Kobera2

3:47 PM

[vim/vim] Fix netrw remote uri parse (PR #18611)

@Swantosaurus pushed 1 commit. 775da7f remove trailing whitespaces — View it on GitHub or unsubscribe

unread,

[vim/vim] Fix netrw remote uri parse (PR #18611)

@Swantosaurus pushed 1 commit. 775da7f remove trailing whitespaces — View it on GitHub or unsubscribe

3:47 PM

12:41 PM

[vim/vim] Improve test_codestyle whitespace testing (PR #18599)

@dkearns pushed 1 commit. 365133a Improve test_codestyle help file whitespace testing — View it on

unread,

[vim/vim] Improve test_codestyle whitespace testing (PR #18599)

@dkearns pushed 1 commit. 365133a Improve test_codestyle help file whitespace testing — View it on

12:41 PM

10:44 AM

[vim/vim] Cmdline history not updated when mapping both <Up> and <CR> (PR #18607)

@zeertzjq pushed 1 commit. d8849b5 Cmdline history not updated when mapping both <Up> and <

unread,

[vim/vim] Cmdline history not updated when mapping both <Up> and <CR> (PR #18607)

@zeertzjq pushed 1 commit. d8849b5 Cmdline history not updated when mapping both <Up> and <

10:44 AM

9:42 AM

[vim/vim] How to fix `vim` sometimes starting in `REPLACE` mode? (Discussion #18608)

On this box I'm using Git Bash in Windows Terminal. I have fzf around. Together with its bash-

unread,

[vim/vim] How to fix `vim` sometimes starting in `REPLACE` mode? (Discussion #18608)

On this box I'm using Git Bash in Windows Terminal. I have fzf around. Together with its bash-

9:42 AM

8:03 AM

[vim/vim] completeopt+=popup might be too narrow (Issue #18606)

girishji left a comment (vim/vim#18606) In your screenshot, do you expect the info window to sit

unread,

[vim/vim] completeopt+=popup might be too narrow (Issue #18606)

girishji left a comment (vim/vim#18606) In your screenshot, do you expect the info window to sit

8:03 AM

Linwei, … Bram Moolenaar204

7:02 AM

[vim/vim] [proposal] Can we introduce TextMate grammar system for syntax highlighting ? (Issue #9087)

albfan left a comment (vim/vim#9087) @jclsn totally open for that. I inspect their repos and looks

unread,

[vim/vim] [proposal] Can we introduce TextMate grammar system for syntax highlighting ? (Issue #9087)

albfan left a comment (vim/vim#9087) @jclsn totally open for that. I inspect their repos and looks

7:02 AM

6:18 AM

[vim/vim] Prevent makeTargetinDefine matching extra line (PR #18570)

@rohieb approved this pull request. — Reply to this email directly, view it on GitHub, or unsubscribe

unread,

[vim/vim] Prevent makeTargetinDefine matching extra line (PR #18570)

@rohieb approved this pull request. — Reply to this email directly, view it on GitHub, or unsubscribe

6:18 AM

Oct 19

[vim/vim] can't run `normal! n` in a command block (Issue #18605)

zeertzjq left a comment (vim/vim#18605) Related #14491 — Reply to this email directly, view it on

unread,

[vim/vim] can't run `normal! n` in a command block (Issue #18605)

zeertzjq left a comment (vim/vim#18605) Related #14491 — Reply to this email directly, view it on

Oct 19

Oct 19

[vim/vim] Sunset `completefuzzycollect` option (Issue #18498)

habamax left a comment (vim/vim#18498) @chrisbra I believe now you have enough information to make a

unread,

[vim/vim] Sunset `completefuzzycollect` option (Issue #18498)

habamax left a comment (vim/vim#18498) @chrisbra I believe now you have enough information to make a

Oct 19

Oct 19

[vim/vim] incorrect syntax highlighting of local variable assigned an array with bash (Issue #18472)

zzzyxwvut left a comment (vim/vim#18472) Both parentheses (of shArrayRegion ) are rendered in the

unread,

[vim/vim] incorrect syntax highlighting of local variable assigned an array with bash (Issue #18472)

zzzyxwvut left a comment (vim/vim#18472) Both parentheses (of shArrayRegion ) are rendered in the

Oct 19

Aliaksei Budavei3

Oct 19

[vim/vim] CI: Include a job index in names of collected artifacts (PR #18556)

@zzzyxwvut pushed 1 commit. d50e3a0 CI: Include a job index in names of collected artifacts — View it

unread,

[vim/vim] CI: Include a job index in names of collected artifacts (PR #18556)

@zzzyxwvut pushed 1 commit. d50e3a0 CI: Include a job index in names of collected artifacts — View it

Oct 19

Oct 19

[vim/vim] Add OSC52 plugin for clipboard support (PR #18575)

alex-huff left a comment (vim/vim#18575) I experience the same issues. However, if I manually run :

unread,

[vim/vim] Add OSC52 plugin for clipboard support (PR #18575)

alex-huff left a comment (vim/vim#18575) I experience the same issues. However, if I manually run :

Oct 19

Oct 19

[vim/vim] Capture backtrace (Issue #18604)

albfan created an issue (vim/vim#18604) In the middle of a debug session can be nice to see current

unread,

[vim/vim] Capture backtrace (Issue #18604)

albfan created an issue (vim/vim#18604) In the middle of a debug session can be nice to see current

Oct 19

Oct 19

[vim/vim] runtime(doc): Improve highlighting of the +feature-list table (PR #18603)

@dkearns pushed 1 commit. ae374a4 runtime(doc): Improve highlighting of the +feature-list table —

unread,

[vim/vim] runtime(doc): Improve highlighting of the +feature-list table (PR #18603)

@dkearns pushed 1 commit. ae374a4 runtime(doc): Improve highlighting of the +feature-list table —

Oct 19

Phạm Bình An

Oct 19

[vim/vim] runtime(ftplugin): don't create new user commands for keywordprg (PR #18602)

Problems Creating a new user command for 'keywordprg' makes it visible to users in '

unread,

[vim/vim] runtime(ftplugin): don't create new user commands for keywordprg (PR #18602)

Problems Creating a new user command for 'keywordprg' makes it visible to users in '

Oct 19

Oct 19

[vim/vim] runtime(doc): Improve header formmating (PR #18601)

@dkearns pushed 1 commit. 9a57e66 runtime(doc): Improve header formatting — View it on GitHub or

unread,

[vim/vim] runtime(doc): Improve header formmating (PR #18601)

@dkearns pushed 1 commit. 9a57e66 runtime(doc): Improve header formatting — View it on GitHub or

Oct 19

Oct 18

[vim/vim] patch 9.1.1857 (Missing clipboard provider support) appears to break backward compatibility (Issue #18600)

peterwu created an issue (vim/vim#18600) Steps to reproduce On macOS (26.0.1), I built from the

unread,

[vim/vim] patch 9.1.1857 (Missing clipboard provider support) appears to break backward compatibility (Issue #18600)

peterwu created an issue (vim/vim#18600) Steps to reproduce On macOS (26.0.1), I built from the

Oct 18

Oct 18

Re: [vim/vim] runtime(doc): Normalise formatting of builtin function descriptions (83eb1da)

@dkearns I have no intention of changing tw=78 , and I think the current behavior of formatting using

unread,

Re: [vim/vim] runtime(doc): Normalise formatting of builtin function descriptions (83eb1da)

@dkearns I have no intention of changing tw=78 , and I think the current behavior of formatting using

Oct 18

Christian Brabandt

Oct 18

Commit: patch 9.1.1868: v:register is wrong in v_: command

patch 9.1.1868: v:register is wrong in v_: command Commit: https://github.com/vim/vim/commit/

unread,

Commit: patch 9.1.1868: v:register is wrong in v_: command

patch 9.1.1868: v:register is wrong in v_: command Commit: https://github.com/vim/vim/commit/

Oct 18

Christian Brabandt

Oct 18

Commit: patch 9.1.1867: HAVE_STDARG_H still defined

patch 9.1.1867: HAVE_STDARG_H still defined Commit: https://github.com/vim/vim/commit/

unread,

Commit: patch 9.1.1867: HAVE_STDARG_H still defined

patch 9.1.1867: HAVE_STDARG_H still defined Commit: https://github.com/vim/vim/commit/

Oct 18

Tony Mechelynck, … Christian Brabandt5

Oct 18

Warning -Wmaybe-uninitialized in normal.c at 9.1.1863 (and possibly shortly before it)

On Sa, 18 Okt 2025, Christian Brabandt wrote: > Ah yes, possible. Let's see if https://github.

unread,

Warning -Wmaybe-uninitialized in normal.c at 9.1.1863 (and possibly shortly before it)

On Sa, 18 Okt 2025, Christian Brabandt wrote: > Ah yes, possible. Let's see if https://github.

Oct 18

Oct 18

[vim/vim] v:register is wrong in v_: command (PR #18597)

chrisbra left a comment (vim/vim#18597) thanks — Reply to this email directly, view it on GitHub. You

unread,

[vim/vim] v:register is wrong in v_: command (PR #18597)

chrisbra left a comment (vim/vim#18597) thanks — Reply to this email directly, view it on GitHub. You

Oct 18

Oct 18

[vim/vim] Fixing systemlist() on Windows (PR #18598)

MiguelBarro left a comment (vim/vim#18598) I don't think this makes sense. The documentation

unread,

[vim/vim] Fixing systemlist() on Windows (PR #18598)

MiguelBarro left a comment (vim/vim#18598) I don't think this makes sense. The documentation

Oct 18

Oct 18

[vim/vim] Problem: HAVE_STDARG_H is unused (PR #18593)

Closed #18593 via 5932ed3. — Reply to this email directly, view it on GitHub. You are receiving this

unread,

[vim/vim] Problem: HAVE_STDARG_H is unused (PR #18593)

Closed #18593 via 5932ed3. — Reply to this email directly, view it on GitHub. You are receiving this

Oct 18

Christian Brabandt

Oct 18

Commit: patch 9.1.1866: HAVE_STRCSPN define is unused

patch 9.1.1866: HAVE_STRCSPN define is unused Commit: https://github.com/vim/vim/commit/

unread,

Commit: patch 9.1.1866: HAVE_STRCSPN define is unused

patch 9.1.1866: HAVE_STRCSPN define is unused Commit: https://github.com/vim/vim/commit/

Oct 18

Christian Brabandt

Oct 18

Commit: patch 9.1.1865: tests: do not notice lines containing only a tab

patch 9.1.1865: tests: do not notice lines containing only a tab Commit: https://github.com/vim/vim/

unread,

Commit: patch 9.1.1865: tests: do not notice lines containing only a tab

patch 9.1.1865: tests: do not notice lines containing only a tab Commit: https://github.com/vim/vim/

Oct 18

Search

Clear search

Close search

Google apps

Main menu