hi,
just wondering what would be lost if vim's own mainloop was replaced
by or at least properly integrated with the glib mainloop
as it would help to integrate things like gio (direct ssh/http file
access) and dbus
also the current way to deal with gtk and its mainloop seems like a
big hack
Hello,
We've rebuilt all Fedora-12 packages and vim was one of the programs
that failed to
run with enhanced glibc fortify features:
vi
*** buffer overflow detected ***: vim terminated
=== Backtrace: =
/lib64/libc.so.6(__fortify_fail+0x37)[0x7f780f90df47]
Karsten Hopp wrote:
We've rebuilt all Fedora-12 packages and vim was one of the programs
that failed to
run with enhanced glibc fortify features:
vi
*** buffer overflow detected ***: vim terminated
=== Backtrace: =
/lib64/libc.so.6(__fortify_fail+0x37)[0x7f780f90df47]
Bram Moolenaar wrote:
Karsten Hopp wrote:
We've rebuilt all Fedora-12 packages and vim was one of the programs
that failed to
run with enhanced glibc fortify features:
vi
*** buffer overflow detected ***: vim terminated
=== Backtrace: =
Am 04.08.2009 14:59, schrieb Dominique Pellé:
Bram Moolenaar wrote:
Karsten Hopp wrote:
We've rebuilt all Fedora-12 packages and vim was one of the programs
that failed to
run with enhanced glibc fortify features:
vi
*** buffer overflow detected ***: vim terminated
===
Karsten Hopp wrote:
Am 04.08.2009 14:59, schrieb Dominique Pellé:
Bram Moolenaar wrote:
Karsten Hopp wrote:
We've rebuilt all Fedora-12 packages and vim was one of the programs
that failed to
run with enhanced glibc fortify features:
vi
*** buffer overflow
On Tue, Aug 04, 2009 at 05:54:58PM +0200, Karsten Hopp wrote:
and we were using -D_FORTIFY_SOURCE=2 to compile vim as you've already
suspected.
Actually, you're using -Wp,-D_FORTIFY_SOURCE=2 instead of simply
-D_FORTIFY_SOURCE=2. I'd take a guess that's the issue because
otherwise the later
Bram Moolenaarb...@moolenaar.net wrote:
Karsten Hopp wrote:
Am 04.08.2009 14:59, schrieb Dominique Pellé:
Bram Moolenaar wrote:
Karsten Hopp wrote:
We've rebuilt all Fedora-12 packages and vim was one of the programs
that failed to
run with enhanced glibc fortify features:
On Tue, Aug 4, 2009 at 9:13 PM, Bram Moolenaar wrote:
Hello,
The build log is available at
http://kojipkgs.fedoraproject.org/packages/vim/7.2.245/1.fc12/data/logs/i686/build.log
and we were using -D_FORTIFY_SOURCE=2 to compile vim as you've already
suspected.
This compile option comes
Hello,
I very much like the version of vim for gtk2.0, because it looks a
little better than the other versions of vim.
So my question is, if it is possible to get vim-gtk2.0 for Windows?
It should look something like this:
http://www.opensky.ca/~jdhildeb/software/gnome-vim/gvim-gtk2.0.png
(I
On Tue, Aug 4, 2009 at 5:03 PM, AndreasRandre...@pvv.ntnu.no wrote:
It should look something like this:
http://www.opensky.ca/~jdhildeb/software/gnome-vim/gvim-gtk2.0.png
It wouldn't look like that under Windows, since gtk uses the native
widgits. So it would look an awful lot like gvim for
11 matches
Mail list logo