Mail Archives: cygwin/2004/02/20/19:34:05
* 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/
- Raw text -