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: <00cc01c22c55$2f9e9700$0100a8c0@wdg.uk.ibm.com> From: "Max Bowsher" To: References: <09b601c22bc1$ec09e870$2300a8c0 AT LAPTOP> <005601c22be1$c1fb8f00$0100a8c0 AT wdg DOT uk DOT ibm DOT com> <004701c22be4$93de6a40$1800a8c0 AT LAPTOP> Subject: Re: gzip.exe as symlink... Date: Tue, 16 Jul 2002 00:13:09 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Robert Collins wrote: > ----- Original Message ----- > From: "Max Bowsher" maxb AT ukf DOT net > >> Never mind emacs - surely it makes more sense for gzip to be the >> real file, and gunzip to be the symlink? Isn't that what most people >> would automatically assume? > > I'd never thought about it - why would anyone care which is the real > file? Ah - you want a reason :-). Dunno, it just felt better. But David Robinow came up with a good one - if gzip.exe is a symlink, then there is no way to invoke gzip in compression mode from a non cygwin program. OK, its not that important, but since the fix is trivial... Max. -- 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/