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);
Is this really right? Is there any reason to call DeleteFile() here?
On Tue, Feb 17, 2009 at 9:19 PM, Markus Heidelberg wrote:
>
> Bram Moolenaar, 18.02.2009:
>>
>> Markus Heidelberg wrote:
>>
>> > After reaching the end of the more prompt, hitting SPACE jumps out of
>> > it. Add 'f' to avoid this problem and for consistency with 'b' in
>> > "scroll down a screen".
Bram Moolenaar, 18.02.2009:
>
> Markus Heidelberg wrote:
>
> > After reaching the end of the more prompt, hitting SPACE jumps out of
> > it. Add 'f' to avoid this problem and for consistency with 'b' in
> > "scroll down a screen".
> >
> > This also changes the help message to contain "f" instea
Markus Heidelberg wrote:
> ---
> src/message.c |2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/src/message.c b/src/message.c
> index e0f2897..1cb7344 100644
> --- a/src/message.c
> +++ b/src/message.c
> @@ -2504,7 +2504,6 @@ do_more_prompt(typed_char)
>
Markus Heidelberg wrote:
> Also fix a typo.
> ---
> runtime/doc/syntax.txt |5 +++--
> runtime/doc/tagsrch.txt |2 +-
> 2 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/runtime/doc/syntax.txt b/runtime/doc/syntax.txt
> index 415b8bd..22250eb 100644
> --- a/runtime/doc
Dominique Pelle wrote:
> Vim-7.2.108 can read and write beyond allocated memory when
> using autocmd VimResized. Bug happens if a shell command is
> used in VimResized autocmd such as...
>
> :au! VimResized * sil !echo -ne "\033]12;green\007"
>
> With this autocmd, I observe the following er
Markus Heidelberg wrote:
> After reaching the end of the more prompt, hitting SPACE jumps out of
> it. Add 'f' to avoid this problem and for consistency with 'b' in
> "scroll down a screen".
>
> This also changes the help message to contain "f" instead of "SPACE",
> I'm not sure about this.
> T
James Vega wrote:
> When triggering the cmdwin from input(), the search history is displayed
> instead of the input history. This is because ex_window() is directly
> inspecting ccline.cmdfirstc instead of using get_cmdline_type().
> Attached patch fixes the issue.
Thanks, I'll put it in the t
Yukihiro Nakadaira wrote:
> This command causes crash.
>
> :call substitute('', '\(.\@<=\)*', '\=submatch(1)', '')
>
> Here is backtrace.
Easy to reproduce. Thanks for reporting the problem.
--
>From "know your smileys":
<>:-) Bishop
/// Bram Moolenaar -- b...@moolenaar.net -- http://w
Also fix a typo.
---
runtime/doc/syntax.txt |5 +++--
runtime/doc/tagsrch.txt |2 +-
2 files changed, 4 insertions(+), 3 deletions(-)
diff --git a/runtime/doc/syntax.txt b/runtime/doc/syntax.txt
index 415b8bd..22250eb 100644
--- a/runtime/doc/syntax.txt
+++ b/runtime/doc/syntax.txt
@@ -
Hi
Vim-7.2.108 can read and write beyond allocated memory when
using autocmd VimResized. Bug happens if a shell command is
used in VimResized autocmd such as...
:au! VimResized * sil !echo -ne "\033]12;green\007"
With this autocmd, I observe the following error with valgrind
when resizing the
And in this subject it should obiously be PageUp, as in the patch :)
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~--~~~~--~~--~--~---
On Tue, Feb 17, 2009 at 10:42:00PM +0100, björn wrote:
> The following bit of configure.in looked a bit strange, so I changed
> it. No idea what that special "if" for MACOSX does though.
Well, there's that comment:
dnl For Mac OSX 10.2 config.o is included in the Python library.
Can't spe
2009/2/17 Danek Duvall:
>
> I may not get to it before this weekend, but I'll post another patch as
> soon as I have it. In the meantime, if you have a chance to try my latest
> patch out on OS X, I'd be curious to know if it works there.
The following bit of configure.in looked a bit strange, s
On Tue, Feb 17, 2009 at 07:32:35PM +0100, björn wrote:
> Yes that is all I am after -- I can't see any particular use for
> having two or more co-resident. (?)
The use case would be if you had a script that could only run with 2.3 and
another that could only run with 2.6, and you wanted to use
On 17/02/09 19:15, Larson, DavidX S wrote:
> Hello all,
>
> I was working on my script when I ran across this unexpected behavior with
> the "if" statement. The doc says:
>
> :if {expr1} *:if* *:endif* *:en* *E171* *E579* *E580*
> :en[dif]Execute the commands u
On 2/17/09, Larson, DavidX S wrote:
>
> Hello all,
>
> I was working on my script when I ran across this unexpected behavior
> with the "if" statement. The doc says:
>
> :if {expr1} *:if* *:endif* *:en* *E171* *E579* *E580*
> :en[dif]Execute the commands un
2009/2/17 Danek Duvall:
>
> björn wrote:
>
>> 2009/2/15 Danek Duvall:
>> >
>> > And further down that road would be to experiment with whether multiple
>> > versions of Python can be loaded into memory at the same time. If that's
>> > the case, then you could have different scripts running with d
Hello all,
I was working on my script when I ran across this unexpected behavior with the
"if" statement. The doc says:
:if {expr1} *:if* *:endif* *:en* *E171* *E579* *E580*
:en[dif]Execute the commands until the next matching ":else"
On Feb 17, 9:47 am, Andreas Bernauer wrote:
> Yukihiro Nakadaira wrote:
> > This command causes crash.
>
> > :call substitute('', '\(.\@<=\)*', '\=submatch(1)', '')
>
> Confirmed for vim 7.2.108
> (called as vim -u NONE)
>
Also on Windows gvim, 7.2.101.
--~--~-~--~~~---
björn wrote:
> 2009/2/15 Danek Duvall:
> >
> > And further down that road would be to experiment with whether multiple
> > versions of Python can be loaded into memory at the same time. If that's
> > the case, then you could have different scripts running with different
> > versions in the same
Hi Danek,
2009/2/15 Danek Duvall:
>
> And further down that road would be to experiment with whether multiple
> versions of Python can be loaded into memory at the same time. If that's
> the case, then you could have different scripts running with different
> versions in the same vim session. I
Yukihiro Nakadaira wrote:
> This command causes crash.
>
> :call substitute('', '\(.\@<=\)*', '\=submatch(1)', '')
>
Confirmed for vim 7.2.108
(called as vim -u NONE)
--
Andreas.
--~--~-~--~~~---~--~~
You received this message from the "vim_dev" maillist.
Fo
This command causes crash.
:call substitute('', '\(.\@<=\)*', '\=submatch(1)', '')
Here is backtrace.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb708fac0 (LWP 23440)]
0xb73f9939 in strncpy () from /lib/tls/i686/cmov/libc.so.6
(gdb) backtrace
#0 0xb73f9939 in st
Markus Heidelberg, 17.02.2009:
> After reaching the end of the more prompt, hitting SPACE jumps out of
> it. Add 'f' to avoid this problem and for consistency with 'b' in
> "scroll down a screen".
Of course here it should be "scroll back a screen" and in the subject
"scrolling down a screen".
Ma
After reaching the end of the more prompt, hitting SPACE jumps out of
it. Add 'f' to avoid this problem and for consistency with 'b' in
"scroll down a screen".
This also changes the help message to contain "f" instead of "SPACE",
I'm not sure about this.
This change also adds a missing leading Spa
---
src/message.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/src/message.c b/src/message.c
index e0f2897..1cb7344 100644
--- a/src/message.c
+++ b/src/message.c
@@ -2504,7 +2504,6 @@ do_more_prompt(typed_char)
break;
case 'u': /*
---
runtime/doc/tips.txt |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/runtime/doc/tips.txt b/runtime/doc/tips.txt
index fa03236..ea108b7 100644
--- a/runtime/doc/tips.txt
+++ b/runtime/doc/tips.txt
@@ -26,8 +26,8 @@ Change a name in multiple files
28 matches
Mail list logo
