Re: default PATH

2006-02-12 Thread John Morrison
On Sat, February 11, 2006 8:41 pm, Christopher Faylor wrote: > We're > just trying go figure out if removing the ;; translation will affect > many people. We're not looking to add things to the PATH. > > There is a tradeoff here and I don't believe that we really know what > the implications are.

Re: make: rm: command not found

2006-02-12 Thread Yitzchak Scott-Thoennes
On Sat, Feb 11, 2006 at 03:15:37AM -0800, Tim Prince wrote: > At 08:40 AM 2/10/2006, JefV wrote: > >-- > >View this message in context: > >http://www.nabble.com/make%3A-rm%3A-command-not-found-t1100243.html#a2873151 > >Sent from the Cygwin Users forum at Nabble.com. > > > > > >-- > >Unsubscribe in

Re: default PATH

2006-02-12 Thread Corinna Vinschen
On Feb 11 15:24, Stephan Mueller wrote: > cgf wrote: > " So, I don't think this really answers Corinna's question. I believe that > " she was looking for documentation which stated that ;; was ignored, not > " reasoning which implies it. > > In the absence of the former, I'd hope the latter would

Re: default PATH

2006-02-12 Thread Corinna Vinschen
On Feb 12 08:44, John Morrison wrote: > On Sat, February 11, 2006 8:41 pm, Christopher Faylor wrote: > > We're > > just trying go figure out if removing the ;; translation will affect > > many people. We're not looking to add things to the PATH. > > > > There is a tradeoff here and I don't believe

Re: default PATH

2006-02-12 Thread Corinna Vinschen
On Feb 11 20:22, Eric Blake wrote: > I strongly oppose option 3 - cygwin should never add '.' implicitly to the > front of a POSIX path - if you are crazy enough to want dot there, put > it there yourself explicitly. But I like option 2, of squeezing ';;' into a > single ':' (avoiding the implicit

Re: make: rm: command not found

2006-02-12 Thread Tim Prince
Yitzchak Scott-Thoennes wrote: On Sat, Feb 11, 2006 at 03:15:37AM -0800, Tim Prince wrote: At 08:40 AM 2/10/2006, JefV wrote: -- View this message in context: http://www.nabble.com/make%3A-rm%3A-command-not-found-t1100243.html#a2873151 Sent from the Cygwin Users forum at Nabble.com. -- Un

Re: 1.5.19: timeval struct not correct defined

2006-02-12 Thread Corinna Vinschen
On Feb 11 19:59, Johnny Willemsen wrote: > Hi, > > In sys/time.h the timeval struct is defined as: > > struct timeval { > long tv_sec; > long tv_usec; > }; > > It should be > > struct timeval { > time_t tv_sec; > suseconds_t tv_usec; > }; > > See the following link for the opengroup s

Re: default PATH

2006-02-12 Thread John Morrison
On Sun, February 12, 2006 11:58 am, Corinna Vinschen wrote: > On Feb 12 08:44, John Morrison wrote: >> On Sat, February 11, 2006 8:41 pm, Christopher Faylor wrote: >> > We're >> > just trying go figure out if removing the ;; translation will affect >> > many people. We're not looking to add things

Re: default PATH

2006-02-12 Thread Corinna Vinschen
On Feb 12 13:52, John Morrison wrote: > On Sun, February 12, 2006 11:58 am, Corinna Vinschen wrote: > > On Feb 12 08:44, John Morrison wrote: > >> Would a reasonable solution would be to make the PATH environment > >> variable > >> a special case and parse it when set? (Appologies if this isn't a

Re: default PATH

2006-02-12 Thread Christopher Faylor
On Sun, Feb 12, 2006 at 01:03:18PM +0100, Corinna Vinschen wrote: >On Feb 11 20:22, Eric Blake wrote: >>I strongly oppose option 3 - cygwin should never add '.' implicitly to >>the front of a POSIX path - if you are crazy enough to want dot there, >>put it there yourself explicitly. But I like opt

Re: default PATH

2006-02-12 Thread Yitzchak Scott-Thoennes
On Sun, Feb 12, 2006 at 11:57:00AM -0500, Christopher Faylor wrote: > If we don't get a single person indicating that they rely on the current > behavior then I'm ok with changing it. We have a patch ready to be > checked in, in fact. I assume that: $ PATH="/foo::$PATH" cmd /c printenv PATH

[ANNOUNCEMENT] New Package: cairo-1.0.2-1

2006-02-12 Thread Yaakov S (Cygwin Ports)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 The following packages have been added to the Cygwin net release: *** cairo-1.0.2-1 *** libcairo2-1.0.2-1 Cairo is a vector graphics library with cross-device output support. Currently supported output targets include the X Window System and in-memor

RE: default PATH

2006-02-12 Thread Dave Korn
On 10 February 2006 19:01, Corinna Vinschen wrote: > On Feb 8 18:59, Dave Korn wrote: >> >> Since POSIX semantics requires an empty path component to be treated as >> $CWD, but Win32 semantics require an empty path component to be ignored, > ^

Gmsh Using Cygwin "Badly"

2006-02-12 Thread Gary R. Van Sickle
I just ran across a program, Gmsh (http://www.geuz.org/gmsh/, "an automatic 3D finite element grid generator (primarily Delaunay) with a build-in CAD engine and post-processor"), that does the "multiple cygwin1.dll's" thing. While the README acknowledges the issue, it offers the following incorrect