On Sat, 21 Jan 2017, Bram Moolenaar wrote:
Patch 8.0.0210
Problem:Vim does not support bracketed paste, as implemented by xterm and
other terminals.
Solution: Add t_BE, t_BD, t_PS and t_PE.
Thanks for this, nice to see native support in Vim. Minor typo fix below.
I'm a
The XPM(2) syntax files that ship with vim currently do special highlighting
when `has("gui_running")` - it colorizes the display according to the colors of
the image.
Now that vim supports truecolor in the terminal, I'd like to see that same
support used when `termguicolors` is set.
I've
Patch 8.0.0271
Problem:May get ml_get error when :tcldo deletes lines or switches to
another buffer. (Nikolai Pavlov, closes #1421)
Solution: Check the buffer and line every time.
Files: src/if_tcl.c, src/testdir/test_tcl.vim, src/Makefile,
Patch 8.0.0270
Problem:May get ml_get error when :rubydo deletes lines or switches to
another buffer. (Nikolai Pavlov, issue #1421)
Solution: Check the buffer and line every time.
Files: src/if_ruby.c, src/testdir/test_ruby.vim
*** ../vim-8.0.0269/src/if_ruby.c
Patch 8.0.0269
Problem:May get ml_get error when :perldo deletes lines or switches to
another buffer. (Nikolai Pavlov, issue #1421)
Solution: Check the buffer and line every time.
Files: src/if_perl.xs, src/testdir/test_perl.vim
*** ../vim-8.0.0268/src/if_perl.xs
Patch 8.0.0268
Problem:May get ml_get error when :luado deletes lines or switches to
another buffer. (Nikolai Pavlov, issue #1421)
Solution: Check the buffer and line every time.
Files: src/if_lua.c, src/testdir/test_lua.vim, src/Makefile,
Bram Moolenaar wrote:
>> [...]
>> Yanking the first 3 visual columns [1,3] of
>> a
>> a
>> the output of
>> [...]
>
> That is correct. For the double-wide character the position of the
> right half is given, as documented:
>
> That is, the last screen position occupied by the character
Patch 8.0.0267
Problem:A channel test sometimes fails on Mac.
Solution: Add the test to the list of flaky tests.
Files: src/testdir/runtest.vim
*** ../vim-8.0.0266/src/testdir/runtest.vim 2016-11-17 17:56:10.103449001
+0100
--- src/testdir/runtest.vim 2017-01-29
Patch 8.0.0266
Problem:Compiler warning for using uninitialized variable.
Solution: Set tab_number also when there is an error.
Files: src/ex_docmd.c
*** ../vim-8.0.0265/src/ex_docmd.c 2017-01-29 15:18:04.896478906 +0100
--- src/ex_docmd.c 2017-01-29 21:40:06.796879123
Patch 8.0.0265
Problem:May get ml_get error when :pydo deletes lines or switches to
another buffer. (Nikolai Pavlov, issue #1421)
Solution: Check the buffer and line every time.
Files: src/if_py_both.h, src/testdir/test_python2.vim,
src/testdir/test_python3.vim,
Patch 8.0.0264
Problem:Memory error reported by ubsan, probably for using the string
returned by execute().
Solution: NUL terminate the result of execute().
Files: src/evalfunc.c
*** ../vim-8.0.0263/src/evalfunc.c 2017-01-28 18:31:36.690078200 +0100
---
Patch 8.0.0263
Problem:Farsi support is not tested enough.
Solution: Add more tests for Farsi. Clean up the code.
Files: src/farsi.c, src/testdir/test_farsi.vim
*** ../vim-8.0.0262/src/farsi.c 2017-01-29 17:59:07.872772178 +0100
--- src/farsi.c 2017-01-29 18:18:48.621069472 +0100
Patch 8.0.0262
Problem:Farsi support is barely tested.
Solution: Add more tests for Farsi. Clean up the code.
Files: src/edit.c, src/farsi.c, src/testdir/test_farsi.vim
*** ../vim-8.0.0261/src/edit.c 2017-01-27 21:48:46.960162956 +0100
--- src/edit.c 2017-01-29 17:06:40.557446744
Patch 8.0.0261
Problem:Not enough test coverage for eval functions.
Solution: Add more tests. (Dominique Pelle, closes #1420)
Files: src/testdir/test_functions.vim
*** ../vim-8.0.0260/src/testdir/test_functions.vim 2017-01-26
22:51:51.997875762 +0100
---
On Sun, Jan 29, 2017 at 3:10 PM, Bram Moolenaar wrote:
>
> Patch 8.0.0259
> Problem:Tab commands do not handle count correctly. (Ken Hamada)
> Solution: Add ADDR_TABS_RELATIVE. (Hirohito Higashi)
> Files: runtime/doc/tabpage.txt, src/ex_cmds.h, src/ex_docmd.c,
>
Patch 8.0.0260
Problem:Build fails with tiny features.
Solution: Move get_tabpage_arg() inside #ifdef.
Files: src/ex_docmd.c
*** ../vim-8.0.0259/src/ex_docmd.c 2017-01-29 14:48:06.288454957 +0100
--- src/ex_docmd.c 2017-01-29 15:13:08.498451464 +0100
***
***
Tony Mechelynck wrote:
> Line 5977 of the eval.txt helpfile says:
>
> %Gfloating point number, as %f or %E depending on value
>
> This is ambiguous if the value is NaN or =C2=B1INF: is the result in upper
> case (as for %E) or in lower case (as for %f)? I propose to replace %f
>
Patch 8.0.0259
Problem:Tab commands do not handle count correctly. (Ken Hamada)
Solution: Add ADDR_TABS_RELATIVE. (Hirohito Higashi)
Files: runtime/doc/tabpage.txt, src/ex_cmds.h, src/ex_docmd.c,
src/testdir/test_tabpage.vim
*** ../vim-8.0.0258/runtime/doc/tabpage.txt
Christian Brabandt wrote:
> On Sa, 28 Jan 2017, Bram Moolenaar wrote:
>
> > + " call delete('test_mks.out')
>
> Why is this commented out?
Oops, unfinished. File name should start with X.
--
Yesterday is history.
Tomorrow is a mystery.
Today is a gift.
That's why it is called 'present'.
Hirohito Higashi wrote:
> Hi Bram and list,
>
> How to reproduce:
> - Run vanilla Vim with five tab-pages.
> $ vim -Nu NONE -p 1 2 3 4 5
> - Edit the first tab-page's buffer and move to current line three.
> o3
> - Type the following command.
> :.tabnext
>
> Expected behavior:
> - Stay
Christian Ludwig wrote:
> Bram Moolenaar wrote:
> >
> > Thanks for explaining. So the '] mark is on the last byte of the
> > yanked text. I hesitate to change this, since quite a few Vim
> > functions with byte positions, and the number of bytes between '[ and
> > '] could be used.
> >
> > So
Patch 8.0.0258 (after 8.0.0253)
Problem:mksession test leaves file behind.
Solution: Delete the file. Rename files to start with "X".
Files: src/testdir/test_mksession.vim
*** ../vim-8.0.0257/src/testdir/test_mksession.vim 2017-01-28
17:11:09.724620245 +0100
---
Line 5977 of the eval.txt helpfile says:
%Gfloating point number, as %f or %E depending on value
This is ambiguous if the value is NaN or ±INF: is the result in upper
case (as for %E) or in lower case (as for %f)? I propose to replace %f
by %F in that line to remove the ambiguity,
Hi Bram and list,
How to reproduce:
- Run vanilla Vim with five tab-pages.
$ vim -Nu NONE -p 1 2 3 4 5
- Edit the first tab-page's buffer and move to current line three.
o3
- Type the following command.
:.tabnext
Expected behavior:
- Stay first tab-page.
Actual behavior:
- Go to the third
24 matches
Mail list logo