Re: The list on vim-patches page

2009-12-16 Fir de Conversatie Tom Link
It would help if the items listed on the vim-patches page mentioned any restrictions on OShttp://groups.google.com/group/vim_dev/web/vim-patches  BTW what is the procedure to determine whether these patches are ever included in vim? Since some of these patches were written for older versions

Re: The list on vim-patches page

2009-12-16 Fir de Conversatie Charles Campbell
Tom Link wrote: It would help if the items listed on the vim-patches page mentioned any restrictions on OShttp://groups.google.com/group/vim_dev/web/vim-patches BTW what is the procedure to determine whether these patches are ever included in vim? The procedure is straightforward:

Re: Patch for 2html.vim

2009-12-16 Fir de Conversatie Bram Moolenaar
Andy Spencer wrote: On 2009-12-15 21:11, Christian Brabandt wrote: Hi, the following patch adds diff functionality to the 2html.vim plugin. Maybe I should start a new thread for this, but since we're on the topic of 2html.vim.. I've made a few modifications to 2html.vim as well, some

Re: Patch 7.2.310

2009-12-16 Fir de Conversatie Bram Moolenaar
Sir Raorn (?) wrote: On Wed, Dec 2, 2009 at 15:28, Bram Moolenaar b...@moolenaar.net wrote: Problem:When a filetype plugin in ~/.vim/ftdetect uses :setfiletype and the file starts with a # comment it gets conf filetype. This patch was submitted more than three years ago.

Re: The list on vim-patches page

2009-12-16 Fir de Conversatie Tom Link
The procedure is straightforward: Bram M decides whether a patch goes into the vim source. When I asked Bram about that particular patch he said that there were some problems with it and that he waited for a new version that solves these issues. These problems were reported by the author of the

Patch 7.2.316

2009-12-16 Fir de Conversatie Bram Moolenaar
Patch 7.2.316 Problem:May get multiple _FORTIFY_SOURCE arguments. (Tony Mechelynck) Solution: First remove all these arguments and then add the one we want. (Dominique Pelle) Files: src/auto/configure, src/configure.in *** ../vim-7.2.315/src/auto/configure 2009-12-02

Patch 7.2.319

2009-12-16 Fir de Conversatie Bram Moolenaar
Patch 7.2.319 Problem:Motif: accessing freed memory when cancelling font dialog. Solution: Destroy the widget only after accessing it. (Dominique Pelle) Files: src/gui_xmdlg.c *** ../vim-7.2.318/src/gui_xmdlg.c 2009-11-03 12:53:44.0 +0100 --- src/gui_xmdlg.c

Patch 7.2.320

2009-12-16 Fir de Conversatie Bram Moolenaar
Patch 7.2.320 Problem:Unused function in Mzscheme interface. Solution: Remove the function and what depends on it. (Dominique Pelle) Files: src/if_mzsch.c, src/proto/if_mzsch.pro *** ../vim-7.2.319/src/if_mzsch.c 2009-09-11 12:20:47.0 +0200 --- src/if_mzsch.c

[patch] Initialise history before adding elements

2009-12-16 Fir de Conversatie Lech Lorens
The attached patch fixes the behaviour of Vim where histadd() and searching with * fail to add elements to history if the history is empty. How to reproduce: Problem with histadd(): $ vim -i NONE -c 'call histadd(search, search)' \ -c 'call histadd(search, for)'\

Re: [patch] Initialise history before adding elements

2009-12-16 Fir de Conversatie Steven Sajous
does anyone know why the unsubscribe does not work on this list? I have done it 4 times and got a confirmation every time. Still getting emails. On Wed, Dec 16, 2009 at 5:38 PM, Lech Lorens lech.lor...@gmail.com wrote: The attached patch fixes the behaviour of Vim where histadd() and searching

RE: [patch] Initialise history before adding elements

2009-12-16 Fir de Conversatie John Beckett
Steven Sajous wrote: does anyone know why the unsubscribe does not work on this list? I have done it 4 times and got a confirmation every time. Still getting emails. Please say exactly what you did. You emailed what address approximately how many hours ago? John -- You received this message