From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1313 invoked from network); 18 Jan 2000 11:28:47 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 18 Jan 2000 11:28:47 -0000 Received: (qmail 3224 invoked by alias); 18 Jan 2000 11:28:38 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 9343 Received: (qmail 3217 invoked from network); 18 Jan 2000 11:28:37 -0000 To: Sven Wischnowsky Cc: zsh-workers@sunsite.auc.dk Subject: Re: PATCH: _a2ps completion References: From: Akim Demaille Date: 18 Jan 2000 12:32:27 +0100 In-Reply-To: Akim Demaille's message of "18 Jan 2000 12:00:57 +0100" Message-ID: User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Hi! I realize my message was probably too short, and was not showing why it would be an error to limit the features a2ps from within zsh. When you give a2ps a PostScript file (or virtually any kind of file), you can use it just as if it were a plain file. In particular you still can use --pages to select the pages to print, -1, -2, -4 etc. for 2up and so one, insert special requests (Duplex, ManualFeed etc.). It will not print the PostScript source, nor the HTML source by default: you have to tell it you know what you're doing, and it will obey. You don't need to put soft corners around a2ps from zsh: they're builtin already. Please, the fact that a2ps behaves properly, and actually even *very well* with non text files is one of its major features, it is part of its identity. If zsh removes this from a2ps it would be like condemning Leonardo da Vinci to painting (am I being clear? ;) Thanks! Akim