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
--~--~-~--~~
On Sun, Feb 15, 2009 at 09:02:15PM +1100, Doug Kearns wrote:
> On 2/15/09, Danek Duvall 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 Python omni com
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
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 src/auto
On 2/15/09, Danek Duvall 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 Python omni completion:
autoload/pythoncomplete.vim
Regards,
Doug
--~--~
