Gnus development mailing list
 help / color / mirror / Atom feed
From: Brian May <bmay@csse.monash.edu.au>
Subject: Re: `A P' induces postscript error
Date: 17 May 2000 11:20:01 +1000	[thread overview]
Message-ID: <x3rpuqmt1ku.fsf@lyell.csse.monash.edu.au> (raw)
In-Reply-To: Karl Kleinpaste's message of "Sun, 14 May 2000 14:47:49 -0400"

>>>>> "Karl" == Karl Kleinpaste <karl@charcoal.com> writes:

    Karl> I'm trying print a couple of mail messages today --
    Karl> something I do only rarely -- and everything I'm trying to
    Karl> print is rewarding me with postscript errors, which begin as
    Karl> Error: /undefined in " Operand stack: HeaderLinesLeft
    Karl> --nostringval-- --...  Is this something over which Gnus has
    Karl> control, or is this purely the fault of the underlying
    Karl> ps-print-buffer-with-faces?

I have had heaps of problems with this command, especially
when trying to select a non-default printer.

By default, printed output disappears down a black hole. I would have
hoped that gnus would display the error from lpr, but it doesn't.

I assume I have to change either lpr-command or lpr-switches.

Rather then trying to reproduce all the horrible LISP errors I have
encountered, could somebody please give me sample LISP code to change
the active printer with the -P option to lpr? Thanks.

Also, there is a bug in C-u A P. From memory, it asks what file to
write the output to. However, if multiple messages have been selected,
only the last one will appear (I assume that each message overwrites
the last one).

>From time to time, other weird problems have occurred (eg printing the
wrong message), but I doubt I would be able to reproduce this.

As for that postscript error, /undefined seems to be one of the most
common errors I have seen (not from gnus though).
-- 
Brian May <bmay@csse.monash.edu.au>



  parent reply	other threads:[~2000-05-17  1:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-14 18:47 Karl Kleinpaste
2000-05-15  8:52 ` Terje Tverberg
2000-05-17  1:20 ` Brian May [this message]
2000-05-17  2:26   ` Alan Shutko
2000-05-17 12:53   ` Kai Großjohann
2000-05-17 23:25     ` Brian May
2000-05-18 11:57       ` Kai Großjohann

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=x3rpuqmt1ku.fsf@lyell.csse.monash.edu.au \
    --to=bmay@csse.monash.edu.au \
    /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.
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).