Hello,
I'm moving back from Emacs to Vim, but see that there is no Python enabled
since: echo has("python") gives 0, although I see there is the following
snippet in Makefile:
.if defined(WITH_PYTHON)
USE_PYTHON= yes
MAKE_ARGS+= CONF_OPT_PYTHON="--enable-pythoninterp"
.endif
Can anyone
On Sat, May 28, 2011 at 9:24 AM, Gour-Gadadhara Dasa wrote:
> Hello,
>
> I'm moving back from Emacs to Vim, but see that there is no Python enabled
> since: echo has("python") gives 0, although I see there is the following
> snippet in Makefile:
>
> .if defined(WITH_PYTHON)
> USE_PYTHON= yes
>
On Sat, 28 May 2011 11:23:32 +0100
Florent Thoumie wrote:
> You can rebuild the port with WITH_PYTHON=yes.
Thank you.
How is it that there is no 'make config' menu to choose options from?
Sincerely,
Gour
--
“In the material world, conceptions of good and bad are
all mental speculations…” (
On Sat, 28 May 2011 13:00:41 +0200
Gour-Gadadhara Dasa wrote:
> On Sat, 28 May 2011 11:23:32 +0100
> Florent Thoumie wrote:
>
> > You can rebuild the port with WITH_PYTHON=yes.
>
> Thank you.
>
> How is it that there is no 'make config' menu to choose options from?
IIRC the maintainer object
> How is it that there is no 'make config' menu to choose options from?
This has come up multiple times on this mailing list. The maintainer
dislikes the options system and has hidden vim's options behind a
variable "WITH_VIM_OPTIONS"
add WITH_VIM_OPTIONS="YES" to /etc/make.conf to have it act lik
On Sat, 28 May 2011 11:44:07 +
Eitan Adler wrote:
> This has come up multiple times on this mailing list. The maintainer dislikes
> the options system and has hidden vim's options behind a variable
> "WITH_VIM_OPTIONS" add WITH_VIM_OPTIONS="YES" to /etc/make.conf to have it
> act like other p
On Sat, May 28, 2011 at 12:22 PM, RW wrote:
> On Sat, 28 May 2011 13:00:41 +0200
> Gour-Gadadhara Dasa wrote:
>
>> On Sat, 28 May 2011 11:23:32 +0100
>> Florent Thoumie wrote:
>>
>> > You can rebuild the port with WITH_PYTHON=yes.
>>
>> Thank you.
>>
>> How is it that there is no 'make config' m
On Sat, May 28, 2011 at 11:44:07AM +, Eitan Adler wrote:
> > How is it that there is no 'make config' menu to choose options from?
>
> This has come up multiple times on this mailing list. The maintainer
> dislikes the options system and has hidden vim's options behind a
> variable "WITH_VIM_O
On Sat, 28 May 2011 12:38:13 +0100
Florent Thoumie wrote:
> There's a WITH_VIM_OPTIONS option, but if you select PYTHON it won't
> now.
Yeah, just experienced that menu options do not have effect.
Sincerely,
Gour
--
“In the material world, conceptions of good and bad are
all mental speculat
# uname -a
FreeBSD home.encontacto.net 9.0-CURRENT FreeBSD 9.0-CURRENT #206: Wed
May 18 05:29:44 CDT 2011
r...@home.encontacto.net:/usr/obj/usr/src/sys/ENCONTACTO i386
snd_atiixp.ko loaded and works fine with everything except skype.
My linux stuff is up to date AFAIK All ports are up
On 28 May 2011 14:25, eculp wrote:
> # uname -a
> FreeBSD home.encontacto.net 9.0-CURRENT FreeBSD 9.0-CURRENT #206: Wed May 18
> 05:29:44 CDT 2011
> r...@home.encontacto.net:/usr/obj/usr/src/sys/ENCONTACTO i386
>
> snd_atiixp.ko loaded and works fine with everything except skype.
>
> My linux stu
on 18/05/2011 12:10 O. Hartmann said the following:
> ---
> Oh dear - something failed during the build - sorry !
> For more help with debugging build errors, please see the section in:
> http://wiki.documentfoundation.org/Devel
On Sat, May 28, 2011 at 11:13 AM, Chris Rees wrote:
> On 28 May 2011 14:25, eculp wrote:
>> # uname -a
>> FreeBSD home.encontacto.net 9.0-CURRENT FreeBSD 9.0-CURRENT #206: Wed May 18
>> 05:29:44 CDT 2011
>> r...@home.encontacto.net:/usr/obj/usr/src/sys/ENCONTACTO i386
>>
>> snd_atiixp.ko loaded
2011/5/28 O. Hartmann :
>
>
> on 18/05/2011 12:10 O. Hartmann said the following:
>> ---
>> Oh dear - something failed during the build - sorry !
>> For more help with debugging build errors, please see the section in:
>> http://wi
on 28/05/2011 21:01 O. Hartmann said the following:
> Hello.
>
> I tried the advice. Several times on three different machines running FBSD
> 9.0-CURRENT/amd64.
> It's always the same, build process stops at the same error message as shown
> above.
My point was that you should be able to see rea
On 28 May 2011 19:26, "Edwin L. Culp W." wrote:
>
> On Sat, May 28, 2011 at 11:13 AM, Chris Rees wrote:
> > On 28 May 2011 14:25, eculp wrote:
> >> # uname -a
> >> FreeBSD home.encontacto.net 9.0-CURRENT FreeBSD 9.0-CURRENT #206: Wed
May 18
> >> 05:29:44 CDT 2011
> >> r...@home.encontacto.net:/u
On Sat, 2011-05-28 at 21:16 +0100, Chris Rees wrote:
> On 28 May 2011 19:26, "Edwin L. Culp W." wrote:
> >
> > On Sat, May 28, 2011 at 11:13 AM, Chris Rees wrote:
> > > On 28 May 2011 14:25, eculp wrote:
> > >> # uname -a
> > >> FreeBSD home.encontacto.net 9.0-CURRENT FreeBSD 9.0-CURRENT #206: W
On Sat, 28 May 2011 22:14:34 -0400
Jason Hellenthal wrote:
> It should be noted here that the WITH_VIM_OPTIONS and WITH_OPTIONS
> vars still will not have an effect on vim. I currently have
> WITH_OPTIONS defined globally and it does not effect the outcome of
> vim as python is still not enabled.
18 matches
Mail list logo