Patch 7.1.147

2007-10-30 Fir de Conversatie Bram Moolenaar
Patch 7.1.147 (after 7.1.127) Problem:Freeing memory already freed when completing user name. (Meino Cramer) Solution: Use a flag to remember if orig needs to be freed. Files: src/ex_getln.c *** ../vim-7.1.146/src/ex_getln.c Sun Sep 30 22:10:45 2007 ---

Python unit tests

2007-10-30 Fir de Conversatie George V. Reilly
I've updated the Win64 port. By far the biggest change is that the Python interface is now supported. That required some substantial changes to the code to use Py_ssize_t: see http://docs.python.org/whatsnew/pep-353.html You can read more about some of the issues that I had at

Re: Operator pending mode

2007-10-30 Fir de Conversatie [EMAIL PROTECTED]
On Oct 30, 1:38 pm, Bram Moolenaar [EMAIL PROTECTED] wrote: Ben Schmidt wrote: 3. Don't know about v:operator (works for me), the showcmd option means it could also be v:command or v:operatorcommand (since there is ... I'm not quite convinced adding v:operator is useful. What would help

Re: Operator pending mode

2007-10-30 Fir de Conversatie David Fishburn
On 10/30/07, Bram Moolenaar [EMAIL PROTECTED] wrote: David Fishburn wrote: On Oct 30, 1:38 pm, Bram Moolenaar [EMAIL PROTECTED] wrote: Ben Schmidt wrote: 3. Don't know about v:operator (works for me), the showcmd option means it could also be v:command or v:operatorcommand

Re: Operator pending mode

2007-10-30 Fir de Conversatie Ben Schmidt
Well, I can see that you get the information, but this is not really a useful real-world example. Think of a user that wants to get something done for which v:operator is needed. And for which there is no other solution. Here's a somewhat naively implemented example where a custom

Reproducible SEGV when deleting over BOL using i_CTRL-o

2007-10-30 Fir de Conversatie Matthew Wozniski
To reproduce, do the following in a newly started vim: First enable 'h' moving between lines to give us a way to delete over BOL, though left would work if you're using gvim :set ww=h then, ixCRC-odh that is, insert a line containing x, then try to delete over BOL without leaving insert mode

Re: (2, actually 3) Operator pending mode

2007-10-30 Fir de Conversatie Ben Schmidt
Well, I can see that you get the information, but this is not really a useful real-world example. Think of a user that wants to get something done for which v:operator is needed. And for which there is no other solution. Here's a somewhat naively implemented example where a custom

Re: (2) Operator pending mode

2007-10-30 Fir de Conversatie Ben Schmidt
[CCing this to the mailing lists; only went to Bram before, but some parts may be useful for others.] I'm not quite convinced adding v:operator is useful. What would help is giving a couple of examples how it's used. Also, in the docs for v:operator it would be good to have a few examples