Ragged-end block: actual behaviour conflicts with help

2006-09-22 Thread A.J.Mechelynck
From *visual.txt*For Vim version 7.0. Last change: 2006 Apr 24 second paragraph under ":help v_$" (lines 176-179). This help tag is about using $ in visual-block mode, which produces a block-visual selection with a ragged right side. ---8<--- For moving the end of the block many commands

Re: Convert2HTML Again

2006-09-22 Thread Edward L. Fox
Hi developers, On 9/22/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote: Edd - > I have spoken to your development team and I think we have come to a conclusion. > > I draw your attention to this thread: > > http://tech.groups.yahoo.com/group/vimdev/message/44853 > > Lemme know your opinions. I

completion problem

2006-09-22 Thread Yukihiro Nakadaira
There are two problems in completion. I wrote a patch. Please check the following. 1. 'ignorecase' does not work for completion. For example, when ":set nosmartcase ignorecase" and buffer is 1: foo 2: Foo Then, complete with 3: or 3: f or 3: F In all cases, only "foo" is matched. 2

block insert mode and CTRL-C problem

2006-09-22 Thread Yukihiro Nakadaira
There are two problems in block insert mode ( + I). 1. When CTRL-C is used in block insert mode, text is inserted to first line only even if multi-line was selected. For example, when there are three lines and type "1GjjIxxx" 1: aaa1: xxxaaa 2: bbb -> 2: bbb 3: ccc3: ccc P

syntax. Contained items should not contribute to highlight outside of a containing keepend item highlighting area

2006-09-22 Thread Ilya Bobir
Hello. I'm continuing my investigation on Vim's syntax highlight for the following syntax rules: :syn cluster Top contains=Block,String,Identifier :syn region Block start=+{+ end=+}+ keepend extend [EMAIL PROTECTED] :syn region String start=+"+ end=+"+ contains=Identifier :syn region Identifie

Re: Python 2.5 support

2006-09-22 Thread Bram Moolenaar
Sumner Hayes wrote: > Python 2.5 has tightened up the way it handles memory > allocation, and there's a mis-match in the way that > if_python.c handles memory allocation which worked > with earlier Python versions but causes vim to > seg-fault with 2.5. Essentially, PyMem_DEL shouldn't > be pair