On 19/08/2010 21:52, Sergey Khorev wrote:
F1rst! :-)
Pros: All Windows specific code.
Cons: Can't do anything clever with an invalid format string.
Should be ok with mingw32.
Wow, so quick :)
I think you've done it right by installing the handler once and for
all. For users of ancient
On Aug 19, 8:47 am, Mike Williams mike.willi...@globalgraphics.com
wrote:
Degrees of failing. There is a school of thought that if you are gonna
fail, fail in a really obvious way. Such as crashing? ;-)
I think for things like a text editor, with the possibility of losing
important data
On 20/08/2010 13:40, Ben Fritz wrote:
On Aug 19, 8:47 am, Mike Williamsmike.willi...@globalgraphics.com
wrote:
Degrees of failing. There is a school of thought that if you are gonna
fail, fail in a really obvious way. Such as crashing? ;-)
I think for things like a text editor, with the
Works for me. Checked with VC6 which does not have the invalid param
handler. I tidied it up for potential ambiguity and reworked the patch -
see attached. Using macros for the function calls removes the needs for
duplicating the complex conditional or introducing another symbol for later
On 18/08/2010 22:18, Bram Moolenaar wrote:
Mike Williams wrote:
On 18/08/2010 10:09, Benjamin R. Haskell wrote:
On Wed, 18 Aug 2010, Christian Brabandt wrote:
Hi Bram!
On Mi, 18 Aug 2010, Bram Moolenaar wrote:
Christian Brabandt wrote:
On Mo, 16 Aug 2010, Christian Brabandt wrote:
On 18/08/2010 18:54, Sergey Khorev wrote:
It is by design in the recent VC CRT libraries (VS2005 onwards?) Any
unsupported format specifier will result in a crash. On Windows, or at
least builds that use recent VC CRT libraries, VIM needs to validate the
format string that it only contains
Mike Williams wrote:
On 18/08/2010 18:54, Sergey Khorev wrote:
It is by design in the recent VC CRT libraries (VS2005 onwards?) Any
unsupported format specifier will result in a crash. On Windows, or at
least builds that use recent VC CRT libraries, VIM needs to validate the
format
On 19/08/2010 11:57, Bram Moolenaar wrote:
Mike Williams wrote:
On 18/08/2010 18:54, Sergey Khorev wrote:
It is by design in the recent VC CRT libraries (VS2005 onwards?) Any
unsupported format specifier will result in a crash. On Windows, or at
least builds that use recent VC CRT libraries,
On 18/08/2010 19:16, Benjamin R. Haskell wrote:
On Wed, 18 Aug 2010, Sergey Khorev wrote:
It is by design in the recent VC CRT libraries (VS2005 onwards?)
Any unsupported format specifier will result in a crash. On
Windows, or at least builds that use recent VC CRT libraries, VIM
needs to
F1rst! :-)
Pros: All Windows specific code.
Cons: Can't do anything clever with an invalid format string.
Should be ok with mingw32.
Wow, so quick :)
I think you've done it right by installing the handler once and for
all. For users of ancient compilers I suggest to add something like:
#if
Hi Bram!
On Mi, 18 Aug 2010, Bram Moolenaar wrote:
Christian Brabandt wrote:
On Mo, 16 Aug 2010, Christian Brabandt wrote:
Anyway, I noticed another problem. I cannot edit my .vimrc from within
gvim. When writing it, gvim simply crashes.
I found the problem. It can be
On Wed, 18 Aug 2010, Christian Brabandt wrote:
Hi Bram!
On Mi, 18 Aug 2010, Bram Moolenaar wrote:
Christian Brabandt wrote:
On Mo, 16 Aug 2010, Christian Brabandt wrote:
Anyway, I noticed another problem. I cannot edit my .vimrc from
within gvim. When writing it,
On 18/08/2010 10:09, Benjamin R. Haskell wrote:
On Wed, 18 Aug 2010, Christian Brabandt wrote:
Hi Bram!
On Mi, 18 Aug 2010, Bram Moolenaar wrote:
Christian Brabandt wrote:
On Mo, 16 Aug 2010, Christian Brabandt wrote:
Anyway, I noticed another problem. I cannot edit my .vimrc from
Am 17.08.2010 19:09, schrieb Christian Brabandt:
Hi Bram!
On Mo, 16 Aug 2010, Christian Brabandt wrote:
Anyway, I noticed another problem. I cannot edit my .vimrc from within
gvim. When writing it, gvim simply crashes.
I found the problem. It can be reproduced on Windows using this
On 18/08/2010 12:05, Mike Williams wrote:
On 18/08/2010 10:09, Benjamin R. Haskell wrote:
On Wed, 18 Aug 2010, Christian Brabandt wrote:
Hi Bram!
On Mi, 18 Aug 2010, Bram Moolenaar wrote:
Christian Brabandt wrote:
On Mo, 16 Aug 2010, Christian Brabandt wrote:
Anyway, I noticed another
It is by design in the recent VC CRT libraries (VS2005 onwards?) Any
unsupported format specifier will result in a crash. On Windows, or at
least builds that use recent VC CRT libraries, VIM needs to validate the
format string that it only contains supported format specifiers. I'm
guessing
On Wed, 18 Aug 2010, Sergey Khorev wrote:
It is by design in the recent VC CRT libraries (VS2005 onwards?)
Any unsupported format specifier will result in a crash. On
Windows, or at least builds that use recent VC CRT libraries, VIM
needs to validate the format string that it only
Mike Williams wrote:
On 18/08/2010 10:09, Benjamin R. Haskell wrote:
On Wed, 18 Aug 2010, Christian Brabandt wrote:
Hi Bram!
On Mi, 18 Aug 2010, Bram Moolenaar wrote:
Christian Brabandt wrote:
On Mo, 16 Aug 2010, Christian Brabandt wrote:
Anyway, I noticed another
On Tue, 17 Aug 2010, Christian Brabandt wrote:
Hi Bram!
On Mo, 16 Aug 2010, Christian Brabandt wrote:
Anyway, I noticed another problem. I cannot edit my .vimrc from
within gvim. When writing it, gvim simply crashes.
I found the problem. It can be reproduced on Windows using this
Hi everybody,
gvim -u NONE -U NONE -N -c echo strftime('%a %Y\-%m\-%d %R')
Which gvim version is this with?
With the distributed gvim 7.3 invoked from MS-DOS (in Windows XP),
I get the error.
AppName: gvim.exeAppVer: 7.3.277.0 ModName: gvim.exe
ModVer: 7.3.277.0Offset:
Hi Bram!
On So, 15 Aug 2010, Bram Moolenaar wrote:
Announcing: Vim (Vi IMproved) version 7.3
[…]
I think I found an error with the Windows builds. All messages that are
given, can't be displayed correctly, when they contain umlauts:
e.g.
E474: Ungfcltiges Argument
which should have been
Christian Brabandt wrote:
On So, 15 Aug 2010, Bram Moolenaar wrote:
Announcing: Vim (Vi IMproved) version 7.3
[…]
I think I found an error with the Windows builds. All messages that are
given, can't be displayed correctly, when they contain umlauts:
e.g.
E474: Ungfcltiges Argument
Hi Bram!
On Mo, 16 Aug 2010, Bram Moolenaar wrote:
Christian Brabandt wrote:
On So, 15 Aug 2010, Bram Moolenaar wrote:
Announcing: Vim (Vi IMproved) version 7.3
[…]
I think I found an error with the Windows builds. All messages that are
given, can't be displayed correctly,
Trying to cross-compile, but this breaks:
checking uint32_t is 32 bits... configure: error: could not compile program
using uint32_t.
Note that this error message is misleading. The program compiles just fine.
It simply won't run because it's built for the wrong architecture.
Not sure if
On 8/16/10 3:17 PM, Philip Prindeville wrote:
Trying to cross-compile, but this breaks:
checking uint32_t is 32 bits... configure: error: could not compile program
using uint32_t.
Note that this error message is misleading. The program compiles just fine.
It simply won't run because it's
Hello Vim users,
Announcing: Vim (Vi IMproved) version 7.3
This is a minor release of Vim. It consists of Vim 7.2 plus all
patches, updated runtime files and some more, see below. It has been
two years since the 7.2 release, thus it's not that minor. But not
major either. Something in
26 matches
Mail list logo
