Patch 7.2.078

2009-01-06 Fir de Conversatie Bram Moolenaar
Patch 7.2.078 Problem:When deleting a fold that is specified with markers the cursor position may be wrong. Folds may not be displayed properly after a delete. Wrong fold may be deleted. Solution: Fix the problems. (mostly by Lech Lorens) Files: src/fold.c

Patch 7.2.079

2009-01-06 Fir de Conversatie Bram Moolenaar
Patch 7.2.079 Problem:killed netbeans events are not handled correctly. Solution: A killed netbeans event is sent when the buffer is deleted or wiped out (in this case, the netbeans annotations in this buffer have been removed). A user can still remove a sign with

Re: [patch] bug in completion with i_CTRL-N using arabic or persian keymap

2009-01-06 Fir de Conversatie Bram Moolenaar
Dominique Pelle wrote: Hi. I can reproduce the following error with valgrind memory checker using Vim-7.2.75 (huge) on Linux x86 with utf-8 locale: ==15276== Invalid read of size 1 ==15276==at 0x4026438: strlen (mc_replace_strmem.c:242) ==15276==by 0x8107E39: ins_bytes

Is vim really fully unicoded?

2009-01-06 Fir de Conversatie anhnmncb
Hi, list, as title, if so, why can't many functions still handle correctly with unicode? For example the func: getline('.')[col('.')-1] Can't return a charactor outside the range of ascii. -- Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

Re: Is vim really fully unicoded?

2009-01-06 Fir de Conversatie Tony Mechelynck
On 06/01/09 12:31, anhnmncb wrote: Hi, list, as title, if so, why can't many functions still handle correctly with unicode? For example the func: getline('.')[col('.')-1] Can't return a charactor outside the range of ascii. because string[index] returns a byte value, not a character

Re: Is vim really fully unicoded?

2009-01-06 Fir de Conversatie Matt Wozniski
On Tue, Jan 6, 2009 at 6:10 PM, Tony Mechelynck wrote: On 06/01/09 12:31, anhnmncb wrote: Hi, list, as title, if so, why can't many functions still handle correctly with unicode? For example the func: getline('.')[col('.')-1] Can't return a charactor outside the range of ascii.

Re: Is vim really fully unicoded?

2009-01-06 Fir de Conversatie Tony Mechelynck
On 07/01/09 00:39, Matt Wozniski wrote: On Tue, Jan 6, 2009 at 6:10 PM, Tony Mechelynck wrote: On 06/01/09 12:31, anhnmncb wrote: Hi, list, as title, if so, why can't many functions still handle correctly with unicode? For example the func: getline('.')[col('.')-1] Can't return a

Re: Is vim really fully unicoded?

2009-01-06 Fir de Conversatie Matt Wozniski
On 1/6/09, Tony Mechelynck wrote: On 07/01/09 00:39, Matt Wozniski wrote: On Tue, Jan 6, 2009 at 6:10 PM, Tony Mechelynck wrote: On 06/01/09 12:31, anhnmncb wrote: Hi, list, as title, if so, why can't many functions still handle correctly with unicode? For example the func:

Re: Is vim really fully unicoded?

2009-01-06 Fir de Conversatie Tony Mechelynck
On 07/01/09 02:14, Matt Wozniski wrote: On 1/6/09, Tony Mechelynck wrote: On 07/01/09 00:39, Matt Wozniski wrote: On Tue, Jan 6, 2009 at 6:10 PM, Tony Mechelynck wrote: On 06/01/09 12:31, anhnmncb wrote: Hi, list, as title, if so, why can't many functions still handle

Re: Is vim really fully unicoded?

2009-01-06 Fir de Conversatie Yue Wu
On Wed, 07 Jan 2009 08:25:35 +0800, Tony Mechelynck wrote: On 07/01/09 00:39, Matt Wozniski wrote: On Tue, Jan 6, 2009 at 6:10 PM, Tony Mechelynck wrote: On 06/01/09 12:31, anhnmncb wrote: Hi, list, as title, if so, why can't many functions still handle correctly with unicode? For example

Re: Is vim really fully unicoded?

2009-01-06 Fir de Conversatie Tony Mechelynck
On 07/01/09 02:10, Yue Wu wrote: On Wed, 07 Jan 2009 08:25:35 +0800, Tony Mechelynck wrote: On 07/01/09 00:39, Matt Wozniski wrote: On Tue, Jan 6, 2009 at 6:10 PM, Tony Mechelynck wrote: On 06/01/09 12:31, anhnmncb wrote: Hi, list, as title, if so, why can't many functions still handle

Re: Is vim really fully unicoded?

2009-01-06 Fir de Conversatie Yue Wu
On Wed, 07 Jan 2009 10:24:30 +0800, Tony Mechelynck wrote: On 07/01/09 02:10, Yue Wu wrote: On Wed, 07 Jan 2009 08:25:35 +0800, Tony Mechelynck wrote: On 07/01/09 00:39, Matt Wozniski wrote: On Tue, Jan 6, 2009 at 6:10 PM, Tony Mechelynck wrote: On 06/01/09 12:31, anhnmncb wrote: Hi,

Re: Is vim really fully unicoded?

2009-01-06 Fir de Conversatie Tony Mechelynck
On 07/01/09 03:38, Yue Wu wrote: [...] I always think that a normal operator is only used for normal mode by keyboard,[...] Oh? I have the opposite impression. For normal mode by keyboard, I don't use :normal ylEnter but yl To me, the :normal command is _only_ useful in

Re: Is vim really fully unicoded?

2009-01-06 Fir de Conversatie Yue Wu
On Wed, 07 Jan 2009 10:55:33 +0800, Tony Mechelynck wrote: On 07/01/09 03:38, Yue Wu wrote: [...] I always think that a normal operator is only used for normal mode by keyboard,[...] Oh? I have the opposite impression. For normal mode by keyboard, I don't use :normal ylEnter

Re: Is vim really fully unicoded?

2009-01-06 Fir de Conversatie Tony Mechelynck
On 07/01/09 04:17, Yue Wu wrote: On Wed, 07 Jan 2009 10:55:33 +0800, Tony Mechelynck wrote: On 07/01/09 03:38, Yue Wu wrote: [...] I always think that a normal operator is only used for normal mode by keyboard,[...] Oh? I have the opposite impression. For normal mode by keyboard, I don't

Re: Is vim really fully unicoded?

2009-01-06 Fir de Conversatie Matt Wozniski
On 1/6/09, Tony Mechelynck wrote: On 1/6/09, Matt Wozniski wrote: echo matchstr(getline('.'), '\%' . col('.') . 'c.') Again, col('.') is a byte index, not a column. What about virtcol('.') instead? Nope. \%15c is also a byte index, not a column (which is also counter-intuitive, and brings