Grupos
Iniciar sesión
Grupos
vim_dev
Conversaciones
Información
Enviar comentarios
Ayuda
vim_dev
Contactar con los propietarios y administradores
1-30 de 41791
Vim developers maillist
For an overview of all the Vim maillists see:
http://www.vim.org/maillist.
php
Marcar todo como leído
Denunciar grupo
0 grupos seleccionados
ubaldot
12
10:08
[vim/vim] Termdebug: added InitScriptVariables() and SanityCheck() functions, tests and refactoring. (PR #14978)
it is the problem now, the experience was different or buggy (you should notice some tickets had been
no leída,
[vim/vim] Termdebug: added InitScriptVariables() and SanityCheck() functions, tests and refactoring. (PR #14978)
it is the problem now, the experience was different or buggy (you should notice some tickets had been
10:08
ubaldot
19
9:48
[vim/vim] Added InitScriptVariables() function, refactor & bugfix. (PR #14980)
@errael commented on this pull request. In runtime/pack/dist/opt/termdebug/plugin/termdebug.vim: >
no leída,
[vim/vim] Added InitScriptVariables() function, refactor & bugfix. (PR #14980)
@errael commented on this pull request. In runtime/pack/dist/opt/termdebug/plugin/termdebug.vim: >
9:48
glepnir
10
9:38
[vim/vim] fix(completion): when only fuzzy no completion insert (PR #14976)
@glepnir pushed 1 commit. d0806b2 fix(completion): when only fuzzy no completion insert — View it on
no leída,
[vim/vim] fix(completion): when only fuzzy no completion insert (PR #14976)
@glepnir pushed 1 commit. d0806b2 fix(completion): when only fuzzy no completion insert — View it on
9:38
errael
3
9:22
[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
no leída,
[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
dkearns
2
9:02
[vim/vim] runtime(vim): Update base-syntax, match :catch and :throw args (PR #14989)
@dkearns pushed 1 commit. c5d2880 runtime(vim): Update base-syntax, match :catch and :throw args —
no leída,
[vim/vim] runtime(vim): Update base-syntax, match :catch and :throw args (PR #14989)
@dkearns pushed 1 commit. c5d2880 runtime(vim): Update base-syntax, match :catch and :throw args —
9:02
dkearns
9
8:40
[vim/vim] runtime(html): Fix syntax test failures (PR #13595)
@dkearns pushed 1 commit. 8ab85bb runtime(html): Fix syntax test failures — View it on GitHub or
no leída,
[vim/vim] runtime(html): Fix syntax test failures (PR #13595)
@dkearns pushed 1 commit. 8ab85bb runtime(html): Fix syntax test failures — View it on GitHub or
8:40
lkintact
7
8:30
[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
no leída,
[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
Yinzuo Jiang
17
6:58
[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
no leída,
[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
errael
4
6:46
[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
no leída,
[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
AMF064
13
6:44
[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
no leída,
[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
lkintact
6
6:42
[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
no leída,
[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
zeertzjq
2
6: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
no leída,
[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
6:24
zeertzjq
5: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
no leída,
[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
glepnir
3
5: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
no leída,
[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
zeertzjq
4
5: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
no leída,
[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
Xcess
18
3: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 (
no leída,
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
Yegappan Lakshmanan
,
Yegappan Lakshmanan
23
3: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`
no leída,
[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
Sami Farin
4
3: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
no leída,
[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
errael
2
1: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
no leída,
[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
1:37
errael
2
0: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
no leída,
[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
0:42
Ali Rizvi-Santiago
16
12 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,
no leída,
[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 jun
Ernie Rael
12 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
no leída,
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 jun
Maxim Kim
3
12 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
no leída,
[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 jun
zeertzjq
4
12 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
no leída,
[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 jun
Aliaksei Budavei
12 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
no leída,
[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 jun
Christian Brabandt
12 jun
Commit: runtime(doc): deduplicate getpos(), line(), col(), virtcol()
runtime(doc): deduplicate getpos(), line(), col(), virtcol() Commit: https://github.com/vim/vim/
no leída,
Commit: runtime(doc): deduplicate getpos(), line(), col(), virtcol()
runtime(doc): deduplicate getpos(), line(), col(), virtcol() Commit: https://github.com/vim/vim/
12 jun
Ernie Rael
,
Christian Brabandt
3
12 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: > >
no leída,
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 jun
zeertzjq
3
12 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
no leída,
[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 jun
dkearns
3
12 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
no leída,
[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 jun
Christian Brabandt
12 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/
no leída,
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 jun