Re: [vim/vim] Fuzzy completion doesn't work properly for Ex commands (PR #9843)

2022-02-26 Fir de Conversatie Yegappan Lakshmanan
Hi, On Sat, Feb 26, 2022 at 9:24 PM Shane-XB-Qian wrote: > one left curious question: why :killkill would not expand to > :KillKillKill? :-) > > > This is a bug. Internally, if a command starts with 'k' and is followed by any character other than 'e', then it is treated as the 'k' command. This

Minor update to the quickfix.txt help file

2022-02-26 Fir de Conversatie Yegappan Lakshmanan
Hi, I am attaching a patch to the quickfix.txt file to update the steps used to find a window when an entry is selected from the quickfix window or a location list window. - Yegappan -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text yo

vim9script: =Function() in a mapping fails to work

2022-02-26 Fir de Conversatie Christian J. Robinson
Source the attached script to see the error. If I prefix Function() with it does work. Is this correct behavior? -- Christian J. Robinson -- -- 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, v

Patch 8.2.4478

2022-02-26 Fir de Conversatie Bram Moolenaar
Patch 8.2.4478 Problem:Crash when using fuzzy completion. Solution: Temporary fix: put back regexp. (closes #9852, closes #9851) Files: src/cmdexpand.c, src/testdir/test_cmdline.vim *** ../vim-8.2.4477/src/cmdexpand.c 2022-02-26 15:52:04.744494083 + --- src/cmdexpand.c 20

Patch 8.2.4477

2022-02-26 Fir de Conversatie Bram Moolenaar
Patch 8.2.4477 Problem:Crash when using fuzzy completion. Solution: Temporary fix: put back regexp. (closes #9851) Files: src/cmdexpand.c *** ../vim-8.2.4476/src/cmdexpand.c 2022-02-26 11:04:39.090453026 + --- src/cmdexpand.c 2022-02-26 15:11:27.222716003 + **

Re: [vim/vim] Fuzzy completion doesn't work properly for Ex commands (PR #9843)

2022-02-26 Fir de Conversatie Bram Moolenaar
> thx, the 'case' looks fine now. > but if the input was heading with num e.g '2bar', then looks the num > was treated as the 'range' of cmd 'bar', and doing the expanding of > 'bar' i do not know how to workaround it or it just should > be like that or it was a flaw? Well, a number

Re: [vim/vim] Fuzzy completion doesn't work properly for Ex commands (PR #9843)

2022-02-26 Fir de Conversatie Yegappan Lakshmanan
Hi, On Sat, Feb 26, 2022 at 4:43 AM Shane-XB-Qian wrote: > and i opened a another ticket #9851 > seg fault if set fuzzy > > > Thanks for testing and reporting the issue. This should be addressed by https://github.com/vim/vim/pull/9852. Regards, Yegappan

Patch 8.2.4476

2022-02-26 Fir de Conversatie Bram Moolenaar
Patch 8.2.4476 Problem:Operator name spelled wrong. Solution: Change trinary to ternary. (Goc Dundar, closes #9850) Files: src/testdir/test_expr.vim, src/testdir/test_vim9_expr.vim, src/testdir/test_vimscript.vim *** ../vim-8.2.4475/src/testdir/test_expr.vim 2022-02-13

Patch 8.2.4475

2022-02-26 Fir de Conversatie Bram Moolenaar
Patch 8.2.4475 Problem:Fuzzy cmdline completion does not work for lower case. Solution: Also use fuzzy completion for lower case input. (Yegappan Lakshmanan, closes #9849) Files: src/cmdexpand.c, src/testdir/test_cmdline.vim *** ../vim-8.2.4474/src/cmdexpand.c 2022-02

Patch 8.2.4474

2022-02-26 Fir de Conversatie Bram Moolenaar
Patch 8.2.4474 Problem:Memory allocation failures not tested in quickfix code. Solution: Add alloc IDs and tests. (Yegappan Lakshmanan, closes #9848) Files: src/alloc.h, src/quickfix.c, src/vim.h, src/testdir/test_quickfix.vim *** ../vim-8.2.4473/src/alloc.h 2018-12-21 13