On 28-Jun-2013 23:05 +0200, Bram Moolenaar wrote:
Dominique Pelle wrote:
Ingo Karkat sw...@ingo-karkat.de wrote:
Hello Vim developers,
I recently started using latest Vim builds with the new NFA-engine
enabled, and I immediately noticed discrepancies when using my personal
fork of the
понедельник, 1 июля 2013 г., 1:15:35 UTC+3 пользователь Lech Lorens написал:
On 29-Jun-2013 Aliaksandr Rahalevich saks...@gmail.com wrote:
It works with
set regexpengine=1
but fails to open file with regexpengine=2.
It's definitely working with 1242 patchset, but fails with
I updated my patch because I found my change of Py_file_input in run_do should
be kept with Py_eval_input.
--
--
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
Hi mattn,
2013/07/01 Mon 19:27:42 UTC+9 mattn wrote:
I updated my patch because I found my change of Py_file_input in run_do
should be kept with Py_eval_input.
After applying your new patch, test 86 and 87 still fail even on Windows.
It seems that calling PyErr_PrintEx() was missing.
Please
On Monday, July 1, 2013 9:00:04 PM UTC+9, Ken Takata wrote:
Hi mattn,
2013/07/01 Mon 19:27:42 UTC+9 mattn wrote:
I updated my patch because I found my change of Py_file_input in run_do
should be kept with Py_eval_input.
After applying your new patch, test 86 and 87 still fail even on
On Mon, Jul 01, 2013 at 05:00:04AM -0700, Ken Takata wrote:
After applying your new patch, test 86 and 87 still fail even on Windows.
It seems that calling PyErr_PrintEx() was missing.
Please check the attached patch.
diff --git a/runtime/doc/if_pyth.txt b/runtime/doc/if_pyth.txt
---
Hi James,
2013/07/01 Mon 21:18:28 UTC+9 James McCoy wrote:
I think you mean endorsed in this sentence.
Thank you.
--
Ken Takata
--
--
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
Hi,
I found some compiler warnings in winclip.c.
Attached patch fixes them.
Thanks,
Ken Takata
--
--
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
Hello Vim developers,
I noticed a regression:
$ vim -N -u NONE
:echo foo
The intro message is cleared, the (now empty) UI does not show foo.
Expected behavior: The intro message stays visible, the command-line
shows foo.
This happens with any command that echoes a single line, e.g. also with
On Mon, Jul 1, 2013 at 11:45 AM, Ingo Karkat sw...@ingo-karkat.de wrote:
Hello Vim developers,
I noticed a regression:
$ vim -N -u NONE
:echo foo
The intro message is cleared, the (now empty) UI does not show foo.
Expected behavior: The intro message stays visible, the command-line
This problem appeared with a recent patch (I can't backtrack on the
patches to find out which one on my work machine -- however, I suspect
its patch#1277).
Have two files, tmp1 and tmp2, with several lines contained in each:
vim -O tmp1 tmp2
:set cul
:wincmd l
:set cul
:wincmd h
Note that
Kevin Goodsell wrote:
Using Vim built with GUI support in a terminal, and ttymouse set to
xterm2, mouse clicks (as well as dragging events) in column 123
consistently register as being in column 96. E.g., if a line of text
contains 123 characters, clicking on the last character will position
Patch 7.3.1281
Problem:When 'ttymouse' is set to xterm2 clicking in column 123 moves
the cursor to column 96. (Kevin Goodsell)
Solution: Decode KE_CSI.
Files: src/term.c
*** ../vim-7.3.1280/src/term.c 2013-06-30 17:51:46.0 +0200
--- src/term.c 2013-07-01
Charles Campbell wrote:
This problem appeared with a recent patch (I can't backtrack on the
patches to find out which one on my work machine -- however, I suspect
its patch#1277).
Have two files, tmp1 and tmp2, with several lines contained in each:
vim -O tmp1 tmp2
:set cul
:wincmd
Patch 7.3.1282 (after 7.3.1277)
Problem:'cursorline' not drawn in any other window. (Charles Campbell)
Solution: Do draw the cursor line in other windows.
Files: src/screen.c
*** ../vim-7.3.1281/src/screen.c2013-06-30 17:23:46.0 +0200
--- src/screen.c
Ken Takata wrote:
2013/06/20 The 16:03:03 UTC+9 Bram Moolenaar wrote:
When running the tests reloading is not an option.
Perhaps explicitly setting 'fenc' would work?
No, it doesn't solve the problem. When Vim loads test17.in,
the binary part is already broken, because the default
Patch 7.3.1283
Problem:Test 71 fails on MS-Windows.
Solution: Put the binary data in a separate file. (Ken Takata)
Files: src/testdir/test71.in, src/testdir/test71a.in
*** ../vim-7.3.1282/src/testdir/test71.in 2013-06-19 21:17:26.0
+0200
--- src/testdir/test71.in
Patch 7.3.1284
Problem:Compiler warnings in MS-Windows clipboard handling.
Solution: Add type casts. (Ken Takata)
Files: src/winclip.c
*** ../vim-7.3.1283/src/winclip.c 2013-02-26 14:56:24.0 +0100
--- src/winclip.c 2013-07-01 21:05:53.0 +0200
Patch 7.3.1285
Problem:No tests for picking a window when selecting an entry in a
location list. Not picking the right window sometimes.
Solution: Add test 96. Set usable_win appropriately. (Lech Lorens)
Files: src/quickfix.c, src/testdir/Makefile, src/testdir/test96.in,
Ken Takata wrote:
Hi James,
2013/07/01 Mon 21:18:28 UTC+9 James McCoy wrote:
I think you mean endorsed in this sentence.
Thank you.
Thanks everybody, the tests now pass for me.
--
-rwxr-xr-x 1 root 24 Oct 29 1929 /bin/ed
-rwxr-xr-t 4 root 131720 Jan 1 1970
Ingo Karkat wrote:
Hello Vim developers,
I noticed a regression:
$ vim -N -u NONE
:echo foo
The intro message is cleared, the (now empty) UI does not show foo.
Expected behavior: The intro message stays visible, the command-line
shows foo.
This happens with any command that
On Mon, Jul 01, 2013 at 10:03:19PM +0200, Bram Moolenaar wrote:
Ingo Karkat wrote:
Hello Vim developers,
I noticed a regression:
$ vim -N -u NONE
:echo foo
The intro message is cleared, the (now empty) UI does not show foo.
Expected behavior: The intro message stays visible,
On Mon, July 1, 2013 17:45, Ingo Karkat wrote:
Hello Vim developers,
I noticed a regression:
$ vim -N -u NONE
:echo foo
The intro message is cleared, the (now empty) UI does not show foo.
Expected behavior: The intro message stays visible, the command-line
shows foo.
This happens with
23 matches
Mail list logo