`A P' induces postscript error

`A P' induces postscript error

[Karl Kleinpaste]

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?

XEmacs 21.2.b31, with sumo tarballs from a couple months back.  I
probably haven't upgraded the underlying packages in 3+ months, and
haven't printed from inside Gnus for somewhat longer than that, which
is why I'm wondering which package, Gnus or ps-print, would be
responsible.

--karl

Re: `A P' induces postscript error

[Terje Tverberg]

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

Re: `A P' induces postscript error

[Brian May]

>>>>> "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>

Re: `A P' induces postscript error

[Alan Shutko]

Brian May <bmay@csse.monash.edu.au> writes:

> 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.

Just use 

ftp://ftp.cis.ohio-state.edu/pub/emacs-lisp/misc/printers.el.gz

-- 
Alan Shutko <ats@acm.org> - In a variety of flavors!
178 days, 13 hours, 9 minutes, 16 seconds till we run away.
Conscience is what hurts when everything else feels so good.

Re: `A P' induces postscript error

[Kai Großjohann]

Brian May <bmay@csse.monash.edu.au> writes:

> 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.

(setq lpr-switches '("-P" "foo"))

kai
-- 
Beware of flying birch trees.

Re: `A P' induces postscript error

[Brian May]

>>>>> "Kai" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:

    Kai> Brian May <bmay@csse.monash.edu.au> writes:
    >> 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.

    Kai> (setq lpr-switches '("-P" "foo"))


Thanks for that, it worked first go. I thought I list was required
but wasn't sure. Previously, I had tried

(setq lpr-switches "-Pfoo")

but that didn't work.
-- 
Brian May <bmay@csse.monash.edu.au>

Re: `A P' induces postscript error

[Kai Großjohann]

Brian May <bmay@csse.monash.edu.au> writes:

> (setq lpr-switches "-Pfoo")

lpr-switches is supposed to be a list of arguments, and "-Pfoo" is not
a list.  You could have said this:

(setq lpr-switches '("-Pfoo"))

This is a list of one argument.

kai
-- 
Beware of flying birch trees.