Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <80575AFA5F0DD31197CE00805F650D767B225A@wilber.adroit.com> From: "Robinow, David" To: cygwin AT cygwin DOT com Subject: RE: gzip.exe as symlink... Date: Mon, 15 Jul 2002 17:47:18 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" > From: Robert Collins [mailto:robert DOT collins AT syncretize DOT net] > Subject: RE: gzip.exe as symlink... > > From: Jon Cast > > Subject: Re: gzip.exe as symlink... > > Robert Collins wrote: > > > > > I'd never thought about it - why would anyone care which > > > is the real file? > > If they have to use any program not linked with cygwin1.dll. > Then they presumably have the luxry of telling it what .exe to run. > Rob except that there isn't one. if gzip.exe is a (unusable outside cygwin) link to gunzip.exe, then "gunzip" will read in a compressed file, but there is no switch to gunzip which will allow recompressing the file on output. if gunzip.exe is a (unusable outside cygwin) link to gzip.exe, then "gzip -d" will read in a compressed file, and "gzip" will allow recompressing the file on output. The second case has been the state of affairs in the past and it's why NTemacs has worked. The first case is what cygwin gzip currently provides, thus a minor difficulty. As I mentioned in a previous post, the problem can be easily remedied with some elisp or by simply copying gunzip.exe to gzip.exe. Nevertheless I think it would be advisable to restore the gzip distribution to what it was in the past, with gzip.exe being the executable and gunzip.exe being the link. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/