From: Sebastian Tennant <sebyte@smolny.plus.com>
Subject: Bug in ps-print.el?
Date: Wed, 12 Jan 2005 04:18:33 +0000 [thread overview]
Message-ID: <1105503514.9849.81.camel@localhost.localdomain> (raw)
(current-buffer)
#<buffer *scratch*>
(emacs-version)
"GNU Emacs 21.3.1 (i386-pc-linux-gnu)
of 2004-10-16 on raven, modified by Debian"
(progn
(setq ps-selected-pages '(1))
(ps-print-buffer nil))
t
; works fine printing this scratch buffer
(progn
(setq ps-selected-pages '(1))
(set-buffer "*info*") ; info buffer - emacs (Top)
(ps-print-buffer nil))
t
; doesn't work - printer gears up and then winds down without doing anything
; spooled PS file ends up in /var/spool/cups/
(shell-command "sudo ls -l /var/spool/cups" t)
536
total 32
-rw------- 1 root lpadmin 672 Jan 11 22:28 c00065
-rw------- 1 root lpadmin 672 Jan 11 22:30 c00066
-rw------- 1 root lpadmin 672 Jan 11 22:31 c00067
-rw------- 1 root lpadmin 672 Jan 12 02:09 c00068
-rw------- 1 root lpadmin 672 Jan 12 02:11 c00069
-rw------- 1 root lpadmin 672 Jan 12 03:40 c00070
-rw------- 1 root lpadmin 672 Jan 12 03:51 c00071
drwxrwx--T 2 root lpadmin 4096 Jan 10 02:09 tmp
; As you can see there are several failed print jobs here.
; I only use the *info* buffer as an example. Behaviour is
; completely erratic as far as I can tell, but generally,
; individual pages and ranges are far more likely to fail
; that printing the whole buffer. I have got some ranges
; to work by expanding the range beyond my requirements and
; then getting the range I'm after.
(shell-command "sudo cat /var/spool/cups/c00071" t)
1402
^A^A^@^B^@^@^@^A^AG^@^Rattributes-charset^@^Eutf-8H^@^[attributes-natural-language^@^Ben^BE^@^Kprinter-uri^@$ip\p://localhost:631/printers/HL-1450B^@^Yjob-originating-user-name^@^FsebyteB^@^Hjob-name^@^G(stdin)I^@^Odocument\-format^@^Vapplication/postscriptB^@
job-sheets^@^DnoneB^@^@^@^DnoneD^@^Emedia^@^BA4B^@^HPageSize^@^BA4B^@
InputSlot^@^DautoB^@
PageRegion^@^BA4B^@
Resolution^@
600x600dpi!^@^Ljob-priority^@^D^@^@^@2B^@^Yjob-originating-host-name^@
localhost!^@^Fjob-id^@^D^@^@^@G#^@ \ job-state^@^D^@^@^@ !
^@^Zjob-media-sheets-completed^@^D^@^@^@^@E^@^Ojob-printer-uri^@)http://debian-laptop\:631/printers/HL-1450B^@^Hjob-name^@^G(stdin)!^@^Ljob-k-octets^@^D^@^@^@$!^@^Ptime-at-creation^@^DA\344\236\272\!^@^Rtime-at-processing^@^DA\344\236\272!^@^Qtime-at-completed^@^DA\344\236\275D^@^Njob-hold-until^@^Gno-hold^C
; I've no idea if this is any use and I sincerely hope I'm not
; doing something incredibly dumb and wasting your time.
Sebastian
next reply other threads:[~2005-01-12 4:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-12 4:18 Sebastian Tennant [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-21 11:15 Bug in ps-print.el? Sebastian Tennant
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=1105503514.9849.81.camel@localhost.localdomain \
--to=sebyte@smolny.plus.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).