From: Tony Mechelynck <antoine.mechelynck@gmail.com>
To: vim_use@googlegroups.com
Cc: ping <songpingemail@gmail.com>,
cygwin@cygwin.com, Vlad Irnov <vlad.irnov@gmail.com>
Subject: Re: vim/cygwin: python support
Date: Sat, 30 Jun 2012 13:09:00 -0000 [thread overview]
Message-ID: <4FEEFA89.6000409@gmail.com> (raw)
In-Reply-To: <4FEDBA31.4060104@gmail.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
next prev parent reply other threads:[~2012-06-30 13:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4FEDBA31.4060104@gmail.com>
2012-06-29 14:26 ` ping
2012-06-29 15:06 ` Ryan Johnson
2012-06-29 15:43 ` ping
2012-06-29 20:50 ` ping
2012-06-30 13:09 ` Tony Mechelynck [this message]
[not found] <1198556727-1341091933-cardhu_decombobulator_blackberry.rim.net-741837253-@b12.c30.bise6.blackberry>
2012-06-30 22:04 ` Tony Mechelynck
2012-07-01 5:11 ` ping
2012-07-01 23:20 ` Andrey Repin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4FEEFA89.6000409@gmail.com \
--to=antoine.mechelynck@gmail.com \
--cc=cygwin@cygwin.com \
--cc=songpingemail@gmail.com \
--cc=vim_use@googlegroups.com \
--cc=vlad.irnov@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).