Groups
Sign in
Groups
vim_dev
Conversations
About
Send feedback
Help
vim_dev
Contact owners and managers
1–30 of 41586
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
Gary Johnson
12:58 PM
[vim/vim] Left shift is incorrect with vartabstop and shiftwidth=0 (Issue #14864)
Steps to reproduce Start vim as "vim -N -u NONE -i NONE" :set vts=11,7,5 sw=0 ruler Insert
unread,
[vim/vim] Left shift is incorrect with vartabstop and shiftwidth=0 (Issue #14864)
Steps to reproduce Start vim as "vim -N -u NONE -i NONE" :set vts=11,7,5 sw=0 ruler Insert
12:58 PM
Riley Bruins
,
Ajit Thakkar
39
12:58 PM
[vim/vim] feat(runtime)!: add padding to commentstrings (PR #14843)
For liquid.vim, the tag-like nature of it makes me think it's one of the few where the space
unread,
[vim/vim] feat(runtime)!: add padding to commentstrings (PR #14843)
For liquid.vim, the tag-like nature of it makes me think it's one of the few where the space
12:58 PM
VimWei
4
12:51 PM
[vim/vim] Update syntax/markdown.vim: Don't allow space between link text and URL (Issue #14855)
That change could have a negative impact for some users, so it's not something I will be rushing
unread,
[vim/vim] Update syntax/markdown.vim: Don't allow space between link text and URL (Issue #14855)
That change could have a negative impact for some users, so it's not something I will be rushing
12:51 PM
chdiza
5
11:43 AM
[vim/vim] New compiler warnings in 9.1.444 (Issue #14847)
I don't see it with gcc-13 . and gcc-12 . Seems an issue with gcc-10 and gcc-11 then. Does the
unread,
[vim/vim] New compiler warnings in 9.1.444 (Issue #14847)
I don't see it with gcc-13 . and gcc-12 . Seems an issue with gcc-10 and gcc-11 then. Does the
11:43 AM
Christian Brabandt
11:30 AM
Commit: runtime(doc): Add ft_hare.txt to Reference Manual TOC
runtime(doc): Add ft_hare.txt to Reference Manual TOC Commit: https://github.com/vim/vim/commit/
unread,
Commit: runtime(doc): Add ft_hare.txt to Reference Manual TOC
runtime(doc): Add ft_hare.txt to Reference Manual TOC Commit: https://github.com/vim/vim/commit/
11:30 AM
Christian Brabandt
2
11:17 AM
[vim/vim] Problem: "i" in 'complete' option may slow down Vim (PR #14862)
Please note: this change may break backwards compatibility — Reply to this email directly, view it on
unread,
[vim/vim] Problem: "i" in 'complete' option may slow down Vim (PR #14862)
Please note: this change may break backwards compatibility — Reply to this email directly, view it on
11:17 AM
h_east
3
11:16 AM
[vim/vim] Add ft_hare.txt to Reference Manual TOC (PR #14863)
Closed #14863 via 0bdc5d8. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] Add ft_hare.txt to Reference Manual TOC (PR #14863)
Closed #14863 via 0bdc5d8. — Reply to this email directly, view it on GitHub. You are receiving this
11:16 AM
eldorel
2
10:48 AM
[vim/vim] Unify/simplify the config file search across OS versions. ALT: Allow all versions to honor XDG_CONFIG_HOME if set (Issue #14786)
XDG environment variables are a Linux spefic. Although on MacOS in the terminal they are use, due to
unread,
[vim/vim] Unify/simplify the config file search across OS versions. ALT: Allow all versions to honor XDG_CONFIG_HOME if set (Issue #14786)
XDG environment variables are a Linux spefic. Although on MacOS in the terminal they are use, due to
10:48 AM
Christian Brabandt
10:00 AM
Commit: runtime(vim): re-generate vim syntax from generator
runtime(vim): re-generate vim syntax from generator Commit: https://github.com/vim/vim/commit/
unread,
Commit: runtime(vim): re-generate vim syntax from generator
runtime(vim): re-generate vim syntax from generator Commit: https://github.com/vim/vim/commit/
10:00 AM
h_east
5
9:52 AM
[vim/vim] Fix syntax vim bug (Close #14858) (PR #14861)
yeah sorry, fixed now — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] Fix syntax vim bug (Close #14858) (PR #14861)
yeah sorry, fixed now — Reply to this email directly, view it on GitHub. You are receiving this
9:52 AM
Christian Brabandt
9:45 AM
Commit: runtime(vim): fix syntax vim bug (Close #14858) (#14861)
runtime(vim): fix syntax vim bug (Close #14858) (#14861) Commit: https://github.com/vim/vim/commit/
unread,
Commit: runtime(vim): fix syntax vim bug (Close #14858) (#14861)
runtime(vim): fix syntax vim bug (Close #14858) (#14861) Commit: https://github.com/vim/vim/commit/
9:45 AM
Christian Brabandt
9:45 AM
Commit: patch 9.1.0447: completion may be wrong when deleting all chars
patch 9.1.0447: completion may be wrong when deleting all chars Commit: https://github.com/vim/vim/
unread,
Commit: patch 9.1.0447: completion may be wrong when deleting all chars
patch 9.1.0447: completion may be wrong when deleting all chars Commit: https://github.com/vim/vim/
9:45 AM
matveyt
6
9:41 AM
[vim/vim] Vim syntax bug (Issue #14858)
Closed #14858 as completed via c984b2f. — Reply to this email directly, view it on GitHub. You are
unread,
[vim/vim] Vim syntax bug (Issue #14858)
Closed #14858 as completed via c984b2f. — Reply to this email directly, view it on GitHub. You are
9:41 AM
lkintact
2
9:37 AM
[vim/vim] :echo works incorrectly in gVim (Issue #14860)
echo during startup may not work, especially when starting up the GUI. You shouldn't rely on that
unread,
[vim/vim] :echo works incorrectly in gVim (Issue #14860)
echo during startup may not work, especially when starting up the GUI. You shouldn't rely on that
9:37 AM
glepnir
10
9:30 AM
[vim/vim] fix(completion): reset shown to first when leader delete to empty (PR #14854)
Closed #14854 via 53387c5. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] fix(completion): reset shown to first when leader delete to empty (PR #14854)
Closed #14854 via 53387c5. — Reply to this email directly, view it on GitHub. You are receiving this
9:30 AM
Nguyen Phu Huy
2
8:09 AM
[vim/vim] how to use Vim (Issue #14859)
Closed #14859 as not planned. — Reply to this email directly, view it on GitHub. You are receiving
unread,
[vim/vim] how to use Vim (Issue #14859)
Closed #14859 as not planned. — Reply to this email directly, view it on GitHub. You are receiving
8:09 AM
Luca Saccarola
10
6:00 AM
[vim/vim] Update defaults.vim (Issue #14853)
I don't think virtualedit=all is a good idea. Less intrusive block might be though. Anyways,
unread,
[vim/vim] Update defaults.vim (Issue #14853)
I don't think virtualedit=all is a good idea. Less intrusive block might be though. Anyways,
6:00 AM
A4-Tacks
6
5:30 AM
[vim/vim] runtime(lua): optional one expr in unamed function conceal to lambda (PR #14857)
I understand, thank you very much. — Reply to this email directly, view it on GitHub. You are
unread,
[vim/vim] runtime(lua): optional one expr in unamed function conceal to lambda (PR #14857)
I understand, thank you very much. — Reply to this email directly, view it on GitHub. You are
5:30 AM
yu3s
4
3:37 AM
[vim/vim] [''] and [{}] behave differently as repeat function parameter (Issue #14856)
Closed #14856 as completed. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] [''] and [{}] behave differently as repeat function parameter (Issue #14856)
Closed #14856 as completed. — Reply to this email directly, view it on GitHub. You are receiving this
3:37 AM
Christian Brabandt
May 26
Commit: patch 9.1.0446: getregionpos() inconsistent for partly-selected multibyte char
patch 9.1.0446: getregionpos() inconsistent for partly-selected multibyte char Commit: https://github
unread,
Commit: patch 9.1.0446: getregionpos() inconsistent for partly-selected multibyte char
patch 9.1.0446: getregionpos() inconsistent for partly-selected multibyte char Commit: https://github
May 26
zeertzjq
3
May 26
[vim/vim] getregionpos() inconsistent for partly-selected multibyte char (PR #14851)
Closed #14851 via ef73374. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] getregionpos() inconsistent for partly-selected multibyte char (PR #14851)
Closed #14851 via ef73374. — Reply to this email directly, view it on GitHub. You are receiving this
May 26
Christian Brabandt
May 26
Commit: runtime(typescriptreact): fix highlighting nested and escaped quotes in string props (#14852)
runtime(typescriptreact): fix highlighting nested and escaped quotes in string props (#14852) Commit:
unread,
Commit: runtime(typescriptreact): fix highlighting nested and escaped quotes in string props (#14852)
runtime(typescriptreact): fix highlighting nested and escaped quotes in string props (#14852) Commit:
May 26
Linda_pp
4
May 26
[vim/vim] runtime(typescriptreact): fix highlighting nested and escaped quotes in string props (PR #14852)
Merged #14852 into master. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] runtime(typescriptreact): fix highlighting nested and escaped quotes in string props (PR #14852)
Merged #14852 into master. — Reply to this email directly, view it on GitHub. You are receiving this
May 26
Christian Brabandt
May 26
Commit: runtime(asm): remove the indent plugin since it has too many issues
runtime(asm): remove the indent plugin since it has too many issues Commit: https://github.com/vim/
unread,
Commit: runtime(asm): remove the indent plugin since it has too many issues
runtime(asm): remove the indent plugin since it has too many issues Commit: https://github.com/vim/
May 26
Zachary Huang
6
May 26
[vim/vim] Remove/modify filetype indent for asm files (Issue #14791)
Closed #14791 as completed via 76174e7. — Reply to this email directly, view it on GitHub. You are
unread,
[vim/vim] Remove/modify filetype indent for asm files (Issue #14791)
Closed #14791 as completed via 76174e7. — Reply to this email directly, view it on GitHub. You are
May 26
giri
11
May 26
[vim/vim] HighlightedYank feature (Issue #14848)
Does your Vim version contain patch 9.1.0443? I made a mistake when I did 'make install'. It
unread,
[vim/vim] HighlightedYank feature (Issue #14848)
Does your Vim version contain patch 9.1.0443? I made a mistake when I did 'make install'. It
May 26
rcmosher
8
May 25
[vim/vim] listchars: trailmultispace to easily identify the number of trailing spaces (Issue #14819)
I'll add that vim includes markdownLineBreak in it's default syntax files. It matches 2 or
unread,
[vim/vim] listchars: trailmultispace to easily identify the number of trailing spaces (Issue #14819)
I'll add that vim includes markdownLineBreak in it's default syntax files. It matches 2 or
May 25
Aliaksei Budavei
7
May 25
[vim/vim] Screen dumps may omit lines for test files with lines longer than 75 columns (Issue #14245)
Here is another topic branch with a new set of proposed changes. For reviewers, a couple head-
unread,
[vim/vim] Screen dumps may omit lines for test files with lines longer than 75 columns (Issue #14245)
Here is another topic branch with a new set of proposed changes. For reviewers, a couple head-
May 25
lkintact
4
May 25
[vim/vim] No indentation of HTML tags in PHP files (Issue #14850)
Closed #14850 as completed. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] No indentation of HTML tags in PHP files (Issue #14850)
Closed #14850 as completed. — Reply to this email directly, view it on GitHub. You are receiving this
May 25
lkintact
4
May 25
[vim/vim] Some text in filetype.vim is incorrectly highlighted (Issue #14765)
Closed #14765 as not planned. — Reply to this email directly, view it on GitHub. You are receiving
unread,
[vim/vim] Some text in filetype.vim is incorrectly highlighted (Issue #14765)
Closed #14765 as not planned. — Reply to this email directly, view it on GitHub. You are receiving
May 25