Grupos
Fazer login
Grupos
vim_dev
Conversas
Sobre
Enviar feedback
Ajuda
vim_dev
Entrar em contato com proprietários e gerentes
1 a 30 de 41790
Vim developers maillist
For an overview of all the Vim maillists see:
http://www.vim.org/maillist.
php
Marcar tudo como lido
Denunciar grupo
0 selecionadas
zeertzjq
2
06:24
[vim/vim] fuzzy_match_str_with_pos() does unnecessary list operations (PR #14987)
@zeertzjq pushed 1 commit. bc4f2fe fuzzy_match_str_with_pos() does unnecessary list operations — View
não lida,
[vim/vim] fuzzy_match_str_with_pos() does unnecessary list operations (PR #14987)
@zeertzjq pushed 1 commit. bc4f2fe fuzzy_match_str_with_pos() does unnecessary list operations — View
06:24
zeertzjq
05:33
[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
não lida,
[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
05:33
glepnir
3
05:30
[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
não lida,
[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
05:30
zeertzjq
4
05:08
[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
não lida,
[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
05:08
Yinzuo Jiang
16
04:36
[vim/vim] Is there a better project management method than maintaining the todo.txt? (Discussion #14974)
> * easy to integrate with gen AI no, it is a "joke" :sweat_smile: // as @yegappan had
não lida,
[vim/vim] Is there a better project management method than maintaining the todo.txt? (Discussion #14974)
> * easy to integrate with gen AI no, it is a "joke" :sweat_smile: // as @yegappan had
04:36
ubaldot
16
03:59
[vim/vim] Added InitScriptVariables() function, refactor & bugfix. (PR #14980)
Is it worth mentioning specifically what bug is fixed by this PR? Line 1770: there where a leftover
não lida,
[vim/vim] Added InitScriptVariables() function, refactor & bugfix. (PR #14980)
Is it worth mentioning specifically what bug is fixed by this PR? Line 1770: there where a leftover
03:59
Xcess
18
03:34
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 (
não lida,
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 (
03:34
ubaldot
8
03:22
[vim/vim] Termdebug: added InitScriptVariables() and SanityCheck() functions, tests and refactoring. (PR #14978)
@Shane-XB-Qian Out of curiosity: does vim9 implies different colorschema? Furthermore, what
não lida,
[vim/vim] Termdebug: added InitScriptVariables() and SanityCheck() functions, tests and refactoring. (PR #14978)
@Shane-XB-Qian Out of curiosity: does vim9 implies different colorschema? Furthermore, what
03:22
Yegappan Lakshmanan
,
Yegappan Lakshmanan
23
03:20
[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`
não lida,
[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`
03:20
Sami Farin
4
03:17
[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
não lida,
[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
03:17
AMF064
11
02:53
[vim/vim] :make does not add entries to the quickfix list or the location list (Issue #14967)
I mean the various shell options in Vim. See :h 'shell' and the following options. — Reply to
não lida,
[vim/vim] :make does not add entries to the quickfix list or the location list (Issue #14967)
I mean the various shell options in Vim. See :h 'shell' and the following options. — Reply to
02:53
glepnir
4
02:20
[vim/vim] fix(completion): when only fuzzy no completion insert (PR #14976)
removing edit on get_normal_compl_info will fix the problem of keyword not being completed when
não lida,
[vim/vim] fix(completion): when only fuzzy no completion insert (PR #14976)
removing edit on get_normal_compl_info will fix the problem of keyword not being completed when
02:20
errael
2
01:37
[vim/vim] If vim9script, return null_job from term_getjob when there is no job. (PR #14984)
@errael pushed 1 commit. 7e5b277 If vim9script, return null_job from term_getjob when there is no job
não lida,
[vim/vim] If vim9script, return null_job from term_getjob when there is no job. (PR #14984)
@errael pushed 1 commit. 7e5b277 If vim9script, return null_job from term_getjob when there is no job
01:37
errael
00:46
[vim/vim] Have job_status handle `null` arg in addition to `null_job` arg. (PR #14983)
This feels like a minor cleanup. With this PR you can pass a null to job_status You can view, comment
não lida,
[vim/vim] Have job_status handle `null` arg in addition to `null_job` arg. (PR #14983)
This feels like a minor cleanup. With this PR you can pass a null to job_status You can view, comment
00:46
errael
2
00:42
[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
não lida,
[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
00:42
Ali Rizvi-Santiago
16
12 de jun.
[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,
não lida,
[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,
12 de jun.
Ernie Rael
12 de jun.
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
não lida,
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
12 de jun.
Maxim Kim
3
12 de jun.
[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
não lida,
[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
12 de jun.
lkintact
4
12 de jun.
[vim/vim] Netrw incorrectly handles folders containing [] in their names (Issue #14952)
So while I was there, I went down the rabbit hole and the following patch fixed glob() behaviour on
não lida,
[vim/vim] Netrw incorrectly handles folders containing [] in their names (Issue #14952)
So while I was there, I went down the rabbit hole and the following patch fixed glob() behaviour on
12 de jun.
zeertzjq
4
12 de jun.
[vim/vim] runtime(doc): restore description of "$" in col() and virtcol() (PR #14981)
@zeertzjq pushed 1 commit. c91cb09 runtime(doc): restore description of "$" in col() and
não lida,
[vim/vim] runtime(doc): restore description of "$" in col() and virtcol() (PR #14981)
@zeertzjq pushed 1 commit. c91cb09 runtime(doc): restore description of "$" in col() and
12 de jun.
dkearns
7
12 de jun.
[vim/vim] runtime(html): Fix syntax test failures (PR #13595)
A similar problem was encountered for a Markdown syntax test file during the merge effort for #14215.
não lida,
[vim/vim] runtime(html): Fix syntax test failures (PR #13595)
A similar problem was encountered for a Markdown syntax test file during the merge effort for #14215.
12 de jun.
errael
3
12 de jun.
[vim/vim] test_override('defcompile', 1) gives lots of false errors (Issue #14969)
what happens, is that test_override('defcompile', 1) causes your function to be compiled
não lida,
[vim/vim] test_override('defcompile', 1) gives lots of false errors (Issue #14969)
what happens, is that test_override('defcompile', 1) causes your function to be compiled
12 de jun.
Aliaksei Budavei
12 de jun.
[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
não lida,
[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
12 de jun.
Christian Brabandt
12 de jun.
Commit: runtime(doc): deduplicate getpos(), line(), col(), virtcol()
runtime(doc): deduplicate getpos(), line(), col(), virtcol() Commit: https://github.com/vim/vim/
não lida,
Commit: runtime(doc): deduplicate getpos(), line(), col(), virtcol()
runtime(doc): deduplicate getpos(), line(), col(), virtcol() Commit: https://github.com/vim/vim/
12 de jun.
Ernie Rael
,
Christian Brabandt
3
12 de jun.
How to use the old termdebug
On 24/06/12 11:59 AM, Christian Brabandt wrote: > On Mi, 12 Jun 2024, Ernie Rael wrote: > >
não lida,
How to use the old termdebug
On 24/06/12 11:59 AM, Christian Brabandt wrote: > On Mi, 12 Jun 2024, Ernie Rael wrote: > >
12 de jun.
zeertzjq
3
12 de jun.
[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
não lida,
[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
12 de jun.
dkearns
3
12 de jun.
[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
não lida,
[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
12 de jun.
Christian Brabandt
12 de jun.
Commit: runtime(vim): Update g:vimsyn_comment_strings dump file tests
runtime(vim): Update g:vimsyn_comment_strings dump file tests Commit: https://github.com/vim/vim/
não lida,
Commit: runtime(vim): Update g:vimsyn_comment_strings dump file tests
runtime(vim): Update g:vimsyn_comment_strings dump file tests Commit: https://github.com/vim/vim/
12 de jun.
Christian Brabandt
12 de jun.
Commit: runtime(termdebug): Use string interpolation instead of string concat
runtime(termdebug): Use string interpolation instead of string concat Commit: https://github.com/vim/
não lida,
Commit: runtime(termdebug): Use string interpolation instead of string concat
runtime(termdebug): Use string interpolation instead of string concat Commit: https://github.com/vim/
12 de jun.
Christian Brabandt
12 de jun.
Commit: patch 9.1.0478: potential deref of NULL pointer in fuzzy_match_str_with_pos
patch 9.1.0478: potential deref of NULL pointer in fuzzy_match_str_with_pos Commit: https://github.
não lida,
Commit: patch 9.1.0478: potential deref of NULL pointer in fuzzy_match_str_with_pos
patch 9.1.0478: potential deref of NULL pointer in fuzzy_match_str_with_pos Commit: https://github.
12 de jun.