From: "Totte Karlsson" <tkarlsson@qm.com>
To: cygwin@cygwin.com
Subject: Re: python and cygwin
Date: Sat, 21 Feb 2004 02:29:00 -0000 [thread overview]
Message-ID: <c16d7u$2ck$1@sea.gmane.org> (raw)
In-Reply-To: <1amf6c54ignfm.dlg@thorstenkampe.de>
I guess the problem is, as I see it, if cygwin was the "perfect" unix tool
running under windows, it would integrate with existing windows tools. It
does that to some extent, but not fully and that is the problem. If I want a
pure unix environment, on the other hand, then I would use the real stuff,
such as Linux or qnx on which I do most of my work... but nothing is perfect
as we know..
When I open up a "cygwin-bash" on windows, I just thought that I could use
my already installed "win-32" python. I realize now that you can't and I
think that creates problems. As a programmer I don't like do have to
duplicate things. I only want one "repository".
> > and both are running in windows!
>
> No, one runs in Windows and the other one under Cygwin. You can always
> run the Cygwin binaries from Windows (ls, d, etc. work for me in a
> Windows cmd.exe console window). Many Windows binaries work *directly*
> in Cygwin bash or zsh (also much slower, so it's wise to execute them
> in a cmd subshell).
>
It sounds as if you are talking about cygwin as an operating system, on
which you can run cygwin applications. Sounds weird, they are all running on
windows as far as I can see.. at least on my machine.
cheers
/tk
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2004-02-21 1:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-20 22:33 Totte Karlsson
2004-02-20 22:53 ` Totte Karlsson
2004-02-20 23:20 ` Brian Dessent
2004-02-20 23:39 ` Totte Karlsson
2004-02-21 0:00 ` Brian Dessent
2004-02-21 1:25 ` Thorsten Kampe
2004-02-21 2:29 ` Totte Karlsson [this message]
2004-02-21 2:36 ` Norman Vine
2004-02-21 2:38 ` Thorsten Kampe
2004-02-21 3:10 ` Larry Hall
2004-02-22 19:29 ` Yitzchak Scott-Thoennes
2004-02-22 20:09 ` Larry Hall
2004-02-22 22:15 ` Yitzchak Scott-Thoennes
2004-02-20 23:54 DePriest, Jason R.
2004-02-21 0:01 ` Igor Pechtchanski
2004-02-21 0:26 ` Christopher Faylor
2004-02-21 18:45 Totte Karlsson
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='c16d7u$2ck$1@sea.gmane.org' \
--to=tkarlsson@qm.com \
--cc=cygwin@cygwin.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).