public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Thorsten Kampe <thorsten@thorstenkampe.de>
To: cygwin@cygwin.com
Subject: Re: python and cygwin
Date: Sat, 21 Feb 2004 01:25:00 -0000	[thread overview]
Message-ID: <1amf6c54ignfm.dlg@thorstenkampe.de> (raw)
In-Reply-To: <c1658e$jsc$1@sea.gmane.org>

* Totte Karlsson (2004-02-21 00:29 +0100)
> OK, I see, However, it seems as if I can execute the win32 python
> interpreter from within the cygwin bash shell, and it seems to work
> as long the cygwin path come into play, which is "unfortunate". 
> 
> I thought the idea with cygwin was to provide unix tools working
> under windows,

Exactly. That's why you need the python binary for Cygwin. 

> not to make windows into unix/posix?

I hope at least you know what you mean by that. 

> Now it looks as if I need to have two sets of python running, one
> for cygwin and one for windows,

In fact you don't, as long as you translate Posix paths to Windows
(via "cygpath -w"). Many Cygwin utilities also understand Windows
paths ("cd 'C:\', "cd C:/", etc).

> 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).


Thorsten


--
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/

  parent reply	other threads:[~2004-02-21  0:33 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 [this message]
2004-02-21  2:29         ` Totte Karlsson
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=1amf6c54ignfm.dlg@thorstenkampe.de \
    --to=thorsten@thorstenkampe.de \
    --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).