vim_dev

Contact owners and managers

1–30 of 41871

Vim developers maillist

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

0 selected

4:34 PM

[vim/vim] Termdebug8 (PR #15027)

Copy from last legacy version before vim9 port. Rename legacy termdebug commands to Termdebug8. With

unread,

[vim/vim] Termdebug8 (PR #15027)

Copy from last legacy version before vim9 port. Rename legacy termdebug commands to Termdebug8. With

4:34 PM

2:17 PM

[vim/vim] [termdebug vim9script] problems with saving/restoring string options (Issue #14957)

'DAP' etc seems not a very matter to termdebug. #11605 — Reply to this email directly, view

unread,

[vim/vim] [termdebug vim9script] problems with saving/restoring string options (Issue #14957)

'DAP' etc seems not a very matter to termdebug. #11605 — Reply to this email directly, view

2:17 PM

Christian Brabandt3

1:44 PM

[vim/vim] create popup_setbuf() function (PR #15026)

@yegappan requested changes on this pull request. In src/popupwin.c: > +/* + * popup_setbuf({id},

unread,

[vim/vim] create popup_setbuf() function (PR #15026)

@yegappan requested changes on this pull request. In src/popupwin.c: > +/* + * popup_setbuf({id},

1:44 PM

1:40 PM

[vim/vim] Undo works differently when buffer is populated by job_start() (Issue #15025)

According to :help undojoin , calling getchar() should start a new change. That does not seem to be

unread,

[vim/vim] Undo works differently when buffer is populated by job_start() (Issue #15025)

According to :help undojoin , calling getchar() should start a new change. That does not seem to be

1:40 PM

Stanislav Asunkin3

1:39 PM

[vim/vim] Returning to help buffer resets scrolloff (Issue #15024)

When reading :h local-options (the part where examples with list option) I thought that even window-

unread,

[vim/vim] Returning to help buffer resets scrolloff (Issue #15024)

When reading :h local-options (the part where examples with list option) I thought that even window-

1:39 PM

Christian Brabandt

11:00 AM

Commit: runtime(java): Add a config variable for commonly used compiler options

runtime(java): Add a config variable for commonly used compiler options Commit: https://github.com/

unread,

Commit: runtime(java): Add a config variable for commonly used compiler options

runtime(java): Add a config variable for commonly used compiler options Commit: https://github.com/

11:00 AM

Christian Brabandt

11:00 AM

Commit: patch 9.1.0494: Wrong matched text highlighted in pum with 'rightleft'

patch 9.1.0494: Wrong matched text highlighted in pum with 'rightleft' Commit: https://github

unread,

Commit: patch 9.1.0494: Wrong matched text highlighted in pum with 'rightleft'

patch 9.1.0494: Wrong matched text highlighted in pum with 'rightleft' Commit: https://github

11:00 AM

Christian Brabandt

11:00 AM

Commit: runtime(html): bump length of character references in syntax script (#15022)

runtime(html): bump length of character references in syntax script (#15022) Commit: https://github.

unread,

Commit: runtime(html): bump length of character references in syntax script (#15022)

runtime(html): bump length of character references in syntax script (#15022) Commit: https://github.

11:00 AM

Christian Brabandt

11:00 AM

Commit: runtime(termdebug): properly check mapping variables using null_dict

runtime(termdebug): properly check mapping variables using null_dict Commit: https://github.com/vim/

unread,

Commit: runtime(termdebug): properly check mapping variables using null_dict

runtime(termdebug): properly check mapping variables using null_dict Commit: https://github.com/vim/

11:00 AM

10:59 AM

[vim/vim] runtime(java): Add a config variable for commonly used compiler options (PR #14999)

Closed #14999 via 0ddab58. — Reply to this email directly, view it on GitHub. You are receiving this

unread,

[vim/vim] runtime(java): Add a config variable for commonly used compiler options (PR #14999)

Closed #14999 via 0ddab58. — Reply to this email directly, view it on GitHub. You are receiving this

10:59 AM

10:53 AM

[vim/vim] fix(highlight): pum matched text respect icase (PR #15023)

@chrisbra commented on this pull request. In src/popupmenu.c: > @@ -485,7 +485,7 @@

unread,

[vim/vim] fix(highlight): pum matched text respect icase (PR #15023)

@chrisbra commented on this pull request. In src/popupmenu.c: > @@ -485,7 +485,7 @@

10:53 AM

10:53 AM

[vim/vim] Wrong matched text highlighted in pum with 'rightleft' (PR #15020)

Closed #15020 via 63901e8. — Reply to this email directly, view it on GitHub. You are receiving this

unread,

[vim/vim] Wrong matched text highlighted in pum with 'rightleft' (PR #15020)

Closed #15020 via 63901e8. — Reply to this email directly, view it on GitHub. You are receiving this

10:53 AM

10:48 AM

[vim/vim] runtime(html): bump length of character references (PR #15022)

Merged #15022 into master. — Reply to this email directly, view it on GitHub. You are receiving this

unread,

[vim/vim] runtime(html): bump length of character references (PR #15022)

Merged #15022 into master. — Reply to this email directly, view it on GitHub. You are receiving this

10:48 AM

Shane-XB-Qian15

10:46 AM

[vim/vim] fix: [termdebug] correct K/-/+ mappings check (PR #15013)

Closed #15013 via a5af73a. — Reply to this email directly, view it on GitHub. You are receiving this

unread,

[vim/vim] fix: [termdebug] correct K/-/+ mappings check (PR #15013)

Closed #15013 via a5af73a. — Reply to this email directly, view it on GitHub. You are receiving this

10:46 AM

9:25 AM

[vim/vim] runtime(vim): Update base-syntax, match shebang lines (PR #15011)

> oh does this actually work? can we use a shebang line and run a vimscript directly? Is this

unread,

[vim/vim] runtime(vim): Update base-syntax, match shebang lines (PR #15011)

> oh does this actually work? can we use a shebang line and run a vimscript directly? Is this

9:25 AM

Shane-XB-Qian21

8:31 AM

[vim/vim] highlight groups PmenuMatch and PmenuMatchSel some buggy (Issue #15021)

Speaking of that, should matched text be highlighted for cmdline completion as well? i donot know, i

unread,

[vim/vim] highlight groups PmenuMatch and PmenuMatchSel some buggy (Issue #15021)

Speaking of that, should matched text be highlighted for cmdline completion as well? i donot know, i

8:31 AM

5:17 AM

[vim/vim] fix(completion): when only fuzzy no completion insert (PR #14976)

@Shane-XB-Qian commented on this pull request. In src/testdir/test_ins_complete.vim: > @@ -2599,7

unread,

[vim/vim] fix(completion): when only fuzzy no completion insert (PR #14976)

@Shane-XB-Qian commented on this pull request. In src/testdir/test_ins_complete.vim: > @@ -2599,7

5:17 AM

Christian Brabandt

3:00 AM

Commit: runtime(kdl): fix KdlIndent and kdlComment in indent script (#15019)

runtime(kdl): fix KdlIndent and kdlComment in indent script (#15019) Commit: https://github.com/vim/

unread,

Commit: runtime(kdl): fix KdlIndent and kdlComment in indent script (#15019)

runtime(kdl): fix KdlIndent and kdlComment in indent script (#15019) Commit: https://github.com/vim/

3:00 AM

Christian Brabandt

3:00 AM

Commit: patch 9.1.0493: Test for patch 9.1.0489 doesn't fail without the fix

patch 9.1.0493: Test for patch 9.1.0489 doesn't fail without the fix Commit: https://github.com/

unread,

Commit: patch 9.1.0493: Test for patch 9.1.0489 doesn't fail without the fix

patch 9.1.0493: Test for patch 9.1.0489 doesn't fail without the fix Commit: https://github.com/

3:00 AM

2:48 AM

[vim/vim] runtime(kdl): fix KdlIndent and kdlComment (PR #15019)

Merged #15019 into master. — Reply to this email directly, view it on GitHub. You are receiving this

unread,

[vim/vim] runtime(kdl): fix KdlIndent and kdlComment (PR #15019)

Merged #15019 into master. — Reply to this email directly, view it on GitHub. You are receiving this

2:48 AM

2:46 AM

[vim/vim] Test for patch 9.1.0489 doesn't fail without the fix (PR #15018)

Closed #15018 via acc8746. — Reply to this email directly, view it on GitHub. You are receiving this

unread,

[vim/vim] Test for patch 9.1.0489 doesn't fail without the fix (PR #15018)

Closed #15018 via acc8746. — Reply to this email directly, view it on GitHub. You are receiving this

2:46 AM

Christian Brabandt

2:45 AM

Commit: runtime(java): Fold multi-line comments with the syntax kind of &fdm (#15016)

runtime(java): Fold multi-line comments with the syntax kind of &fdm (#15016) Commit: https://

unread,

Commit: runtime(java): Fold multi-line comments with the syntax kind of &fdm (#15016)

runtime(java): Fold multi-line comments with the syntax kind of &fdm (#15016) Commit: https://

2:45 AM

Christian Brabandt

2:45 AM

Commit: runtime(termdebug): using wrong type for PlaceSign()

runtime(termdebug): using wrong type for PlaceSign() Commit: https://github.com/vim/vim/commit/

unread,

Commit: runtime(termdebug): using wrong type for PlaceSign()

runtime(termdebug): using wrong type for PlaceSign() Commit: https://github.com/vim/vim/commit/

2:45 AM

Christian Brabandt

2:45 AM

Commit: patch 9.1.0492: filetype: Vim-script files not detected by shebang line

patch 9.1.0492: filetype: Vim-script files not detected by shebang line Commit: https://github.com/

unread,

Commit: patch 9.1.0492: filetype: Vim-script files not detected by shebang line

patch 9.1.0492: filetype: Vim-script files not detected by shebang line Commit: https://github.com/

2:45 AM

Aliaksei Budavei4

2:43 AM

[vim/vim] runtime(java): Fold multi-line comments with the syntax kind of &fdm (PR #15016)

Merged #15016 into master. — Reply to this email directly, view it on GitHub. You are receiving this

unread,

[vim/vim] runtime(java): Fold multi-line comments with the syntax kind of &fdm (PR #15016)

Merged #15016 into master. — Reply to this email directly, view it on GitHub. You are receiving this

2:43 AM

2:39 AM

[vim/vim] Implement lstat() for Windows (PR #15014)

thank you! can we get a test please? — Reply to this email directly, view it on GitHub. You are

unread,

[vim/vim] Implement lstat() for Windows (PR #15014)

thank you! can we get a test please? — Reply to this email directly, view it on GitHub. You are

2:39 AM

2:38 AM

[vim/vim] [termdebug vim9script] Problems debugging vim with vim's termdebug (Issue #14994)

Closed #14994 as completed via f127dce. — Reply to this email directly, view it on GitHub. You are

unread,

[vim/vim] [termdebug vim9script] Problems debugging vim with vim's termdebug (Issue #14994)

Closed #14994 as completed via f127dce. — Reply to this email directly, view it on GitHub. You are

2:38 AM

2:38 AM

[vim/vim] fix: [termdebug] id/subid maybe mis-match type (PR #15015)

Closed #15015 via f127dce. — Reply to this email directly, view it on GitHub. You are receiving this

unread,

[vim/vim] fix: [termdebug] id/subid maybe mis-match type (PR #15015)

Closed #15015 via f127dce. — Reply to this email directly, view it on GitHub. You are receiving this

2:38 AM

2:34 AM

[vim/vim] filetype: Vim-script files not detected by shebang line (PR #15012)

Closed #15012 via 0d4d23d. — Reply to this email directly, view it on GitHub. You are receiving this

unread,

[vim/vim] filetype: Vim-script files not detected by shebang line (PR #15012)

Closed #15012 via 0d4d23d. — Reply to this email directly, view it on GitHub. You are receiving this

2:34 AM

Ernie Rael, Christian Brabandt4

Jun 15

How to use the old termdebug

I've got a patch which includes both the legacy and vim9script termdebug. I set it up so by

unread,

How to use the old termdebug

I've got a patch which includes both the legacy and vim9script termdebug. I set it up so by

Jun 15

Search

Clear search

Close search

Google apps

Main menu