I was at work last week and I was programming.
I found a bug in c/c++ comment highlighting with syntax on.
I replaced all [[:alnum:]] characters with A character. In this way
I can submit it to this group.
How can I submit my c/c++ like file to show the bug?
There seems to be an edge case when positioning the cursor and
'virtualedit' is set to all that causes gvim to crash. This was
introduced between 6.4 and 7.0b.
It can be reproduced using the attached files as follows:
gvim -u NONE -N -S crash.vim crash.txt
If the last jump in crash.vim is
On 07/03/09 22:30, James Vega wrote:
There seems to be an edge case when positioning the cursor and
'virtualedit' is set to all that causes gvim to crash. This was
introduced between 6.4 and 7.0b.
It can be reproduced using the attached files as follows:
What attached files?
gvim -u
On Sat, Mar 07, 2009 at 04:30:30PM -0500, James Vega wrote:
There seems to be an edge case when positioning the cursor and
'virtualedit' is set to all that causes gvim to crash. This was
introduced between 6.4 and 7.0b.
It can be reproduced using the attached files as follows:
gvim -u
On Sat, Mar 7, 2009 at 12:35 PM, Tony Mechelynck wrote:
That's if you want Vim for Cygwin. You can also use Cygwin to compile
(cross-compile, if you want) versions of Vim which don't need Cygwin
to run, as explained on my Windows HowTo
Hm. Support for using cygwin's gcc to do cross-compile
On Sat, 2009-03-07 at 20:35 -0500, Matt Wozniski wrote:
Hm. Support for using cygwin's gcc to do cross-compile builds is
soon to be dropped.
Why?!
Maybe we should remove the option to do this from Make_cyg.mak? Or,
at least add a note to the README noting that the option is
deprecated
On 08/03/09 02:35, Matt Wozniski wrote:
On Sat, Mar 7, 2009 at 12:35 PM, Tony Mechelynck wrote:
That's if you want Vim for Cygwin. You can also use Cygwin to compile
(cross-compile, if you want) versions of Vim which don't need Cygwin
to run, as explained on my Windows HowTo
Hm. Support
On Sat, Mar 7, 2009 at 9:05 PM, Tony Mechelynck wrote:
On 08/03/09 02:35, Matt Wozniski wrote:
On Sat, Mar 7, 2009 at 12:35 PM, Tony Mechelynck wrote:
That's if you want Vim for Cygwin. You can also use Cygwin to compile
(cross-compile, if you want) versions of Vim which don't need Cygwin
On Sun, 2009-03-08 at 03:05 +0100, Tony Mechelynck wrote:
The only interest of Make_cyg.mak is to compile Vim binaries which
don't need Cygwin to run, using the -mno-cygwin option of the
Cygwin gcc compiler and the appropriate corresponding option of the
linker.
Hmm, I use only:
make
On 08/03/09 03:15, Matt Wozniski wrote:
On Sat, Mar 7, 2009 at 9:05 PM, Tony Mechelynck wrote:
On 08/03/09 02:35, Matt Wozniski wrote:
On Sat, Mar 7, 2009 at 12:35 PM, Tony Mechelynck wrote:
That's if you want Vim for Cygwin. You can also use Cygwin to compile
(cross-compile, if you want)
On Sat, Mar 7, 2009 at 9:32 PM, Tony Mechelynck wrote:
On 08/03/09 03:15, Matt Wozniski wrote:
On Sat, Mar 7, 2009 at 9:05 PM, Tony Mechelynck wrote:
using the -mno-cygwin option of the Cygwin gcc
compiler and the appropriate corresponding option of the linker.
This option will be removed
On Sat, Mar 7, 2009 at 10:29 PM, Tony Mechelynck wrote:
On 08/03/09 03:49, Matt Wozniski wrote:
On Sat, Mar 7, 2009 at 9:32 PM, Tony Mechelynck wrote:
[...]
The _option_ to compile native-Windows programs
using Cygwin gcc _is_ a useful thing, I can't imagine on what grounds
someone would
On 08/03/09 04:40, Matt Wozniski wrote:
[...]
Huh? They do different things. Cygwin provides a POSIX emulation
layer through cygwin1.dll, mingw provides mappings from POSIX concepts
to Windows concepts to try to make it possible to cross-compile POSIX
applications. What's there to be
On Sat, Mar 7, 2009 at 9:21 PM, Steve Hall wrote:
On Sun, 2009-03-08 at 03:05 +0100, Tony Mechelynck wrote:
The only interest of Make_cyg.mak is to compile Vim binaries which
don't need Cygwin to run, using the -mno-cygwin option of the
Cygwin gcc compiler and the appropriate corresponding
14 matches
Mail list logo
