From: Vinicius Jose Latorre <viniciusjl@ig.com.br>
Cc: bug-gnu-emacs@gnu.org, rms@gnu.org
Subject: Re: [sebyte@smolny.plus.com: Bug in ps-print.el?]
Date: Tue, 21 Jun 2005 22:34:51 -0300 [thread overview]
Message-ID: <42B8C03B.2000605@ig.com.br> (raw)
In-Reply-To: <E1Dkrhy-0000ul-5P@fencepost.gnu.org>
Hi Sebastian,
> Here is a transcript of a scratch buffer session:
>
> - ---
>
> (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 and 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'm only using the *info* buffer as an example. Behaviour is
> ; completely erratic on all buffers if individual pages and/or
> ; page-ranges are attempted.
>
> ; Printing the whole buffer (all pages) works fine.
>
> ; I have got some ranges to work by expanding the range beyond my
> ; requirements and then getting the range I'm after.
Please, could you follow the steps below and return back the results to me?
1. Switch to *Scratch* buffer
2. M-: (setq ps-selected-pages '(1)) RET
3. M-: (insert (ps-setup)) RET
4. Save *Scratch* buffer into a file (settings, for example).
5. C-u M-x ps-print-buffer RET scratch.ps RET
6. Switch to *info* buffer.
7. C-u M-x ps-print-buffer RET info.ps RET
8. Send me back the settings, scratch.ps and info.ps files.
9. Thanks
> I'm re-submitting this report. First posted 12th Jan 05, no response.
> Problem persists.
Sorry, I only received your email today (2005-06-21).
Thanks for your report,
Vinicius
parent reply other threads:[~2005-06-22 1:34 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1Dkrhy-0000ul-5P@fencepost.gnu.org>]
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=42B8C03B.2000605@ig.com.br \
--to=viniciusjl@ig.com.br \
--cc=bug-gnu-emacs@gnu.org \
--cc=rms@gnu.org \
/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).