* Thorsten Kampe (Tue, 1 May 2007 20:49:59 +0100)
> * Brian Dessent (Tue, 01 May 2007 12:25:15 -0700)
> > Thorsten Kampe wrote:
> > > What about this "winsymlinks" Cygwin environment variable? The
> > > description says "if set, Cygwin creates symlinks as Windows shortcuts
> > > with a special head
* Brian Dessent (Tue, 01 May 2007 12:25:15 -0700)
> Thorsten Kampe wrote:
> > What about this "winsymlinks" Cygwin environment variable? The
> > description says "if set, Cygwin creates symlinks as Windows shortcuts
> > with a special header and the R/O attribute set. If not set, Cygwin
> > creates
Thorsten Kampe wrote:
> What about this "winsymlinks" Cygwin environment variable? The
> description says "if set, Cygwin creates symlinks as Windows shortcuts
> with a special header and the R/O attribute set. If not set, Cygwin
> creates symlinks as plain files with a magic number, a path and th
* Jason Tishler (Tue, 01 May 2007 14:32:06 -0400)
> On Tue, May 01, 2007 at 10:21:25AM -0400, Christopher Faylor wrote:
> > OTOH, I still don't see any reason not to tell people "you have to run
> > bash first if you want to use python".
>
> This is the solution that I prefer.
I think the best so
On Tue, May 01, 2007 at 10:21:25AM -0400, Christopher Faylor wrote:
> OTOH, I still don't see any reason not to tell people "you have to run
> bash first if you want to use python".
This is the solution that I prefer.
> I believe that the vast majority of people who use Cygwin always
> invoke cli
On Tue, May 01, 2007 at 03:30:59PM +0100, Thorsten Kampe wrote:
>* Christopher Faylor (Tue, 1 May 2007 10:22:58 -0400)
>>On Tue, May 01, 2007 at 02:59:20PM +0100, Thorsten Kampe wrote:
>>>* Eric Blake (Tue, 01 May 2007 07:27:49 -0600)
According to Thorsten Kampe on 5/1/2007 7:11 AM:
>Both t
On 01 May 2007 15:33, Christopher Faylor wrote:
> On Tue, May 01, 2007 at 03:15:52PM +0100, Dave Korn wrote:
>> On 01 May 2007 14:59, Charles Wilson wrote:
>>> Because python is a command interpreter,
>
>>> Similarly, sh.exe
>>
>> I think these are two very strong arguments in favour.
>
> pytho
Christopher Faylor wrote:
On Tue, May 01, 2007 at 03:15:52PM +0100, Dave Korn wrote:
On 01 May 2007 14:59, Charles Wilson wrote:
Because python is a command interpreter,
Similarly, sh.exe
I think these are two very strong arguments in favour.
python.exe isn't anything like the interactive
* Christopher Faylor (Tue, 1 May 2007 10:22:58 -0400)
> On Tue, May 01, 2007 at 02:59:20PM +0100, Thorsten Kampe wrote:
> >* Eric Blake (Tue, 01 May 2007 07:27:49 -0600)
> >>According to Thorsten Kampe on 5/1/2007 7:11 AM:
> >>>Both things are actually the same under Cygwin (tested on my FAT32
> >>
On Tue, May 01, 2007 at 03:15:52PM +0100, Dave Korn wrote:
>On 01 May 2007 14:59, Charles Wilson wrote:
>>Because python is a command interpreter,
>>Similarly, sh.exe
>
>I think these are two very strong arguments in favour.
python.exe isn't anything like the interactive shell that people use on
On Tue, May 01, 2007 at 02:59:20PM +0100, Thorsten Kampe wrote:
>* Eric Blake (Tue, 01 May 2007 07:27:49 -0600)
>>According to Thorsten Kampe on 5/1/2007 7:11 AM:
>>>Both things are actually the same under Cygwin (tested on my FAT32
>>>flash drive and under Windows XP NTFS).
>>
>>True only for FAT
On Tue, May 01, 2007 at 09:59:24AM -0400, Charles Wilson wrote:
>Christopher Faylor wrote:
>>Before you do this, I have a question. Why is this important now when
>>you've
>>apparently been doing this for many years? This isn't the only package
>>which
>>makes symlinks to executables. And, sin
On 01 May 2007 14:59, Charles Wilson wrote:
> Because python is a command interpreter,
> Similarly, sh.exe
I think these are two very strong arguments in favour. I note that we
already (appear to?) do the same for perl.
(/me remembers back to the insane gyrations I had to go through a c
* Eric Blake (Tue, 01 May 2007 07:27:49 -0600)
> According to Thorsten Kampe on 5/1/2007 7:11 AM:
> > Both things are actually the same under Cygwin (tested on my FAT32
> > flash drive and under Windows XP NTFS).
>
> True only for FAT and FAT32, which don't support hard links at all.
>
> > NTFS
Christopher Faylor wrote:
Before you do this, I have a question. Why is this important now when you've
apparently been doing this for many years? This isn't the only package which
makes symlinks to executables. And, since, AFAIK, setup.exe doesn't understand
hard links it means that you really
On Tue, May 01, 2007 at 09:50:31AM -0400, Lev Bishop wrote:
>On 5/1/07, Christopher Faylor wrote:
>>On Tue, May 01, 2007 at 08:06:23AM -0400, Jason Tishler wrote:
>>>OK. Should I copy or make a hard link?
>>
>>Before you do this, I have a question. Why is this important now when
>>you've apparen
On 5/1/07, Christopher Faylor wrote:
On Tue, May 01, 2007 at 08:06:23AM -0400, Jason Tishler wrote:
>OK. Should I copy or make a hard link?
Before you do this, I have a question. Why is this important now when you've
apparently been doing this for many years? This isn't the only package whic
On Tue, May 01, 2007 at 08:06:23AM -0400, Jason Tishler wrote:
>On Sun, Apr 29, 2007 at 11:58:57PM +0100, Thorsten Kampe wrote:
>> I just found out that in the standard Cygwin Python setup it is not
>> possible to run the Python interpreter from a Win32 command shell.
>> (You get an error about t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Thorsten Kampe on 5/1/2007 7:11 AM:
> Both things are actually the same under Cygwin (tested on my FAT32
> flash drive and under Windows XP NTFS).
True only for FAT and FAT32, which don't support hard links at all.
> NTFS supports hard
* Jason Tishler (Tue, 01 May 2007 08:06:23 -0400)
> On Sun, Apr 29, 2007 at 11:58:57PM +0100, Thorsten Kampe wrote:
> > I just found out that in the standard Cygwin Python setup it is not
> > possible to run the Python interpreter from a Win32 command shell.
> > (You get an error about the NTVDM
On Sun, Apr 29, 2007 at 11:58:57PM +0100, Thorsten Kampe wrote:
> I just found out that in the standard Cygwin Python setup it is not
> possible to run the Python interpreter from a Win32 command shell.
> (You get an error about the NTVDM (NT Virtual DOS machine even when C:
> \cygwin\bin is in t
* Thorsten Kampe (Sun, 29 Apr 2007 23:58:57 +0100)
> As the Python interpreter itself is only about 43 Kb in size I
> suggest copying the interpreter [...]
which resolves the issue...
Thorsten
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwi
Hi,
I just found out that in the standard Cygwin Python setup it is not
possible to run the Python interpreter from a Win32 command shell.
(You get an error about the NTVDM (NT Virtual DOS machine even when C:
\cygwin\bin is in the path).
The reason is that python.exe is a symbolic link to pyth
23 matches
Mail list logo
