Hi,
2020/2/22 Sat 6:39:30 UTC+9 John Marriott wrote:
>
> Hi All,
>
> I have just applied a bunch of patches to my HP-UX (non-gui) build to
> bring it up to 8.2.0292 and noticed that the message that is displayed when
> a buffer is written isn't right.
>
> For example (note the number of chars)
Hi All,
I have just applied a bunch of patches to my HP-UX (non-gui) build
to bring it up to 8.2.0292 and noticed that the message that is
displayed when a buffer is written isn't right.
For example (note the number of chars):
My Win
Hi All,
I have just applied a bunch of patches to my HP-UX (non-gui) build to
bring it up to 8.2.0292 and noticed that the message that is displayed
when a buffer is written isn't right.
For example (note the number of chars):
My Win64 build looks ok:
Here is output of ':ver' of the HP-UX
Patch 8.2.0295
Problem:Highlighting for :s wrong when using different separator.
Solution: Use separat argument for search direction and separator. (Rob
Pilling, closes #5665)
Files: src/ex_docmd.c, src/ex_getln.c, src/gui.c, src/normal.c,
src/proto/search.pro,
Patch 8.2.0294
Problem:Cannot use Ex command that is also a function name.
Solution: Recognize an Ex command by a colon prefix.
Files: src/vim9compile.c, src/testdir/test_vim9_script.vim,
runtime/doc/vim9.txt
*** ../vim-8.2.0293/src/vim9compile.c 2020-02-20 22:54:39.609
Patch 8.2.0293
Problem:Various Ex commands not sufficiently tested.
Solution: Add more test cases. (Yegappan Lakshmanan, closes #5673)
Files: src/testdir/test_arglist.vim, src/testdir/test_cmdline.vim,
src/testdir/test_ex_mode.vim, src/testdir/test_excmd.vim,
sr
