Groups
Sign in
Groups
vim_dev
Conversations
About
Send feedback
Help
vim_dev
Contact owners and managers
1–30 of 41562
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
Riley Bruins
,
Ajit Thakkar
18
12:49 PM
[vim/vim] feat(runtime)!: add padding to commentstrings (PR #14843)
I am fine with the changes in general, and in particular to the fortran ftplugin. It might indeed be
unread,
[vim/vim] feat(runtime)!: add padding to commentstrings (PR #14843)
I am fine with the changes in general, and in particular to the fortran ftplugin. It might indeed be
12:49 PM
giri
3
11:45 AM
[vim/vim] HighlightedYank feature (Issue #14848)
And I don't quite understand how getregionpos() makes this simpler. It worked perfectly fine with
unread,
[vim/vim] HighlightedYank feature (Issue #14848)
And I don't quite understand how getregionpos() makes this simpler. It worked perfectly fine with
11:45 AM
James McCoy
11:08 AM
[vim/vim] Update Debian runtime files (PR #14849)
Add space in template for 'commentstring' Add 'comments' and 'commentstring'
unread,
[vim/vim] Update Debian runtime files (PR #14849)
Add space in template for 'commentstring' Add 'comments' and 'commentstring'
11:08 AM
Yegappan Lakshmanan
6
9:12 AM
[vim/vim] Fix a Coverity warning, add a test and reduce the calls to clear_tv() (PR #14845)
@yegappan pushed 1 commit. dc12cf5 After clearing the type, set it to VAR_UNKNOWN — View it on GitHub
unread,
[vim/vim] Fix a Coverity warning, add a test and reduce the calls to clear_tv() (PR #14845)
@yegappan pushed 1 commit. dc12cf5 After clearing the type, set it to VAR_UNKNOWN — View it on GitHub
9:12 AM
zeertzjq
5
9:00 AM
[vim/vim] getregionpos() wrong with blockwise mode and multibyte (PR #14805)
Thanks! — Reply to this email directly, view it on GitHub. You are receiving this because you are
unread,
[vim/vim] getregionpos() wrong with blockwise mode and multibyte (PR #14805)
Thanks! — Reply to this email directly, view it on GitHub. You are receiving this because you are
9:00 AM
chdiza
8:56 AM
[vim/vim] New compiler warnings in 9.1.444 (Issue #14847)
Steps to reproduce Run ./configure with the following flags: --with-x --enable-gui=gtk3 --x-includes=
unread,
[vim/vim] New compiler warnings in 9.1.444 (Issue #14847)
Steps to reproduce Run ./configure with the following flags: --with-x --enable-gui=gtk3 --x-includes=
8:56 AM
Sanbei
7:33 AM
Re: [vim/vim] patch 9.1.0444: Not enough tests for getregion() with multibyte chars (dff55a3)
It's very well written. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
Re: [vim/vim] patch 9.1.0444: Not enough tests for getregion() with multibyte chars (dff55a3)
It's very well written. — Reply to this email directly, view it on GitHub. You are receiving this
7:33 AM
lkintact
4
7:30 AM
[vim/vim] A correction to the docs (Issue #14846)
Closed #14846 as completed. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] A correction to the docs (Issue #14846)
Closed #14846 as completed. — Reply to this email directly, view it on GitHub. You are receiving this
7:30 AM
Christian Brabandt
4:30 AM
Commit: patch 9.1.0444: Not enough tests for getregion() with multibyte chars
patch 9.1.0444: Not enough tests for getregion() with multibyte chars Commit: https://github.com/vim/
unread,
Commit: patch 9.1.0444: Not enough tests for getregion() with multibyte chars
patch 9.1.0444: Not enough tests for getregion() with multibyte chars Commit: https://github.com/vim/
4:30 AM
zeertzjq
3
4:27 AM
[vim/vim] Not enough tests for getregion() with multibyte chars (PR #14844)
Closed #14844 via dff55a3. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] Not enough tests for getregion() with multibyte chars (PR #14844)
Closed #14844 via dff55a3. — Reply to this email directly, view it on GitHub. You are receiving this
4:27 AM
zeertzjq
5
May 24
[vim/vim] getregionpos() can't properly indicate positions beyond eol (PR #14838)
@zeertzjq commented on this pull request. In runtime/doc/builtin.txt: > @@ -4348,6 +4348,19 @@
unread,
[vim/vim] getregionpos() can't properly indicate positions beyond eol (PR #14838)
@zeertzjq commented on this pull request. In runtime/doc/builtin.txt: > @@ -4348,6 +4348,19 @@
May 24
Amelia Clarke
11
May 24
[vim/vim] runtime(hare): update hare.vim to match upstream (PR #14836)
@selenebun commented on this pull request. In runtime/autoload/hare.vim: > @@ -0,0 +1,26 @@ +
unread,
[vim/vim] runtime(hare): update hare.vim to match upstream (PR #14836)
@selenebun commented on this pull request. In runtime/autoload/hare.vim: > @@ -0,0 +1,26 @@ +
May 24
Linda_pp
11
May 24
[vim/vim] runtime(typescript): update outdated syntax files (PR #14840)
thank you! — Reply to this email directly, view it on GitHub. You are receiving this because you are
unread,
[vim/vim] runtime(typescript): update outdated syntax files (PR #14840)
thank you! — Reply to this email directly, view it on GitHub. You are receiving this because you are
May 24
Christian Brabandt
May 24
Commit: runtime(typescript): update outdated syntax files
runtime(typescript): update outdated syntax files Commit: https://github.com/vim/vim/commit/
unread,
Commit: runtime(typescript): update outdated syntax files
runtime(typescript): update outdated syntax files Commit: https://github.com/vim/vim/commit/
May 24
Christian Brabandt
May 24
Commit: patch 9.1.0443: Can't use blockwise selection with width for getregion()
patch 9.1.0443: Can't use blockwise selection with width for getregion() Commit: https://github.
unread,
Commit: patch 9.1.0443: Can't use blockwise selection with width for getregion()
patch 9.1.0443: Can't use blockwise selection with width for getregion() Commit: https://github.
May 24
zeertzjq
6
May 24
[vim/vim] Can't use blockwise selection with width for getregion() (PR #14842)
Closed #14842 via afc2295. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] Can't use blockwise selection with width for getregion() (PR #14842)
Closed #14842 via afc2295. — Reply to this email directly, view it on GitHub. You are receiving this
May 24
Kyoh
3
May 24
[vim/vim] Highlighting for the type notation in the import block is broken (Issue #14721)
Closed #14721 as completed via 5e45715. — Reply to this email directly, view it on GitHub. You are
unread,
[vim/vim] Highlighting for the type notation in the import block is broken (Issue #14721)
Closed #14721 as completed via 5e45715. — Reply to this email directly, view it on GitHub. You are
May 24
Christian Brabandt
May 24
Commit: runtime(i3config/swayconfig): fix floating_modifier highlight (#14841)
runtime(i3config/swayconfig): fix floating_modifier highlight (#14841) Commit: https://github.com/vim
unread,
Commit: runtime(i3config/swayconfig): fix floating_modifier highlight (#14841)
runtime(i3config/swayconfig): fix floating_modifier highlight (#14841) Commit: https://github.com/vim
May 24
Josef Litoš
4
May 24
[vim/vim] fixup(i3/swayconfig): `floating_modifier` (PR #14841)
Merged #14841 into master. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] fixup(i3/swayconfig): `floating_modifier` (PR #14841)
Merged #14841 into master. — Reply to this email directly, view it on GitHub. You are receiving this
May 24
James Eapen
14
May 24
[vim/vim] fix(swayconfig): floating_modifier (PR #14827)
Ah I did focus more on the revert and the sway suggestion than the i3 diff. Thanks @JosefLitos, and
unread,
[vim/vim] fix(swayconfig): floating_modifier (PR #14827)
Ah I did focus more on the revert and the sway suggestion than the i3 diff. Thanks @JosefLitos, and
May 24
Christian Brabandt
May 24
Commit: patch 9.1.0442: hare runtime files outdated
patch 9.1.0442: hare runtime files outdated Commit: https://github.com/vim/vim/commit/
unread,
Commit: patch 9.1.0442: hare runtime files outdated
patch 9.1.0442: hare runtime files outdated Commit: https://github.com/vim/vim/commit/
May 24
Christian Brabandt
May 24
Commit: patch 9.1.0441: getregionpos() can't properly indicate positions beyond eol
patch 9.1.0441: getregionpos() can't properly indicate positions beyond eol Commit: https://
unread,
Commit: patch 9.1.0441: getregionpos() can't properly indicate positions beyond eol
patch 9.1.0441: getregionpos() can't properly indicate positions beyond eol Commit: https://
May 24
Christian Brabandt
May 24
Commit: patch 9.1.0440: function get_lval() is too long
patch 9.1.0440: function get_lval() is too long Commit: https://github.com/vim/vim/commit/
unread,
Commit: patch 9.1.0440: function get_lval() is too long
patch 9.1.0440: function get_lval() is too long Commit: https://github.com/vim/vim/commit/
May 24
Yegappan Lakshmanan
3
May 24
[vim/vim] Refactor the get_lval() function (PR #14839)
Closed #14839 via 44cadaa. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] Refactor the get_lval() function (PR #14839)
Closed #14839 via 44cadaa. — Reply to this email directly, view it on GitHub. You are receiving this
May 24
Christian Brabandt
May 24
Commit: patch 9.1.0439: Cannot filter the history
patch 9.1.0439: Cannot filter the history Commit: https://github.com/vim/vim/commit/
unread,
Commit: patch 9.1.0439: Cannot filter the history
patch 9.1.0439: Cannot filter the history Commit: https://github.com/vim/vim/commit/
May 24
Christian Brabandt
May 24
Commit: patch 9.1.0438: Wrong Ex command executed when :g uses '?' as delimiter
patch 9.1.0438: Wrong Ex command executed when :g uses '?' as delimiter Commit: https://
unread,
Commit: patch 9.1.0438: Wrong Ex command executed when :g uses '?' as delimiter
patch 9.1.0438: Wrong Ex command executed when :g uses '?' as delimiter Commit: https://
May 24
Christian Brabandt
2
May 24
[vim/vim] Cannot search the history (PR #14835)
Closed #14835 via 42a5b5a. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] Cannot search the history (PR #14835)
Closed #14835 via 42a5b5a. — Reply to this email directly, view it on GitHub. You are receiving this
May 24
zeertzjq
3
May 24
[vim/vim] Wrong Ex command executed when :g uses '?' as delimiter (PR #14837)
Closed #14837 via 3074137. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] Wrong Ex command executed when :g uses '?' as delimiter (PR #14837)
Closed #14837 via 3074137. — Reply to this email directly, view it on GitHub. You are receiving this
May 24
ElectricPulse
21
May 23
[vim/vim] Adding register viminfo partial write warning (PR #14787)
I did check the vim-history repo and the s flag (max size of registers) has been added to the viminfo
unread,
[vim/vim] Adding register viminfo partial write warning (PR #14787)
I did check the vim-history repo and the s flag (max size of registers) has been added to the viminfo
May 23
Christian Brabandt
May 23
Commit: runtime(i3config/swayconfig): support floating_modifier none; revert broken highlighting
runtime(i3config/swayconfig): support floating_modifier none; revert broken highlighting Commit:
unread,
Commit: runtime(i3config/swayconfig): support floating_modifier none; revert broken highlighting
runtime(i3config/swayconfig): support floating_modifier none; revert broken highlighting Commit:
May 23