Gnus development mailing list
 help / color / mirror / Atom feed
From: Terje Tverberg <terjet@hrp.no>
Subject: Re: `A P' induces postscript error
Date: 15 May 2000 10:52:53 +0200	[thread overview]
Message-ID: <eug0rkyz2y.fsf@hrp.no> (raw)
In-Reply-To: <vxk7lcxklyi.fsf@mesquite.charcoal.com>

Karl Kleinpaste <karl@charcoal.com> writes:

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

Hi Karl. 
This is maybe a shot in the dark, but I saw something similar when I
upgraded my ps-print package - loads of PostScript errors; no printouts.
The errors weren't exactly the same as yours, though, so maybe your
problem is a different one.

Anyway in my case, the problem stemmed from that the (PostScript)
prologue files (ps-prin*.ps) that ps-print uses had changed in the new
version (v. 5.1.5 in my case) and I needed to point ps-print to the
directory where the new (correct) files were placed:

  (setq ps-postscript-code-directory "/path/to/prologue/files/")

You mention that you have a fairly recent XEmacs - maybe something has
changed in the use of the ps-print package there?
As I said, just a shot in the dark.

Regards, 

Terje



  reply	other threads:[~2000-05-15  8:52 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 [this message]
2000-05-17  1:20 ` Brian May
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=eug0rkyz2y.fsf@hrp.no \
    --to=terjet@hrp.no \
    /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).