From: "Eli Zaretskii" <eliz@gnu.org>
Subject: Re: Adjusting page length in "Print buffer" command
Date: Sat, 15 Jan 2005 12:35:12 +0200 [thread overview]
Message-ID: <01c4faee$Blat.v2.2.2$0a46f780@zahav.net.il> (raw)
In-Reply-To: <m2oefrokb6.fsf@Stella-Blue.local> (message from Tim McNamara on Fri, 14 Jan 2005 13:57:33 -0600)
> From: Tim McNamara <timmcn@bitstream.net>
> Date: Fri, 14 Jan 2005 13:57:33 -0600
>
> Thanks. However, I am using the "Print Buffer" command under the File
> menu, not the "Postscript Print Buffer" command. Does that make a
> difference?
Yes.
Please see if any of the options mentioned in the doc string of
print-buffer help you get what you want:
print-buffer is an interactive autoloaded Lisp function in `lpr'.
It is bound to <menu-bar> <file> <print-buffer>.
(print-buffer)
Paginate and print buffer contents.
The variable `lpr-headers-switches' controls how to paginate.
If it is nil (the default), we run the `pr' program (or whatever program
`lpr-page-header-program' specifies) to paginate.
`lpr-page-header-switches' specifies the switches for that program.
Otherwise, the switches in `lpr-headers-switches' are used
in the print command itself; we expect them to request pagination.
See the variables `lpr-switches' and `lpr-command'
for further customization of the printer command.
I'd say, study the man pages on your system for the commands `pr' and
`lpr' and decide what you should put into `lpr-headers-switches'
and/or `lpr-switches' for the letter-size paper.
(This advice might not work for Windows, but you didn't say that you
were using Windows.)
next prev parent reply other threads:[~2005-01-15 10:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-14 14:23 Adjusting page length in "Print buffer" command Tim McNamara
2005-01-14 14:46 ` Sébastien Kirche
2005-01-14 18:45 ` Sébastien Kirche
2005-01-14 19:57 ` Tim McNamara
2005-01-15 10:35 ` Eli Zaretskii [this message]
[not found] ` <mailman.13284.1105787022.27204.help-gnu-emacs@gnu.org>
2005-01-15 15:57 ` Tim McNamara
2005-01-15 16:59 ` Eli Zaretskii
[not found] ` <mailman.13328.1105809630.27204.help-gnu-emacs@gnu.org>
2005-01-15 22:20 ` Tim McNamara
2005-01-16 19:45 ` Eli Zaretskii
[not found] ` <mailman.13534.1105905964.27204.help-gnu-emacs@gnu.org>
2005-01-16 20:47 ` Tim McNamara
2005-01-17 4:42 ` Eli Zaretskii
[not found] ` <mailman.13604.1105938103.27204.help-gnu-emacs@gnu.org>
2005-01-17 6:04 ` Tim McNamara
2005-01-17 11:38 ` Peter Dyballa
[not found] ` <mailman.13658.1105966339.27204.help-gnu-emacs@gnu.org>
2005-01-18 0:30 ` Tim McNamara
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='01c4faee$Blat.v2.2.2$0a46f780@zahav.net.il' \
--to=eliz@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.
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).