Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: article printing with `A P' is generating bad postscript
Date: Wed, 12 Jun 2002 12:29:16 -0400	[thread overview]
Message-ID: <vxkadq0qx43.fsf@cinnamon.vanillaknot.com> (raw)
In-Reply-To: <v9hek8o8oz.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Wed, 12 Jun 2002 16:47:24 +0200")

Reiner Steib <4uce.02.r.steib@gmx.net> writes:
> I can't see anything strange there. Did you get an error related to
> "h0" too ("h0   --nostringval--   --nostringval--")?

Not that I noticed.  I think that was just a quotation in the text
from your message.

> Which version of ps-print do you use (see the variable
> ps-print-version)?

| `ps-print-version' is a variable declared in Lisp.
|   -- loaded from "ps-print"

| Value: "3.05x1"

| Documentation:
| ps-print.el, v 3.05 <97/01/17 duthen>

That seems really old.  But it's what comes with XEmacs' sumo tarballs
these days.  (I certainly haven't any other ps-print lying around.)

> Then it's probably no Gnus error, I can reproduce the error with GNU
> Ghostscript 6.52 and 5.50 and ps-print v6.5.5 (distributed with Emacs
> 21.1).

OK, so I'm not entirely alone if you can reproduce it.

I will see if there's a more appropriate ps-print out there, but I
wonder why this used to work for me.

Hm, comments in ps-print.el say:

;; 3.05x1 -- Forked for XEmacs/No-Mule.  The official version of
;;  ps-print is Mule-only.

I will hunt for that.



  reply	other threads:[~2002-06-12 16:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-11  0:13 Karl Kleinpaste
2002-06-11  2:53 ` Jesper Harder
2002-06-11 16:17 ` Reiner Steib
2002-06-12  2:56   ` Karl Kleinpaste
2002-06-12 14:47     ` Reiner Steib
2002-06-12 16:29       ` Karl Kleinpaste [this message]
2002-06-12 17:40         ` Reiner Steib

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=vxkadq0qx43.fsf@cinnamon.vanillaknot.com \
    --to=karl@charcoal.com \
    /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).