Groupes
Connexion
Groupes
vim_dev
Conversations
À propos de :
Votre avis
Aide
vim_dev
Contacter les propriétaires et les gestionnaires
1 à 30 sur 41822
Vim developers maillist
For an overview of all the Vim maillists see:
http://www.vim.org/maillist.
php
Tout marquer comme lu
Signaler le groupe
0 sélectionné
zeertzjq
2
14:19
[vim/vim] Matched text shouldn't be highlighted in "kind" and "menu" (PR #14996)
thanks! — Reply to this email directly, view it on GitHub. You are receiving this because you are
non lue,
[vim/vim] Matched text shouldn't be highlighted in "kind" and "menu" (PR #14996)
thanks! — Reply to this email directly, view it on GitHub. You are receiving this because you are
14:19
dkearns
3
14:18
[vim/vim] runtime(vim): Update base-syntax, match :sleep arg (PR #15003)
Closed #15003 via 262e25e. — Reply to this email directly, view it on GitHub. You are receiving this
non lue,
[vim/vim] runtime(vim): Update base-syntax, match :sleep arg (PR #15003)
Closed #15003 via 262e25e. — Reply to this email directly, view it on GitHub. You are receiving this
14:18
Mishiko (მიშო)
3
14:15
[vim/vim] Added Georgian keymap (PR #15002)
Closed #15002 via 79a14c0. — Reply to this email directly, view it on GitHub. You are receiving this
non lue,
[vim/vim] Added Georgian keymap (PR #15002)
Closed #15002 via 79a14c0. — Reply to this email directly, view it on GitHub. You are receiving this
14:15
Christian Brabandt
14:15
Commit: runtime(keymap): include Georgian keymap
runtime(keymap): include Georgian keymap Commit: https://github.com/vim/vim/commit/
non lue,
Commit: runtime(keymap): include Georgian keymap
runtime(keymap): include Georgian keymap Commit: https://github.com/vim/vim/commit/
14:15
Christian Brabandt
14:15
Commit: patch 9.1.0484: Sorting of completeopt+=fuzzy is not stable
patch 9.1.0484: Sorting of completeopt+=fuzzy is not stable Commit: https://github.com/vim/vim/commit
non lue,
Commit: patch 9.1.0484: Sorting of completeopt+=fuzzy is not stable
patch 9.1.0484: Sorting of completeopt+=fuzzy is not stable Commit: https://github.com/vim/vim/commit
14:15
glepnir
19
14:11
[vim/vim] fix(completion): when only fuzzy no completion insert (PR #14976)
so maybe we can use a separate sub-option 'fuzzysearch' for the 'completeopt' option
non lue,
[vim/vim] fix(completion): when only fuzzy no completion insert (PR #14976)
so maybe we can use a separate sub-option 'fuzzysearch' for the 'completeopt' option
14:11
zeertzjq
10
14:06
[vim/vim] Sorting of completeopt+=fuzzy is not stable (PR #14988)
Closed #14988 via 8e56747. — Reply to this email directly, view it on GitHub. You are receiving this
non lue,
[vim/vim] Sorting of completeopt+=fuzzy is not stable (PR #14988)
Closed #14988 via 8e56747. — Reply to this email directly, view it on GitHub. You are receiving this
14:06
ubaldot
20
13:11
[vim/vim] Termdebug: added InitScriptVariables() and SanityCheck() functions, tests and refactoring. (PR #14978)
What I am saying is that the termdebug.vim included in neovim is keeping the old legacy language
non lue,
[vim/vim] Termdebug: added InitScriptVariables() and SanityCheck() functions, tests and refactoring. (PR #14978)
What I am saying is that the termdebug.vim included in neovim is keeping the old legacy language
13:11
Damien R.
15
13:07
[vim/vim] runtime(termdebug): add no_tty option to prevent creation of TTY window (PR #14997)
Thank you that worked! I've split the initial commit into two: the first one to only tackle
non lue,
[vim/vim] runtime(termdebug): add no_tty option to prevent creation of TTY window (PR #14997)
Thank you that worked! I've split the initial commit into two: the first one to only tackle
13:07
Yinzuo Jiang
24
12:10
[vim/vim] Is there a better project management method than maintaining the todo.txt? (Discussion #14974)
ok, just to be clear: no one said you cannot improve the room, or ideas, as long as it was meaningful
non lue,
[vim/vim] Is there a better project management method than maintaining the todo.txt? (Discussion #14974)
ok, just to be clear: no one said you cannot improve the room, or ideas, as long as it was meaningful
12:10
dkearns
2
12:08
[vim/vim] runtime(java): Add a config variable for commonly used compiler options (PR #14999)
@dkearns pushed 1 commit. 3203bfa runtime(java): Add a config variable for commonly used compiler
non lue,
[vim/vim] runtime(java): Add a config variable for commonly used compiler options (PR #14999)
@dkearns pushed 1 commit. 3203bfa runtime(java): Add a config variable for commonly used compiler
12:08
errael
8
10:41
[vim/vim] [termdebug vim9script] problems with saving/restoring string options (Issue #14957)
@ubaldot I think everything mentioned in here has been addressed, closing. If you want this open for
non lue,
[vim/vim] [termdebug vim9script] problems with saving/restoring string options (Issue #14957)
@ubaldot I think everything mentioned in here has been addressed, closing. If you want this open for
10:41
git-madresc
3
10:31
Re: [vim/vim] Why is ~/.vim/vimrc read before ./defaults.vim? (Discussion #15001)
I answer with a qoute: "It's (time) like a predator; it's stalking you." Looking at
non lue,
Re: [vim/vim] Why is ~/.vim/vimrc read before ./defaults.vim? (Discussion #15001)
I answer with a qoute: "It's (time) like a predator; it's stalking you." Looking at
10:31
git-madresc
3
09:40
[vim/vim] Why is ~/.vim/vimrc read before ./defaults.vim? (Issue #15000)
@chrisbra converted this issue into discussion #15001. — Reply to this email directly, view it on
non lue,
[vim/vim] Why is ~/.vim/vimrc read before ./defaults.vim? (Issue #15000)
@chrisbra converted this issue into discussion #15001. — Reply to this email directly, view it on
09:40
Lifepillar
2
08:54
[vim/vim] Popup window does not resize any longer after scrolling (Issue #14745)
If I scroll with mouse after step 4, window height increases. — Reply to this email directly, view it
non lue,
[vim/vim] Popup window does not resize any longer after scrolling (Issue #14745)
If I scroll with mouse after step 4, window height increases. — Reply to this email directly, view it
08:54
errael
5
08:41
[vim/vim] [termdebug vim9script] Problems debugging vim with vim's termdebug (Issue #14994)
Needless to say, but if you feel to spend some time to look/fix those datatypes implicit conversions
non lue,
[vim/vim] [termdebug vim9script] Problems debugging vim with vim's termdebug (Issue #14994)
Needless to say, but if you feel to spend some time to look/fix those datatypes implicit conversions
08:41
lkintact
3
05:26
[vim/vim] Zip archive explorer plugin incorrectly handles files with spaces in their names (Issue #14998)
For the plugin to work I placed unzip.exe (unzip.exe.zip) to $VIM\vimfiles and added this line to my
non lue,
[vim/vim] Zip archive explorer plugin incorrectly handles files with spaces in their names (Issue #14998)
For the plugin to work I placed unzip.exe (unzip.exe.zip) to $VIM\vimfiles and added this line to my
05:26
Christian Brabandt
02:30
Commit: runtime(netrw): correctly test for windows in NetrwGlob()
runtime(netrw): correctly test for windows in NetrwGlob() Commit: https://github.com/vim/vim/commit/
non lue,
Commit: runtime(netrw): correctly test for windows in NetrwGlob()
runtime(netrw): correctly test for windows in NetrwGlob() Commit: https://github.com/vim/vim/commit/
02:30
K.Takata
2
02:16
Re: [vim/vim] runtime(netrw): glob() on windows fails with [] in directory name (1487947)
ah yes of course. — Reply to this email directly, view it on GitHub, or unsubscribe. You are
non lue,
Re: [vim/vim] runtime(netrw): glob() on windows fails with [] in directory name (1487947)
ah yes of course. — Reply to this email directly, view it on GitHub, or unsubscribe. You are
02:16
Antoine Cotten
3
01:26
[vim/vim] statusline: Restoring a `User{N}` highlight inside an item group causes the whole item group to disappear (Issue #14993)
@zeertzjq correct, this is intentional and documented in the help section for 'statusline'.
non lue,
[vim/vim] statusline: Restoring a `User{N}` highlight inside an item group causes the whole item group to disappear (Issue #14993)
@zeertzjq correct, this is intentional and documented in the help section for 'statusline'.
01:26
Riley Bruins
4
13 juin
[vim/vim] filetype: snakemake files not recognized (PR #14992)
@ribru17 commented on this pull request. In runtime/filetype.vim: > @@ -2243,6 +2243,9 @@ au
non lue,
[vim/vim] filetype: snakemake files not recognized (PR #14992)
@ribru17 commented on this pull request. In runtime/filetype.vim: > @@ -2243,6 +2243,9 @@ au
13 juin
Gary Johnson
3
13 juin
[vim/vim] Right shifts move text to wrong columns when using 'vartabstop' and 'shiftwidth' is 0 (Issue #14891)
Since it's been over a week, here's an update. I wrote tests to cover every shift command and
non lue,
[vim/vim] Right shifts move text to wrong columns when using 'vartabstop' and 'shiftwidth' is 0 (Issue #14891)
Since it's been over a week, here's an update. I wrote tests to cover every shift command and
13 juin
Peter Wu
3
13 juin
[vim/vim] add OSC 52 clipboard support (Issue #14995)
For completeness, this is the PR where Neovim repurposed TermReponse . neovim/neovim#25868 — Reply to
non lue,
[vim/vim] add OSC 52 clipboard support (Issue #14995)
For completeness, this is the PR where Neovim repurposed TermReponse . neovim/neovim#25868 — Reply to
13 juin
eldorel
3
13 juin
[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
non lue,
[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
13 juin
Christian Brabandt
13 juin
Commit: runtime(doc): rewrite mkdir() doc and simplify {flags} meaning
runtime(doc): rewrite mkdir() doc and simplify {flags} meaning Commit: https://github.com/vim/vim/
non lue,
Commit: runtime(doc): rewrite mkdir() doc and simplify {flags} meaning
runtime(doc): rewrite mkdir() doc and simplify {flags} meaning Commit: https://github.com/vim/vim/
13 juin
Christian Brabandt
13 juin
Commit: runtime(netrw): glob() on windows fails with [] in directory name
runtime(netrw): glob() on windows fails with [] in directory name Commit: https://github.com/vim/vim/
non lue,
Commit: runtime(netrw): glob() on windows fails with [] in directory name
runtime(netrw): glob() on windows fails with [] in directory name Commit: https://github.com/vim/vim/
13 juin
Christian Brabandt
13 juin
Commit: patch 9.1.0483: glob() not sufficiently tested
patch 9.1.0483: glob() not sufficiently tested Commit: https://github.com/vim/vim/commit/
non lue,
Commit: patch 9.1.0483: glob() not sufficiently tested
patch 9.1.0483: glob() not sufficiently tested Commit: https://github.com/vim/vim/commit/
13 juin
lkintact
8
13 juin
[vim/vim] Netrw incorrectly handles folders containing [] in their names (Issue #14952)
Closed #14952 as completed via 1487947. — Reply to this email directly, view it on GitHub. You are
non lue,
[vim/vim] Netrw incorrectly handles folders containing [] in their names (Issue #14952)
Closed #14952 as completed via 1487947. — Reply to this email directly, view it on GitHub. You are
13 juin
Christian Brabandt
4
13 juin
[vim/vim] Problem: glob() not sufficiently tested (PR #14991)
Closed #14991 via 1487947. — Reply to this email directly, view it on GitHub. You are receiving this
non lue,
[vim/vim] Problem: glob() not sufficiently tested (PR #14991)
Closed #14991 via 1487947. — Reply to this email directly, view it on GitHub. You are receiving this
13 juin
Christian Brabandt
13 juin
Commit: runtime(doc): update return type for job_info()
runtime(doc): update return type for job_info() Commit: https://github.com/vim/vim/commit/
non lue,
Commit: runtime(doc): update return type for job_info()
runtime(doc): update return type for job_info() Commit: https://github.com/vim/vim/commit/
13 juin