> I've been digging through the Vim source and had trouble trying to
> understand what win_lbr_chartabsize() is doing. About 112 lines from
> the start of the function (in 7.1.94) there's a part that should take
> the width of a tab into account when used in combination with
> "showbreak". I could
On Sun 30-Sep-07 3:28pm -0600, Bram Moolenaar wrote:
> Patch 7.1.128 (extra)
What's with the "About" in the subject line? Isn't simply:
Patch 7.1.127
Patch 7.1.128 (extra)
enough?
--
Best regards,
Bill
--~--~-~--~~~---~--~~
You received this message
I've been digging through the Vim source and had trouble trying to
understand what win_lbr_chartabsize() is doing. About 112 lines from
the start of the function (in 7.1.94) there's a part that should take
the width of a tab into account when used in combination with
"showbreak". I couldn't work o
Patch 7.1.128 (extra)
Problem:Build problems with new version of Cygwin.
Solution: Remove -D__IID_DEFINED__, like with MingW. (Guopeng Wen)
Files: src/Make_cyg.mak
*** ../vim-7.1.127/src/Make_cyg.mak Sun Apr 30 20:46:49 2006
--- src/Make_cyg.makSat Sep 29 13:09:34 2007
**
Patch 7.1.127
Problem:Memory leak when doing cmdline completion. (Dominique Pelle)
Solution: Free "orig" argument of ExpandOne() when it's not used.
Files: src/ex_getln.c
*** ../vim-7.1.126/src/ex_getln.c Sat Sep 29 14:15:00 2007
--- src/ex_getln.c Sun Sep 30 17:55:47 2007
On Sep 30, 9:20 am, Gautam Iyer <[EMAIL PROTECTED]> wrote:
> Hi All,
>
> Sorry for the spam: I just came across an animated GIF online which
> seems to show what would happen if Micro$oft developed Vim.
>
>http://idorosen.com/images/vim.gif
>
> I thought some of you might find it amusing.
>
On 9/30/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
> Please verify this fixes the leak, also without your suggested patch.
> I tried your example and it appears to fix it. But I have not tried
> every possible completion.
Yes it does fix the leak. Putting a printf() near the new vim_free()
Bram Moolenaar wrote:
> Tony Mechelynck wrote:
>
>>> I don't know about this one:
>>>
gui_gtk_x11.c: In function 'gui_mch_init':
gui_gtk_x11.c:3418: warning: not enough variable arguments to fit a
sentinel
>> at the line just before "# else" in
>>
>> #ifdef FEAT_GUI_GNOME
>>
On Sep 30, 4:16 pm, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
>
> So the first thing to work on would be doing this on MS-Windows. Test
> with various native MS-Windows (or even DOS) programs. After that the
> rest would be easy.
Ok, got it.
>
> Note that I don't like the idea of running a s
On Sep 30, 11:48 am, "Yakov Lerner" <[EMAIL PROTECTED]> wrote:
> On 9/30/07, A.Politz <[EMAIL PROTECTED]> wrote:
>
>
>
>
>
> > I am student of computer science. In the next semester I'll
> > have to do some practical work supervised by a professor.
> > Now what I really would like to do in this
Tony Mechelynck wrote:
> > I don't know about this one:
> >
> >> gui_gtk_x11.c: In function 'gui_mch_init':
> >> gui_gtk_x11.c:3418: warning: not enough variable arguments to fit a
> >> sentinel
>
> at the line just before "# else" in
>
> #ifdef FEAT_GUI_GNOME
> /* Initialize the GNOME
Dominique Pelle wrote:
> I can reproduce a memory leak 100% of the time in vim-7.1.123:
>
> Start vim with:
>
> vim -u NONE -U NONE
>
> Then set the following options:
>
> :set nocompatible
> :set wildmode=longest,list
> :set wildmenu
>
> vim will then leak memory whenever file comp
On Sep 30, 8:18 am, Ben Schmidt <[EMAIL PROTECTED]> wrote:
> A.Politz wrote:
> > I am student of computer science. In the next semester I'll
> > have to do some practical work supervised by a professor.
> > Now what I really would like to do in this project, is
> > giving vim the ability to sta
Hi,
On 9/30/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
>
>
> A.Politz wrote:
>
> > I am student of computer science. In the next semester I'll
> > have to do some practical work supervised by a professor.
> > Now what I really would like to do in this project, is
> > giving vim the ability to
Tony Mechelynck wrote:
> Guopeng Wen wrote:
>> On 9/29/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
>>> Guopeng Wen -
>>>
On 8/11/07, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
> Chris Sutcliffe wrote:
>
>>> Thanks for taking the effort to verify what works.
>> No problem at a
Bram Moolenaar wrote:
> Tony Mechelynck wrote:
>
>> While compiling Vim 7.1.125 a few minutes ago (a full compile since globals.h
>> has changed) I noticed a few warnings and thought you might be interested.
>>
>> My configure options are at
>> http://users.skynet.be/antoine.mechelynck/vim/compun
Hi
I can reproduce a memory leak 100% of the time in vim-7.1.123:
Start vim with:
vim -u NONE -U NONE
Then set the following options:
:set nocompatible
:set wildmode=longest,list
:set wildmenu
vim will then leak memory whenever file completion on Ex command
results in no match:
:e
Tony Mechelynck wrote:
> While compiling Vim 7.1.125 a few minutes ago (a full compile since globals.h
> has changed) I noticed a few warnings and thought you might be interested.
>
> My configure options are at
> http://users.skynet.be/antoine.mechelynck/vim/compunix.htm#p1
>
> The attached t
A.Politz wrote:
> I am student of computer science. In the next semester I'll
> have to do some practical work supervised by a professor.
> Now what I really would like to do in this project, is
> giving vim the ability to start and manage subprocesses.
>
> What I have in mind is :
>
> - Ob
> Somehow all session files set the buffer local option 'autoread' for
> every restored buffer regardless of what the global/local setting is.
I see the problem, I'll fix it.
> I've also noticed that doing "vim -u NONE -c ':setlocal autoread?'"
> shows the odd value of "--autoread".
This mean
Since src/gui_w48.c was included in this patch, it should be marked with
(extra). That means it requires the extra archive to work without
errors. But it will work anyway, just ignore the errors.
--
The chat program is in public domain. This is not the GNU public license.
If it breaks then y
Patch 7.1.126
Problem:":vimgrep */*" fails when a BufRead autocommand changes directory.
(Bernhard Kuhn)
Solution: Change back to the original directory after loading a file.
Also: use shorten_fname1() to avoid duplicating code.
Files: src/buffer.c, src/ex_docmd
ap wrote:
>
>
> On Sep 29, 5:44 pm, "Christian J. Robinson" <[EMAIL PROTECTED]>
> wrote:
>> Somehow all session files set the buffer local option 'autoread' for
>> every restored buffer regardless of what the global/local setting is.
>
> What does
> :verbose set autoread
> tell you, after your
On 9/30/07, A.Politz <[EMAIL PROTECTED]> wrote:
>
>
> I am student of computer science. In the next semester I'll
> have to do some practical work supervised by a professor.
> Now what I really would like to do in this project, is
> giving vim the ability to start and manage subprocesses.
>
> What
Hi All,
Sorry for the spam: I just came across an animated GIF online which
seems to show what would happen if Micro$oft developed Vim.
http://idorosen.com/images/vim.gif
I thought some of you might find it amusing.
GI
--
Shotgun wedding: A case of wife or death.
--~--~-~--~
25 matches
Mail list logo