Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Delivered-To: mailing list cygwin@cygwin.com To: "Eugene Rosenzweig" Cc: Subject: Re: tar -f behaviour References: <0c6501c1bed4$f548d5e0$0300a8c0@bluebox> From: "Julien Gilles" Date: Tue, 26 Feb 2002 16:39:24 +0100 In-Reply-To: <0c6501c1bed4$f548d5e0$0300a8c0@bluebox> ("Eugene Rosenzweig"'s message of "Wed, 27 Feb 2002 01:50:38 +1100") Message-ID: <7radtw9rrn.fsf@glmultimedia.com> Lines: 21 User-Agent: Gnus/5.090005 (Oort Gnus v0.05) XEmacs/21.4 (Common Lisp (Windows [1]), i686-pc-cygwin) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii "Eugene Rosenzweig" writes: > Looking at tar I noticed a small oddity in its behaviour, as compared to > what I would have thought was 'normal' > When dealing with files, using dash before options, the 'f' option has to be > the last one in the option string, e.g. > > In conclusion, is this a bug or a feature? A (normal) feature. In GNU world, options starts with one or two dash, and you can write : tar --file=file tar -f file tar -ffile If fact the syntax 'tar zcf file' is an old syntax, only kept for compatibility, it should be read : 'tar -z -c -f file'. -- Julien Gilles -- 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/