Groups
Sign in
Groups
vim_dev
Conversations
About
Send feedback
Help
vim_dev
Contact owners and managers
1–30 of 41792
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
zeertzjq
4
11:16 AM
[vim/vim] fuzzy_match_str_with_pos() does unnecessary list operations (PR #14987)
Closed #14987 via 2f95ca9. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] fuzzy_match_str_with_pos() does unnecessary list operations (PR #14987)
Closed #14987 via 2f95ca9. — Reply to this email directly, view it on GitHub. You are receiving this
11:16 AM
Christian Brabandt
11:15 AM
Commit: runtime(doc): restore description of "$" in col() and virtcol() (#14981)
runtime(doc): restore description of "$" in col() and virtcol() (#14981) Commit: https://
unread,
Commit: runtime(doc): restore description of "$" in col() and virtcol() (#14981)
runtime(doc): restore description of "$" in col() and virtcol() (#14981) Commit: https://
11:15 AM
ubaldot
30
11:12 AM
[vim/vim] Added InitScriptVariables() function, refactor & bugfix. (PR #14980)
@ubaldot commented on this pull request. In runtime/pack/dist/opt/termdebug/plugin/termdebug.vim:
unread,
[vim/vim] Added InitScriptVariables() function, refactor & bugfix. (PR #14980)
@ubaldot commented on this pull request. In runtime/pack/dist/opt/termdebug/plugin/termdebug.vim:
11:12 AM
glepnir
12
11:10 AM
[vim/vim] fix(completion): when only fuzzy no completion insert (PR #14976)
@chrisbra commented on this pull request. In src/insexpand.c: > @@ -4606,11 +4611,38 @@
unread,
[vim/vim] fix(completion): when only fuzzy no completion insert (PR #14976)
@chrisbra commented on this pull request. In src/insexpand.c: > @@ -4606,11 +4611,38 @@
11:10 AM
dkearns
10
11:04 AM
[vim/vim] runtime(html): Fix syntax test failures (PR #13595)
yes, we could try out, if it still breaks (hopefully not 🤞 ) — Reply to this email directly, view it
unread,
[vim/vim] runtime(html): Fix syntax test failures (PR #13595)
yes, we could try out, if it still breaks (hopefully not 🤞 ) — Reply to this email directly, view it
11:04 AM
errael
3
11:02 AM
[vim/vim] If vim9script, return null_job from term_getjob when there is no job. (PR #14984)
Thanks. I think this makes sense. @yegappan ? — Reply to this email directly, view it on GitHub. You
unread,
[vim/vim] If vim9script, return null_job from term_getjob when there is no job. (PR #14984)
Thanks. I think this makes sense. @yegappan ? — Reply to this email directly, view it on GitHub. You
11:02 AM
zeertzjq
6
11:01 AM
[vim/vim] runtime(doc): restore description of "$" in col() and virtcol() (PR #14981)
Merged #14981 into master. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] runtime(doc): restore description of "$" in col() and virtcol() (PR #14981)
Merged #14981 into master. — Reply to this email directly, view it on GitHub. You are receiving this
11:01 AM
dkearns
3
10:59 AM
[vim/vim] runtime(vim): Update base-syntax, match :catch and :throw args (PR #14989)
@chrisbra commented on this pull request. In runtime/syntax/generator/vim.vim.base: > @@ -206,6 +
unread,
[vim/vim] runtime(vim): Update base-syntax, match :catch and :throw args (PR #14989)
@chrisbra commented on this pull request. In runtime/syntax/generator/vim.vim.base: > @@ -206,6 +
10:59 AM
ubaldot
15
10:58 AM
[vim/vim] Termdebug: added InitScriptVariables() and SanityCheck() functions, tests and refactoring. (PR #14978)
> > if the user experience is different > > But it isn't (or shouldn't). ok,
unread,
[vim/vim] Termdebug: added InitScriptVariables() and SanityCheck() functions, tests and refactoring. (PR #14978)
> > if the user experience is different > > But it isn't (or shouldn't). ok,
10:58 AM
errael
3
9:22 AM
[vim/vim] Have job_status handle `null` arg in addition to `null_job` arg. (PR #14983)
With #14984 this is not needed. — Reply to this email directly, view it on GitHub. You are receiving
unread,
[vim/vim] Have job_status handle `null` arg in addition to `null_job` arg. (PR #14983)
With #14984 this is not needed. — Reply to this email directly, view it on GitHub. You are receiving
9:22 AM
lkintact
7
8:30 AM
[vim/vim] Netrw incorrectly handles folders containing [] in their names (Issue #14952)
Yes, that's because it doesn't use globbing to get the contents of the directory. — Reply to
unread,
[vim/vim] Netrw incorrectly handles folders containing [] in their names (Issue #14952)
Yes, that's because it doesn't use globbing to get the contents of the directory. — Reply to
8:30 AM
Yinzuo Jiang
17
6:58 AM
[vim/vim] Is there a better project management method than maintaining the todo.txt? (Discussion #14974)
Should we adopt better project management methods based on the functionalities of GitHub? I think
unread,
[vim/vim] Is there a better project management method than maintaining the todo.txt? (Discussion #14974)
Should we adopt better project management methods based on the functionalities of GitHub? I think
6:58 AM
errael
4
6:46 AM
[vim/vim] test_override('defcompile', 1) gives lots of false errors (Issue #14969)
Yes. Now if only test_override would do that too. In that case, I guess we should make it try to
unread,
[vim/vim] test_override('defcompile', 1) gives lots of false errors (Issue #14969)
Yes. Now if only test_override would do that too. In that case, I guess we should make it try to
6:46 AM
AMF064
13
6:44 AM
[vim/vim] :make does not add entries to the quickfix list or the location list (Issue #14967)
Hm, we have some special casing for zsh and bash I believe. I have never heard of oksh, not sure if
unread,
[vim/vim] :make does not add entries to the quickfix list or the location list (Issue #14967)
Hm, we have some special casing for zsh and bash I believe. I have never heard of oksh, not sure if
6:44 AM
lkintact
6
6:42 AM
[vim/vim] :echo works incorrectly in gVim (Issue #14860)
let's close it then. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] :echo works incorrectly in gVim (Issue #14860)
let's close it then. — Reply to this email directly, view it on GitHub. You are receiving this
6:42 AM
zeertzjq
5:33 AM
[vim/vim] Sorting of completeopt+=fuzzy is not stable (PR #14988)
Problem: Sorting of completeopt+=fuzzy is not stable. Solution: Compare original indexes when scores
unread,
[vim/vim] Sorting of completeopt+=fuzzy is not stable (PR #14988)
Problem: Sorting of completeopt+=fuzzy is not stable. Solution: Compare original indexes when scores
5:33 AM
glepnir
3
5:30 AM
[vim/vim] fix(completion): when no leader no need run fuzzy logic (PR #14986)
@glepnir pushed 1 commit. d11ba93 fix(completion): when no leader no need run fuzzy logic — View it
unread,
[vim/vim] fix(completion): when no leader no need run fuzzy logic (PR #14986)
@glepnir pushed 1 commit. d11ba93 fix(completion): when no leader no need run fuzzy logic — View it
5:30 AM
zeertzjq
4
5:08 AM
[vim/vim] fuzzy_match_str_with_pos() may leak memory on failure (PR #14985)
Closed #14985. — Reply to this email directly, view it on GitHub. You are receiving this because you
unread,
[vim/vim] fuzzy_match_str_with_pos() may leak memory on failure (PR #14985)
Closed #14985. — Reply to this email directly, view it on GitHub. You are receiving this because you
5:08 AM
Xcess
18
3:34 AM
Re: [vim/vim] Please add BiDi support to Vim (#204)
Newlines are hidden characters and they can be searched via regex. Newlines are slightly different (
unread,
Re: [vim/vim] Please add BiDi support to Vim (#204)
Newlines are hidden characters and they can be searched via regex. Newlines are slightly different (
3:34 AM
Yegappan Lakshmanan
,
Yegappan Lakshmanan
23
3:20 AM
[vim/vim] Fix errors in using the latest termdebug.vim (PR #14941)
@chrisbra could we keep the legacy version of termdebug, which like coloschema, eg `foo` vs `foo_256`
unread,
[vim/vim] Fix errors in using the latest termdebug.vim (PR #14941)
@chrisbra could we keep the legacy version of termdebug, which like coloschema, eg `foo` vs `foo_256`
3:20 AM
Sami Farin
4
3:17 AM
[vim/vim] buf_write does not properly handle non-US-ASCII filename extension (Issue #14948)
Note: vim manages to write the file eventually, but the filename handling should be fixed anyways. So
unread,
[vim/vim] buf_write does not properly handle non-US-ASCII filename extension (Issue #14948)
Note: vim manages to write the file eventually, but the filename handling should be fixed anyways. So
3:17 AM
errael
2
12:42 AM
[vim/vim] Some wrong return types specified in help (Issue #14982)
Oh, I just came across Return type: |vim9-boolean| for something. So for job_stop ? — Reply to this
unread,
[vim/vim] Some wrong return types specified in help (Issue #14982)
Oh, I just came across Return type: |vim9-boolean| for something. So for job_stop ? — Reply to this
12:42 AM
Ali Rizvi-Santiago
16
Jun 12
[vim/vim] E342, unsigned integer underflow in op_change when in visual-block mode (Issue #14960)
no problem. thanks for continuous maintainenance of this editor. :) — Reply to this email directly,
unread,
[vim/vim] E342, unsigned integer underflow in op_change when in visual-block mode (Issue #14960)
no problem. thanks for continuous maintainenance of this editor. :) — Reply to this email directly,
Jun 12
Ernie Rael
Jun 12
Is there an alternative to "execute 'buffer' this.bufnr"
I was looking for a function that could be used instead of execute 'buffer' this.bufnr Is
unread,
Is there an alternative to "execute 'buffer' this.bufnr"
I was looking for a function that could be used instead of execute 'buffer' this.bufnr Is
Jun 12
Maxim Kim
3
Jun 12
[vim/vim] PMenuMatch has no effect for initial list of candidates (Issue #14968)
Closed #14968 as completed. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] PMenuMatch has no effect for initial list of candidates (Issue #14968)
Closed #14968 as completed. — Reply to this email directly, view it on GitHub. You are receiving this
Jun 12
Aliaksei Budavei
Jun 12
[vim/vim] runtime(java): Include element values in non-marker annotations (PR #14979)
Make a formal definition for normal and single-element kinds of annotations that otherwise require
unread,
[vim/vim] runtime(java): Include element values in non-marker annotations (PR #14979)
Make a formal definition for normal and single-element kinds of annotations that otherwise require
Jun 12
Christian Brabandt
Jun 12
Commit: runtime(doc): deduplicate getpos(), line(), col(), virtcol()
runtime(doc): deduplicate getpos(), line(), col(), virtcol() Commit: https://github.com/vim/vim/
unread,
Commit: runtime(doc): deduplicate getpos(), line(), col(), virtcol()
runtime(doc): deduplicate getpos(), line(), col(), virtcol() Commit: https://github.com/vim/vim/
Jun 12
Ernie Rael
,
Christian Brabandt
3
Jun 12
How to use the old termdebug
On 24/06/12 11:59 AM, Christian Brabandt wrote: > On Mi, 12 Jun 2024, Ernie Rael wrote: > >
unread,
How to use the old termdebug
On 24/06/12 11:59 AM, Christian Brabandt wrote: > On Mi, 12 Jun 2024, Ernie Rael wrote: > >
Jun 12
zeertzjq
3
Jun 12
[vim/vim] runtime(doc): deduplicate getpos(), line(), col(), virtcol() (PR #14970)
Closed #14970 via 02f3eba. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] runtime(doc): deduplicate getpos(), line(), col(), virtcol() (PR #14970)
Closed #14970 via 02f3eba. — Reply to this email directly, view it on GitHub. You are receiving this
Jun 12
dkearns
3
Jun 12
[vim/vim] runtime(vim): Update g:vimsyn_comment_string dump file tests (PR #14971)
Closed #14971 via 31441d5. — Reply to this email directly, view it on GitHub. You are receiving this
unread,
[vim/vim] runtime(vim): Update g:vimsyn_comment_string dump file tests (PR #14971)
Closed #14971 via 31441d5. — Reply to this email directly, view it on GitHub. You are receiving this
Jun 12