Trying to compile the latest vim 7.3a (74c8bba1d9e8) I get the following
error (the empty line after the command-line is an artefact to make it
more readable):
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK
-I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include -I/usr/include/atk-1.0
On 18/05/10 09:55, Tony Mechelynck wrote:
[...]
/usr/include/stdint.h:31|#ifndef __uint32_t_defined
/usr/include/stdint.h:32|typedef unsigned int uint32_t;
/usr/include/stdint.h:33|# define __uint32_t_defined
these are of course lines 51 to 53
Looks like the new encryption subsystem
I'm getting the same/similar build error as well on ArchLinux
compiling vim 7.3a (74c8bba1d9e8):
gcc -c -I. -Iproto -DHAVE_CONFIG_H -march=native -mtune=native -O2
-pipe -D_FORTIFY_SOURCE=1-D_REENTRANT -D_GNU_SOURCE -fstack-
protector -I/usr/local/include -D_LARGEFILE_SOURCE -
Hey, i've noticed some people saying on IRC and randomly throughout the web
in places that the whole:
link.sh: We don't need libXt!
link.sh: Removing libXt!
thing is a bit scary if you're new to compiling vim or compiling stuff on
linux in general because you might think its actually going to
On 18/05/10 11:12, JD wrote:
I'm getting the same/similar build error as well on ArchLinux
compiling vim 7.3a (74c8bba1d9e8):
gcc -c -I. -Iproto -DHAVE_CONFIG_H -march=native -mtune=native -O2
-pipe -D_FORTIFY_SOURCE=1-D_REENTRANT -D_GNU_SOURCE -fstack-
protector -I/usr/local/include
On 18/05/2010 03:43 a.m., Bram Moolenaar wrote:
Cesar Romani wrote:
I got following error:
gobjZ/ex_docmd.o:ex_docmd.c:(.text+0x1116c): undefined reference to
`blowfish_self_test'
gobjZ/fileio.o:fileio.c:(.text+0x704f): undefined reference to
`blowfish_self_test'
On 18/05/2010 07:37 a.m., Cesar Romani wrote:
On 18/05/2010 03:43 a.m., Bram Moolenaar wrote:
Cesar Romani wrote:
I got following error:
gobjZ/ex_docmd.o:ex_docmd.c:(.text+0x1116c): undefined reference to
`blowfish_self_test'
On 18/05/10 11:24, Jeff Horelick wrote:
Hey, i've noticed some people saying on IRC and randomly throughout the
web in places that the whole:
link.sh: We don't need libXt!
link.sh: Removing libXt!
thing is a bit scary if you're new to compiling vim or compiling stuff
on linux in general
On Tue, May 18, 2010 at 11:04 AM, Cesar Romani wrote:
On 18/05/2010 04:24 a.m., Jeff Horelick wrote:
Hey, i've noticed some people saying on IRC and randomly throughout the
web in places that the whole:
link.sh: We don't need libXt!
link.sh: Removing libXt!
thing is a bit scary if you're
Cesar Romani wrote:
On 18/05/2010 04:24 a.m., Jeff Horelick wrote:
Hey, i've noticed some people saying on IRC and randomly throughout the
web in places that the whole:
link.sh: We don't need libXt!
link.sh: Removing libXt!
thing is a bit scary if you're new to compiling vim or compiling
On 2010-05-18, Matt Wozniski wrote:
On Tue, May 18, 2010 at 11:04 AM, Cesar Romani wrote:
On 18/05/2010 04:24 a.m., Jeff Horelick wrote:
Hey, i've noticed some people saying on IRC and randomly throughout the
web in places that the whole:
link.sh: We don't need libXt!
link.sh:
Hi
When pressing g8 in normal mode on the NUL character 00,
Vim-7.3 (and older) displays 0a. It should display 00. The :ascii
Ex command correctly displays 00.
Steps to reproduce:
1) Create a file with NUL char in it:
$ perl -e 'print chr(0)' test.txt
2) Run:
$ vim -u NONE -c :set
Gary Johnson wrote:
On 2010-05-18, Matt Wozniski wrote:
On Tue, May 18, 2010 at 11:04 AM, Cesar Romani wrote:
On 18/05/2010 04:24 a.m., Jeff Horelick wrote:
Hey, i've noticed some people saying on IRC and randomly throughout the
web in places that the whole:
link.sh: We don't
Tony Mechelynck wrote:
Trying to compile the latest vim 7.3a (74c8bba1d9e8) I get the following
error (the empty line after the command-line is an artefact to make it
more readable):
gcc -c -I. -Iproto -DHAVE_CONFIG_H -DFEAT_GUI_GTK
-I/usr/include/gtk-2.0 -I/usr/lib/gtk-2.0/include
Cesar Romani wrote:
On 18/05/2010 03:43 a.m., Bram Moolenaar wrote:
Cesar Romani wrote:
I got following error:
gobjZ/ex_docmd.o:ex_docmd.c:(.text+0x1116c): undefined reference to
`blowfish_self_test'
gobjZ/fileio.o:fileio.c:(.text+0x704f):
On Tue, May 18, 2010 at 9:06 PM, Bram Moolenaar b...@moolenaar.net wrote:
Tony Mechelynck wrote:
Trying to compile the latest vim 7.3a (74c8bba1d9e8) I get the following
error (the empty line after the command-line is an artefact to make it
more readable):
gcc -c -I. -Iproto
2010/5/18 Dominique Pellé dominique.pe...@gmail.com:
On Tue, May 18, 2010 at 9:06 PM, Bram Moolenaar b...@moolenaar.net wrote:
Tony Mechelynck wrote:
Trying to compile the latest vim 7.3a (74c8bba1d9e8) I get the following
error (the empty line after the command-line is an artefact to make
Tony Mechelynck, 2010-05-16 18:09:
for instance on my local
repository there's one additional revision every time I fetch the
source (if there is a change in one or more of src/version.c,
src/Makefile, src/eval.c or src/feature.h)
A few days ago I told you that it has *nothing* to do with
On Tue, May 18, 2010 at 9:46 PM, James Vega james...@jamessan.com wrote:
2010/5/18 Dominique Pellé dominique.pe...@gmail.com:
On Tue, May 18, 2010 at 9:06 PM, Bram Moolenaar b...@moolenaar.net wrote:
Tony Mechelynck wrote:
Trying to compile the latest vim 7.3a (74c8bba1d9e8) I get the
Jeff Horelick wrote:
Hey, i've noticed some people saying on IRC and randomly throughout
the web in places that the whole:
link.sh: We don't need libXt!
link.sh: Removing libXt!
thing is a bit scary if you're new to compiling vim or compiling stuff on
linux in general because you might
Cesar Romani wrote:
On 18/05/2010 07:37 a.m., Cesar Romani wrote:
On 18/05/2010 03:43 a.m., Bram Moolenaar wrote:
Cesar Romani wrote:
I got following error:
gobjZ/ex_docmd.o:ex_docmd.c:(.text+0x1116c): undefined reference to
2010/5/18 Dominique Pellé dominique.pe...@gmail.com:
On Tue, May 18, 2010 at 9:46 PM, James Vega james...@jamessan.com wrote:
2010/5/18 Dominique Pellé dominique.pe...@gmail.com:
On Tue, May 18, 2010 at 9:06 PM, Bram Moolenaar b...@moolenaar.net wrote:
Then we could not use the autoconf
On May 18, 4:29 pm, Bram Moolenaar b...@moolenaar.net wrote:
Jeff Horelick wrote:
Hey, i've noticed some people saying on IRC and randomly throughout
the web in places that the whole:
link.sh: We don't need libXt!
link.sh: Removing libXt!
thing is a bit scary if you're new to
On Tue, May 18, 2010 at 4:37 PM, James Vega james...@jamessan.com wrote:
2010/5/18 Dominique Pellé dominique.pe...@gmail.com:
On Tue, May 18, 2010 at 9:46 PM, James Vega james...@jamessan.com wrote:
2010/5/18 Dominique Pellé dominique.pe...@gmail.com:
On Tue, May 18, 2010 at 9:06 PM, Bram
Am 23.03.2010 16:27, schrieb Bram Moolenaar:
Patch 7.2.407
Problem:When using an expression in :s backslashes in the result are
dropped. (Sergey Goldgaber, Christian Brabandt)
Solution: Double backslashes.
Files: src/regexp.c
I found a bug (two lines of text below):
James Vega wrote:
2010/5/18 Dominique Pellé dominique.pe...@gmail.com:
On Tue, May 18, 2010 at 9:46 PM, James Vega james...@jamessan.com wrote:
2010/5/18 Dominique Pellé dominique.pe...@gmail.com:
On Tue, May 18, 2010 at 9:06 PM, Bram Moolenaar b...@moolenaar.net
wrote:
Then we
On Tue, May 18, 2010 at 4:29 PM, Bram Moolenaar b...@moolenaar.net wrote:
Cesar Romani wrote:
On 18/05/2010 07:37 a.m., Cesar Romani wrote:
On 18/05/2010 03:43 a.m., Bram Moolenaar wrote:
Cesar Romani wrote:
I got following error:
While trying to compile Vim 7.3a from Hg under Windows (which worked
fine a few hours ago) with Visual Studio 2008, I receive the
following errors:
http://pastebin.com/G3XxEsqN
Compilation command:
nmake -f Make_mvc.mak GUI=yes OLE=yes PERL=C:\Perl
On 18/05/10 22:42, JD wrote:
[...]
They're also likely the type of people who own the Brooklyn Bridge
(does that joke work outside the US?).
I'm Belgian, and I've met it before, so maybe it does.
Omit sounds quite good to me. I used delinking because I was sort of
under the impression that
I couldn't resist:
I used github because it works best and fastest for me:
http://github.com/MarcWeber/SmartTag
I also moved code and renamed SmartTag to SmartTag#SmartTag
When enabling tagfunc by setting to SmartTag or SmartTag#SmartTag should
tjump show only one match as well? This didn't
On 18/05/10 22:59, Bram Moolenaar wrote:
Dominique Pelle wrote:
Then we could not use the autoconf check, it always defines uint32_t.
I'll undefine uint32_t in vim.h, like it's done for netbeans.
The same kind of error still happens when compiling if_python.c:
In file included from
On 18 May 2010 16:29, Bram Moolenaar wrote:
Strange that these compilers don't define uint32_t. I'll add it in
vim.h:
Unfortunately revision 2184 seems to have broken Cygwin compilation
with complaints of uint32_t being undefined.
Chris
--
Chris Sutcliffe
http://emergedesktop.org
Bram Moolenaar wrote:
James Vega wrote:
2010/5/18 Dominique Pellé dominique.pe...@gmail.com:
On Tue, May 18, 2010 at 9:46 PM, James Vega james...@jamessan.com wrote:
2010/5/18 Dominique Pellé dominique.pe...@gmail.com:
On Tue, May 18, 2010 at 9:06 PM, Bram Moolenaar b...@moolenaar.net
33 matches
Mail list logo
