Patch 8.2.1923
Problem:Vim9: "filter" command modifier doesn't work.
Solution: Check for space on char before argument. (closes #7216,
closes #7222)
Files: src/ex_docmd.c, src/testdir/test_vim9_cmd.vim
*** ../vim-8.2.1922/src/ex_docmd.c 2020-10-28 13:53:46.549128959
Patch 8.2.1922
Problem:Win32: scrolling doesn't work properly when part of window is
off-screen.
Solution: Fall back to GDI scrolling if part of the window is off-screen.
Handle multi-monitor setup better. (Ken Takata, closes #7219)
Files: src/gui_w32.c
*** ..
Marius Gedminas wrote:
> On Wed, Oct 28, 2020 at 11:32:42AM +0100, Bram Moolenaar wrote:
> > Brennan Vincent wrote:
> >
> > > Let's simulate a read that will block forever:
> > >
> > > $ mkfifo /tmp/myfifo
> > > $ vim /tmp/myfifo
> > >
> > > Now vim hangs permanently; it cannot be killed or s
Patch 8.2.1921
Problem:Fuzzy matching does not recognize path separators.
Solution: Add a bonus for slash and backslash. (Yegappan Lakshmanan,
closes #7225)
Files: src/search.c, src/testdir/test_matchfuzzy.vim
*** ../vim-8.2.1920/src/search.c2020-10-24 20:49:37.50
>
>
> I have created PR #7225 to add an additional bonus for matches after a
> path separator.
>
> Thank you!
--
--
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/mailli
Hi,
On Thu, Oct 29, 2020 at 12:38 AM Maxim Kim wrote:
>
> Hi, I am not sure that words after _ should have higher scoring than words
> after / or \:
>
> https://i.imgur.com/bjb45g3.png
>
> What do you think?
>
> Min repro:
>
> echo ["plugin/setup.vim", "plugin/color_setup.vim",
> "after/plugin/s
Hi, I am not sure that words after _ should have higher scoring than words
after / or \:
https://i.imgur.com/bjb45g3.png
What do you think?
Min repro:
echo ["plugin/setup.vim", "plugin/color_setup.vim",
"after/plugin/setup.vim"]->matchfuzzy("setup")
--
--
You received this message from th
>
> What do you think about extending this to support fuzzy matching?
> We can add a value to the 'wildoptions' option (e.g. 'fuzzymatch') to
> enable fuzzy matching instead of regular expression matching
> for builtin commands.
>
>
Would love to have it.
--
--
You received this message from