From: Peter Dyballa <Peter_Dyballa@Web.DE>
Cc: help-gnu-emacs@gnu.org
Subject: Re: sending a buffer content as pipe to enscript
Date: Tue, 4 Oct 2005 12:29:30 +0200 [thread overview]
Message-ID: <dd201a9ddfbd9764ce3ad7958b149414@Web.DE> (raw)
In-Reply-To: <m2psql7gkl.fsf@flatsoft.no-ip.info>
Am 04.10.2005 um 11:54 schrieb Flatman:
> I'd like to use enscript for printing buffer contents . How can I send
> the content of the active buffer to enscript ?
>
top-of-buffer
set-mark
end-of-buffer
shell-command-on-region?
The whole buffer is marked and gets passed to enscript.
How about your elder approach from August with saving the buffer's
contents to /tmp? enscript could pick up this too ...
--
Greetings
Pete
War springs from unseen and generally insignificant causes.
-Anonymous
next prev parent reply other threads:[~2005-10-04 10:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-04 9:54 sending a buffer content as pipe to enscript Flatman
2005-10-04 10:29 ` Peter Dyballa [this message]
2005-10-04 18:48 ` Kevin Rodgers
[not found] ` <mailman.9670.1128422052.20277.help-gnu-emacs@gnu.org>
2005-10-04 10:56 ` Flatman
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=dd201a9ddfbd9764ce3ad7958b149414@Web.DE \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@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).