From: fabio@joplin.colorado.edu (Fabio Somenzi) Subject: Re: gunzip question 22 Mar 1997 14:59:49 -0800 Approved: cygnus.gnu-win32@cygnus.com Distribution: cygnus Message-ID: <199703221829.LAA13649.cygnus.gnu-win32@joplin.colorado.edu> References: <33336C35.2136@netcom.com> Reply-To: Fabio@Colorado.EDU Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Original-To: gnu-win32@cygnus.com In-Reply-To: Original-Sender: owner-gnu-win32@cygnus.com >>>>> "S" == Sheik writes: S> On Fri, 21 Mar 1997, Jim Balter wrote: >> Trey Jackson wrote: > > e.g. This is what I encounter: > > >> C:\cygnus\H-i386-cygwin32\bin>gunzip resume.txt.gz > GUNZIP.EXE: >> resume.txt.gz already has .gz suffix -- unchanged >> >> Subtle. What command processor are you using? For some reason it >> is passing the command name as "GUNZIP.EXE" instead of "gunzip", S> I have noticed this too, whats even odder still... run this puppy S> in bash, and the problem goes away. gzip compares argv[0] to "gzip, "gunzip", and "zcat" and sets the -d and -c options accordingly. At least this is my recollection from several years ago. Under Unix, gunzip and zcat are normally hard links to gzip. Bash passes the name correctly in argv[0], and therefore it works. Fabio -- Fabio Somenzi | Phone: 303-492-3466 University of Colorado | Fax: 303-492-2758 ECE Dept. | Email: Fabio@Colorado.EDU Boulder CO 80309-0425 | WWW: http://vlsi.colorado.edu/~fabio - For help on using this list, send a message to "gnu-win32-request@cygnus.com" with one line of text: "help".