zsh-workers
 help / color / mirror / code / Atom feed
From: Akim Demaille <akim@epita.fr>
To: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
Cc: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: _a2ps completion
Date: 18 Jan 2000 12:32:27 +0100	[thread overview]
Message-ID: <mv4iu0rfwdw.fsf@nostromo.lrde.epita.fr> (raw)
In-Reply-To: Akim Demaille's message of "18 Jan 2000 12:00:57 +0100"


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


  reply	other threads:[~2000-01-18 11:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-01-18 11:00 Akim Demaille
2000-01-18 11:32 ` Akim Demaille [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-01-19 16:16 Sven Wischnowsky
2000-01-18 13:17 Sven Wischnowsky
2000-01-18 20:00 ` Peter Stephenson
2000-01-18 12:06 Sven Wischnowsky
2000-01-18 11:30 Sven Wischnowsky
2000-01-18 11:46 ` Zefram
2000-01-18 11:50 ` Akim Demaille
2000-01-18 10:17 Sven Wischnowsky
2000-01-18  8:08 Sven Wischnowsky
2000-01-17 15:28 Clint Adams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=mv4iu0rfwdw.fsf@nostromo.lrde.epita.fr \
    --to=akim@epita.fr \
    --cc=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).