From: Jean-Pierre Moreau <notuser@baddomain.toto>
Subject: Re: ps-print-buffer does not print
Date: 07 Mar 2006 14:55:45 -0500 [thread overview]
Message-ID: <87r75e3u7y.fsf@cicero1.priv> (raw)
In-Reply-To: 1140865216.087402.31870@i40g2000cwc.googlegroups.com
"Nellinux" <nello.sola@libero.it>, 25 Feb 2006 03:00:16 -0800:
> all commands involving postscript printing in Emacs do not work.
My problem is not printing itself, it is gv. I reply here in
case this can help, I just found this problem 3 hours ago.
Probably I will formulate a question for alt.os.linux.slackware.
I have these softwares/systems, similar to OP:
- Slackware 10.2+ (slackware-current 2006-01-??, not far from 10.2)
- GNU Emacs 21.4.2
- CUPS 1.1.23
- ESP Ghostscript 8.15rc4 (slack package espgs-8.15rc4...)
- gv-3.5.8
- HP LaserJet 4m (PostScript) printer (second hand).
I have *similar* problem, not same, with slackware-10.2 emacs
and gv to view, using gv, PostScript files from
emacs ps print to file (ps-print-region / ps-print-buffer.)
In fact, I suppose (who can be sure in this complex world?)
this is Slackware-10.2 gv (gv-3.5.8), not emacs, that has or
from which comes my problem.
Slackware-10.1 gv (gv-3.5.8, *same* version) does NOT have
this problem.
Here the creation and display of PS files:
slack-10.1$ emacs # C-u M-x ps-print-region ; TO emacs-slack-10.1.ps
slack-10.1$ gv emacs-slack-10.1.ps #> no problem
Similarly for an emacs PS file created on Slackware-10.2,
gv on Slack-10.1 displays it correctly :
slack-10.1$ gv emacs-slack-10.2.ps #> no problem
However these ps files from slack-10.1 or 10.2 emacs ps-print commands
have problems in gv of slackware-10.2.
First, these ps files are printed (on paper!) correctly:
slack-10.2$ lpr emacs-slack-10.1.ps #> Ok.
However gv on Slack-10.2+ has the problem :
slack-10.2$ gv emacs-slack-10.1.ps #> PROBLEM:
This is postscript page 1 showing the error (NOT a msg box!):
# ERROR: configurationerror
# OFFENDING COMMAND: setpagedevice
# STACK:
- dictionary -
# ERRORINFO:
false
/ManualFeed
Hope this bring some light (umm... possibly darkens too!).
--
Jean-Pierre Moreau
nouser@inexistant (s/nouser/jpmoreau/ ; s/inexistant/gmail.com)
prev parent reply other threads:[~2006-03-07 19:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-25 11:00 ps-print-buffer does not print Nellinux
2006-03-01 10:33 ` Peter Dyballa
2006-03-01 18:56 ` Eli Zaretskii
2006-03-04 3:07 ` Ian Zimmerman
2006-03-07 19:55 ` Jean-Pierre Moreau [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r75e3u7y.fsf@cicero1.priv \
--to=notuser@baddomain.toto \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).