On 20/02/09 05:45, Bram Moolenaar wrote:
Matt Wozniski wrote:
src/fileio.c : vim_tempname() contains these lines:
if (GetTempFileName(szTempFile, buf4, 0, itmp) == 0)
return NULL;
/* GetTempFileName() will create the file, we don't want that */
(void)DeleteFile(itmp);
On 20/02/09 05:45, Bram Moolenaar wrote:
Nikola Knezevic wrote:
On 18 Feb 2009, at 03:30 , Matt Wozniski wrote:
I agree with this, leave the message as is.
I'm actually not sure if adding f to go a screen down is helpful.
Slightly off-topic...
Is it possible to add '/' to more-prompt,
On Fri, Feb 20, 2009 at 10:16, Tony Mechelynck
antoine.mechely...@gmail.com wrote:
On 20/02/09 05:45, Bram Moolenaar wrote:
Changing this behavior will not be easy, so you will have to come up
with some kind of proof that the current mechanism may fail.
Also, what about the case when a
However I've made a different design choice: my plugin acts as a
preprocessor. Thanks to that, I'm able to know the line where an
assertion failure occurred
Cool.
BTW, tAssert provides convenience functions that my script don't (yet?).
At first, I wondered if both plugins should be merged.
Saw this interesting post to a tip on the wiki:
http://vim.wikia.com/index.php?title=Fix_broken_arrow_key_navigation_in_insert_modediff=22116oldid=prev
Apparently this xterm bug report:
http://bugs.gentoo.org/212546
has been blamed on Vim, but for whatever reason the poster does not
expect
Tom Link wrote:
However I've made a different design choice: my plugin acts as a
preprocessor. Thanks to that, I'm able to know the line where an
assertion failure occurred
Cool.
BTW, tAssert provides convenience functions that my script don't (yet?).
At first, I wondered if
On Friday 20 February 2009 6:53 am, björn wrote:
For the last two weeks or so I've been getting this warning when
compiling Vim (on Mac OS X):
ex_docmd.c: In function 'do_one_cmd':
ex_docmd.c:5937: warning: 'end' may be used uninitialized in this function
ex_docmd.c: In function
On 20/02/09 16:03, Charles Campbell wrote:
Tom Link wrote:
However I've made a different design choice: my plugin acts as a
preprocessor. Thanks to that, I'm able to know the line where an
assertion failure occurred
Cool.
BTW, tAssert provides convenience functions that my script don't
björn wrote:
Hi,
For the last two weeks or so I've been getting this warning when
compiling Vim (on Mac OS X):
ex_docmd.c: In function 'do_one_cmd':
ex_docmd.c:5937: warning: 'end' may be used uninitialized in this function
ex_docmd.c: In function 'do_one_cmd':
ex_docmd.c:5937: warning:
On 20/02/09 13:53, björn wrote:
Hi,
For the last two weeks or so I've been getting this warning when
compiling Vim (on Mac OS X):
ex_docmd.c: In function 'do_one_cmd':
ex_docmd.c:5937: warning: 'end' may be used uninitialized in this function
ex_docmd.c: In function 'do_one_cmd':
On 20/02/09 17:39, Dominique Pelle wrote:
björn wrote:
Hi,
For the last two weeks or so I've been getting this warning when
compiling Vim (on Mac OS X):
ex_docmd.c: In function 'do_one_cmd':
ex_docmd.c:5937: warning: 'end' may be used uninitialized in this function
ex_docmd.c: In
On 20/02/09 18:02, björn wrote:
2009/2/20 Tony Mechelynck:
On 20/02/09 13:53, björn wrote:
Hi,
For the last two weeks or so I've been getting this warning when
compiling Vim (on Mac OS X):
ex_docmd.c: In function 'do_one_cmd':
ex_docmd.c:5937: warning: 'end' may be used uninitialized in
On 20/02/09 15:43, Ben Fritz wrote:
Saw this interesting post to a tip on the wiki:
http://vim.wikia.com/index.php?title=Fix_broken_arrow_key_navigation_in_insert_modediff=22116oldid=prev
Apparently this xterm bug report:
http://bugs.gentoo.org/212546
has been blamed on Vim, but for
On 20/02/09 15:43, Ben Fritz wrote:
Saw this interesting post to a tip on the wiki:
http://vim.wikia.com/index.php?title=Fix_broken_arrow_key_navigation_in_insert_modediff=22116oldid=prev
Apparently this xterm bug report:
http://bugs.gentoo.org/212546
has been blamed on Vim, but for
This patch implements persistent undo. It is against SVN revision
1365. I'd like to submit it to the list to see what people think.
More specifically, here are the changes:
1. Added commands :wundo and :rundo that write and read undo files
respectively. An undo file is a binary file that
Ben Fritz wrote:
Saw this interesting post to a tip on the wiki:
http://vim.wikia.com/index.php?title=Fix_broken_arrow_key_navigation_in_insert_modediff=22116oldid=prev
Apparently this xterm bug report:
http://bugs.gentoo.org/212546
has been blamed on Vim, but for whatever reason
Bjorn Winckler wrote:
For the last two weeks or so I've been getting this warning when
compiling Vim (on Mac OS X):
ex_docmd.c: In function 'do_one_cmd':
ex_docmd.c:5937: warning: 'end' may be used uninitialized in this function
ex_docmd.c: In function 'do_one_cmd':
ex_docmd.c:5937:
Nikolai Weibull wrote:
On Fri, Feb 20, 2009 at 10:16, Tony Mechelynck
antoine.mechely...@gmail.com wrote:
On 20/02/09 05:45, Bram Moolenaar wrote:
Changing this behavior will not be easy, so you will have to come up
with some kind of proof that the current mechanism may fail.
Nazri Ramliy wrote:
On Fri, Feb 20, 2009 at 9:18 AM, Nazri ayieh...@gmail.com wrote:
I'm refining the patch - fixing a memory leak (stupid me :), and
improving the shortening of the matching paths to get the minimum
unique length of each. This is much much better than the simple (and
19 matches
Mail list logo
