Re: [patch] Fixes wanted-column bug in cursorbind feature

2012-03-28 Fir de Conversatie Bram Moolenaar
Gary Johnson wrote: There is a bug in Vim's tracking of the wanted cursor column in the cursorbind feature. I believe that the attached patch fixes it. Vim keeps track of the desired or wanted cursor column as well as the actual cursor column. When the user moves the cursor to a

[patch] Fixes wanted-column bug in cursorbind feature

2012-03-26 Fir de Conversatie Gary Johnson
There is a bug in Vim's tracking of the wanted cursor column in the cursorbind feature. I believe that the attached patch fixes it. Vim keeps track of the desired or wanted cursor column as well as the actual cursor column. When the user moves the cursor to a different line and the wanted

Re: [patch] Fixes wanted-column bug in cursorbind feature

2012-03-26 Fir de Conversatie Gary Johnson
On 2012-03-26, Gary Johnson wrote: There is a bug in Vim's tracking of the wanted cursor column in the cursorbind feature. I believe that the attached patch fixes it. Patch is against version 7.3.475. Regards, Gary -- You received this message from the vim_dev maillist. Do not top-post!

Re: [patch] Fixes bug in cursorbind feature when ve=all

2012-03-10 Fir de Conversatie Bram Moolenaar
Gary Johnson wrote: There is a bug in the 'cursorbind' feature of Vim 7.3.470 when 'virtualedit' is all. The cursor position in the inactive window(s) is supposed to track the cursor position in the active window so that when one of the inactive windows is entered, the cursor position

Re: is this a bug or a feature??

2007-10-20 Fir de Conversatie Ilya Sher
denis wrote: On Oct 13, 4:41 am, Ilya Sher [EMAIL PROTECTED] wrote: denis wrote: [snip] eh? is this a bug or a feature? It's a feature. The point is that terminal might be resized when running the external command so VIM will try to re-detect it after executing any external command

Re: is this a bug or a feature??

2007-10-15 Fir de Conversatie denis
On Oct 13, 4:41 am, Ilya Sher [EMAIL PROTECTED] wrote: denis wrote: [snip] eh? is this a bug or a feature? It's a feature. The point is that terminal might be resized when running the external command so VIM will try to re-detect it after executing any external command. Detection

Re: is this a bug or a feature??

2007-10-13 Fir de Conversatie Ilya Sher
? is this a bug or a feature? It's a feature. The point is that terminal might be resized when running the external command so VIM will try to re-detect it after executing any external command. Detection of the terminal size is described in :he window-size -- Beating the averages: http

Re: is this a bug or a feature??

2007-10-11 Fir de Conversatie Charles E Campbell Jr
? is this a bug or a feature? Below please find a minimal .vimrc as well as the output when starting gvim from an xterm on ubuntu. Further below is my :version information. --- [20:41:16 [EMAIL PROTECTED] ~ $ cat .vimrc-test if has(gui_running

Re: is this a bug or a feature??

2007-10-11 Fir de Conversatie denis
On Oct 11, 6:00 am, Charles E Campbell Jr [EMAIL PROTECTED] wrote: denis wrote: I am seeing a problem where execution of seemingly unrelated commands causes a problem with resetting 'lines' variable Well, I don't see that behavior. Do you have a .gvimrc file, and what's in it? That's

Re: patch to fix bug in cscope feature

2007-08-19 Fir de Conversatie Bram Moolenaar
Dominique Pelle wrote: I don't think that skipping white space before the pattern is a problem. I would rather call it an improvement. However, I think your solution also has the effect that it's not possible to have a space in the pattern. That is undesired. I found another way to

Re: patch to fix bug in cscope feature

2007-08-19 Fir de Conversatie Dominique Pelle
Your solution depends on strtok() changing the space after the command to a NUL. What if there are several spaces: :cs find e a? I don't think it is defined what strtok() does with the extra spaces. They could be replaced with NUL or not. Another solution, which is not clean either, is

patch to fix bug in cscope feature

2007-08-18 Fir de Conversatie Dominique Pelle
Hi Valgrind memory checker detects a bug when entering the command :cs find g. (requires support for cscope in vim) ==19660== Conditional jump or move depends on uninitialised value(s) ==19660==at 0x80D27F4: cs_find (if_cscope.c:969) ==19660==by 0x80D13E6: do_cscope_general

Re: patch to fix bug in cscope feature

2007-08-18 Fir de Conversatie Dominique Pelle
I just noticed that there was a memory leak in the patch I sent in my previous email. So here it is again without the memory leak. retrieving revision 1.22 diff -c -r1.22 if_cscope.c *** if_cscope.c 11 Mar 2007 14:48:29 - 1.22 --- if_cscope.c 18 Aug 2007 17:48:54 - ***

Re: patch to fix bug in cscope feature

2007-08-18 Fir de Conversatie Bram Moolenaar
Dominique Pelle wrote: Valgrind memory checker detects a bug when entering the command :cs find g. (requires support for cscope in vim) ==19660== Conditional jump or move depends on uninitialised value(s) ==19660==at 0x80D27F4: cs_find (if_cscope.c:969) ==19660==by 0x80D13E6:

Re: patch to fix bug in cscope feature

2007-08-18 Fir de Conversatie Dominique Pelle
I don't think that skipping white space before the pattern is a problem. I would rather call it an improvement. However, I think your solution also has the effect that it's not possible to have a space in the pattern. That is undesired. I found another way to fix it, and preserve old