X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-1.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,KHOP_THREADED,NML_ADSP_CUSTOM_MED,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL
X-Spam-Check-By:	sourceware.org
X-Belgacom-Dynamic:	yes
X-IronPort-Anti-Spam-Filtered:	true
X-IronPort-Anti-Spam-Result:	Ai8qAJn57k9tgLm1/2dsb2JhbABFgj+Fap1JlAMBAQUyAQUkHAEQCwsNCRYPCQMCAQIBESYBDRMBBwKHeAESB6knh2YKGYELiHeOOYMcA5U0gRKOcYJh
Message-ID:	<4FEEFA89.6000409@gmail.com>
Date:	Sat, 30 Jun 2012 15:09:29 +0200
From:	Tony Mechelynck <antoine DOT mechelynck AT gmail DOT com>
User-Agent:	Mozilla/5.0 (X11; Linux x86_64; rv:16.0) Gecko/16.0 Firefox/16.0 SeaMonkey/2.13a1
MIME-Version:	1.0
To:	vim_use AT googlegroups DOT com
CC:	ping <songpingemail AT gmail DOT com>, cygwin AT cygwin DOT com,
	Vlad Irnov <vlad DOT irnov AT gmail DOT com>
Subject:	Re: vim/cygwin: python support
References:	<4FEDBA31 DOT 4060104 AT gmail DOT com>
In-Reply-To:	<4FEDBA31.4060104@gmail.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On 29/06/12 16:22, ping wrote:
> not sure this should go to vim/cygwin team...so copy both and Vlad(Voom
> plugin author)
> I got a new laptop (folio) come with win7.
> for some reason I want to give win7 a trial.
>
> cygwin full install went smooth.
> but looks I don't have python support here.
> that means I won't be able to have some plugins (like Voom) that is
> based on python.
> I did a lot of search and looks this is a common issue, but still I
> don't see a clear answer yet.
> any cygwin users can advise?
>
> regards
> ping

When I was still on Windows, I used to have some Cygwin packages 
installed, but the Python I used (and compiled Vim with, using the 
make_cyg.mak and the Cygwin/MinGW gcc) was not from Cygwin but from 
python.org itself. See 
http://users.skynet.be/antoine.mechelynck/vim/compile.htm for details.

The vim.exe and gvim.exe which I made that way were _built_ under Cygwin 
but not for _use_ under Cygwin — they were for use under Windows from a 
desktop icon or a cmd.exe prompt, and did not use the cygwin1.dll 
library. Also, Win64 was still a thing of the future at the time.

DISCLAIMER: The HowTo page mentioned two paragraphs above is about 1½ 
years old, and since I have left Windows forever I cannot check if it is 
still accurate. However, even if it isn't, a "clever user" ought to be 
able to fill in the gaps.


Best regards,
Tony.
-- 
Ask not for whom the <CONTROL-G> tolls.



--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -