2009/2/22 Danek Duvall:
On Sun, Feb 22, 2009 at 07:04:08PM +0100, bj�rn wrote:
Well, this is turning out to be quite complicated. After quite a bit
of searching I found that passing
-dynamic -undefined suppress -flat_namespace
when linking if_python.so gets rid of all those error
2009/2/17 Danek Duvall:
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
On Sun, Feb 22, 2009 at 07:04:08PM +0100, bj�rn wrote:
Well, this is turning out to be quite complicated. After quite a bit
of searching I found that passing
-dynamic -undefined suppress -flat_namespace
when linking if_python.so gets rid of all those error messages. So
the relevant
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
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 vim
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 different
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
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, so I
So here's a re-work that should allow for dynamic loading on platforms
other than Solaris. The autoconf bits are tuned for Solaris, but change
-Kpic to -fpic, -G to -shared, and SunOS to Linux, and I think it might
work, or at least come close.
The difference here is that if_python.c itself is
On 2/15/09, Danek Duvall duv...@comfychair.org wrote:
snip
If
there are any Python script torture tests I should run, let me know; I'm
not sure what the best python scripts are to play with.
You could play with the distributed Python omni completion:
autoload/pythoncomplete.vim
snip
Danek Duvall wrote:
I've been wanting to code this up for a while, and almost had it a while
back, but couldn't quite get it working, and put it aside until today.
It's not ready for integration, since it's not at all tied into the
autoconf setup, and requires that you modify
On Sun, Feb 15, 2009 at 02:57:35PM +0100, Bram Moolenaar wrote:
I haven't looked at the patch yet, but I would like to encourage others
to help make this work for as many systems as possible. It's so much
nicer when Vim can be build with Python and the binary distributed to
systems where
On Sun, Feb 15, 2009 at 09:02:15PM +1100, Doug Kearns wrote:
On 2/15/09, Danek Duvall duv...@comfychair.org wrote:
If there are any Python script torture tests I should run, let me
know; I'm not sure what the best python scripts are to play with.
You could play with the distributed
Okay, I've hacked configure.in to make it possible to do this from
configure. The patch is attached. It applies only on top of my previous
patch, as it passes the python library name in as a define. This is gross,
but it gets the job done for now.
Thanks,
Danek
I've been wanting to code this up for a while, and almost had it a while
back, but couldn't quite get it working, and put it aside until today.
It's not ready for integration, since it's not at all tied into the
autoconf setup, and requires that you modify src/auto/config.mk to add
15 matches
Mail list logo
