Hi,
On Sat, Mar 28, 2020 at 5:35 PM David Barnett
wrote:
> I expected that getcompletion({pat}, 'command') would be able to complete
> the 2nd word of a command, but it doesn't seem to return any results. For
> instance:
>
> echo getcompletion('set s', 'command')
>
> returns [] instead of result
Hi Bram,
2020/3/29 Sun 4:45:18 UTC+9 Bram Moolenaar wrote:
>
>
> Ken Takata wrote:
>
> > 2020/3/28 Sat 5:09:20 UTC+9 Bram Moolenaar wrote:
> > >
> > > I wrote:
> > >
> > > > Patch 8.2.0463
> > > > Problem:Build error without float and channel feature. (John
> > > Marriott)
> > > > Solu
Patch 8.2.0472
Problem:Terminal highlight name is set twice, leaking memory.
Solution: Delete one.
Files: src/terminal.c
*** ../vim-8.2.0471/src/terminal.c 2020-03-26 20:33:20.995063766 +0100
--- src/terminal.c 2020-03-28 22:34:39.941772950 +0100
***
*** 6925,69
Patch 8.2.0471
Problem:Missing change to compile_list().
Solution: Add error message.
Files: src/vim9compile.c
*** ../vim-8.2.0470/src/vim9compile.c 2020-03-28 19:41:29.595765241 +0100
--- src/vim9compile.c 2020-03-28 21:20:42.843743402 +0100
***
*** 2173,2179
--
Patch 8.2.0470
Problem:Test_confirm_cmd_cancel() can fail on a slow system.
Solution: Use WaitForAssert(). (Ozaki Kiichi, closes #5861)
Files: src/testdir/test_excmd.vim
*** ../vim-8.2.0469/src/testdir/test_excmd.vim 2020-03-27 19:40:59.116735170
+0100
--- src/testdir/test_excmd.vi
Dominique wrote:
> Please find attached minor doc fixes for vim-8.2.468.
Thanks!
--
[SIR LAUNCELOT runs back up the stairs, grabs a rope
of the wall and swings out over the heads of the CROWD in a
swashbuckling manner towards a large window. He stops just short
of the window and
Hi
Please find attached minor doc fixes for vim-8.2.468.
Regards
Dominique
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this messa
Patch 8.2.0469
Problem:Vim9: no error for missing ] after list.
Solution: Add error message. Add more tests.
Files: src/globals.h, src/list.c, src/userfunc.c,
src/testdir/test_vim9_expr.vim, src/testdir/test_lambda.vim
*** ../vim-8.2.0468/src/globals.h 2020-03-27 20
Ken Takata wrote:
> 2020/3/28 Sat 5:09:20 UTC+9 Bram Moolenaar wrote:
> >
> > I wrote:
> >
> > > Patch 8.2.0463
> > > Problem:Build error without float and channel feature. (John
> > Marriott)
> > > Solution: Define return types always.
> > > Files: src/globals.h, src/evalfunc.c
Patch 8.2.0468
Problem:GUI: pixel dust with some fonts and characters.
Solution: Always redraw the character before the cursor. (Nir Lichtman,
closes #5549, closes #5856)
Files: src/gui.c, src/proto/gui.pro, src/screen.c
*** ../vim-8.2.0467/src/gui.c 2020-03-23 22:12:15
Patch 8.2.0467
Problem:Vim9: some errors are not tested
Solution: Add more tests. Fix that Vim9 script flag is not reset.
Files: src/vim9compile.c, src/scriptfile.c, src/dict.c,
src/testdir/test_vim9_expr.vim, src/testdir/test_vim9_script.vim
*** ../vim-8.2.0466/src/vim9
Thanks - per my response to the patch that fixes things.
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are s
Thanks - I can confirm this fixes things.
On Sat, 28 Mar 2020 at 17:07, Bram Moolenaar wrote:
>
>
> Patch 8.2.0466 (after 8.2.0452)
> Problem:Not parsing messages recursively breaks the govim plugin.
> Solution: When called recursively do handle messages but do not close
> chann
Patch 8.2.0466 (after 8.2.0452)
Problem:Not parsing messages recursively breaks the govim plugin.
Solution: When called recursively do handle messages but do not close
channels.
Files: src/channel.c
*** ../vim-8.2.0465/src/channel.c 2020-03-26 20:33:20.999063758 +01
Paul Jolly wrote:
> > It would be good to know why the recursion is needed.
>
> The canonical example is an autocommand handler in a remote plugin
> that performs some actions that trigger another autocommand that also
> has a remote handler.
>
> But we have many others.
>
> > One thing we ca
> I don't like "undefined behavior", because people will depend on it
> anyway. We could add new "BufIs" autocommands that disallow any kind of
> changes to the buffer list:
> BufIsCreated
> BufIsLoaded
> BufIsUnloaded
> BufIsWiped
>
> Do we also need events for a buffer being renamed?
>
Apologies
Hi Bram,
2020/3/28 Sat 5:09:20 UTC+9 Bram Moolenaar wrote:
>
>
> I wrote:
>
> > Patch 8.2.0463
> > Problem:Build error without float and channel feature. (John
> Marriott)
> > Solution: Define return types always.
> > Files: src/globals.h, src/evalfunc.c
>
> Somehow the git commit
> It would be good to know why the recursion is needed.
The canonical example is an autocommand handler in a remote plugin
that performs some actions that trigger another autocommand that also
has a remote handler.
But we have many others.
> One thing we can
> do is to only disallow closing chan
Patch 8.2.0465
Problem:Vim9: dead code and wrong return type.
Solution: Remove dead code. Fix return type. Add more tests.
Files: src/vim9compile.c, src/testdir/test_vim9_script.vim
*** ../vim-8.2.0464/src/vim9compile.c 2020-03-26 13:15:38.578501310 +0100
--- src/vim9compile.c
Paul Jolly wrote:
> This change has broken govim which relies on recursive calls working. I'll
> submit an issue with further details tomorrow
It would be good to know why the recursion is needed. One thing we can
do is to only disallow closing channels when called recursively.
--
The early
20 matches
Mail list logo
