Re: [patch] fixed bug in vim_getenv()

2011-04-14 Thread Dominique Pellé
H Xu wrote: > On 2011/4/14 3:05, Dominique Pellé wrote: >> >> Hi >> >> Attached patch fixes a bug in vim_getenv() found >> with cppcheck static analyzer: >> >> $ cd vim/src ; cppcheck -f -I proto misc1.c >> [misc1.c:3956]: (error) Possible null pointer dereference: mustfree - >> otherwise it is re

Re: [patch] fixed bug in vim_getenv()

2011-04-14 Thread H Xu
On 2011/4/14 16:28, Dominique Pellé wrote: H Xu wrote: On 2011/4/14 3:05, Dominique Pellé wrote: Hi Attached patch fixes a bug in vim_getenv() found with cppcheck static analyzer: $ cd vim/src ; cppcheck -f -I proto misc1.c [misc1.c:3956]: (error) Possible null pointer dereference: mustfree

vimtutor.bat broken?

2011-04-14 Thread Christian J. Robinson
On superuser.com someone asked this question : "I'm running vim on Windows 7. It works, but when I type vimtutor on the command line, a window opens and closes immediately, and nothing else happens.

Re: Suggested change to DiffOrig

2011-04-14 Thread Bram Moolenaar
Gary Johnson wrote: > > > I recently noticed an odd behavior of the DiffOrig command. If > > > 'encoding' is "utf-8", 'fileencoding' is "latin1", and the file I'm > > > editing contains characters whose encoding is different between > > > utf-8 and latin1, DiffOrig will display the lines contain

Re: [patch] fixed bug in vim_getenv()

2011-04-14 Thread Bram Moolenaar
Dominique Pelle wrote: > Attached patch fixes a bug in vim_getenv() found > with cppcheck static analyzer: > > $ cd vim/src ; cppcheck -f -I proto misc1.c > [misc1.c:3956]: (error) Possible null pointer dereference: mustfree - > otherwise it is redundant to check if mustfree is null at line 3953

Re: Suggested change to DiffOrig

2011-04-14 Thread Gary Johnson
On 2011-04-14, Bram Moolenaar wrote: > Gary Johnson wrote: > > > > > I recently noticed an odd behavior of the DiffOrig command. If > > > > 'encoding' is "utf-8", 'fileencoding' is "latin1", and the file I'm > > > > editing contains characters whose encoding is different between > > > > utf-8 and

stderr issue with mksh/pdksh

2011-04-14 Thread Chris Sutcliffe
Hi All, I've noticed an issue with vim while running under mksh and pdksh. Specifically, the stderr output by gcc (i.e. compilation warnings and errors) is not captured in the QuickFix window. I see the stderr output in the terminal window during the compilation process, however, when vim returns

Re: stderr issue with mksh/pdksh

2011-04-14 Thread Chris Sutcliffe
On 14 April 2011 16:38, Chris Sutcliffe wrote: > I've noticed an issue with vim while running under mksh and pdksh. > Specifically, the stderr output by gcc (i.e. compilation warnings and > errors) is not captured in the QuickFix window.  I see the stderr > output in the terminal window during the

Re: stderr issue with mksh/pdksh

2011-04-14 Thread Chris Sutcliffe
On 14 April 2011 20:11, Chris Sutcliffe wrote: > On 14 April 2011 16:38, Chris Sutcliffe wrote: >> I've noticed an issue with vim while running under mksh and pdksh. >> Specifically, the stderr output by gcc (i.e. compilation warnings and >> errors) is not captured in the QuickFix window.  I see th

Re: stderr issue with mksh/pdksh

2011-04-14 Thread James Vega
On Thu, Apr 14, 2011 at 08:22:22PM -0400, Chris Sutcliffe wrote: > On 14 April 2011 20:11, Chris Sutcliffe wrote: > > On 14 April 2011 16:38, Chris Sutcliffe wrote: > >> I've noticed an issue with vim while running under mksh and pdksh. > >> Specifically, the stderr output by gcc (i.e. compilation