unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: James Cloos <cloos@jhcloos.com>
Cc: help-gnu-emacs@gnu.org, Tom Rauchenwald <its.sec@gmx.net>
Subject: Re: postscript output?
Date: Wed, 03 Jan 2007 16:35:39 -0500	[thread overview]
Message-ID: <m34pr7g5dp.fsf@lugabout.jhcloos.org> (raw)
In-Reply-To: <459A3729.3090400@skynet.be> (Jan Brosius's message of "Tue\, 02 Jan 2007 11\:42\:49 +0100")

>>>>> "Jan" == Jan Brosius <jan.brosius@skynet.be> writes:

Jan> I have done this and I get a buffer called *Postscript*.  Is it
Jan> possible to preview this buffer in Emacs in another buffer?

So you want to see what the generated PostScript code will print out
when sent to a printer?

You could, in that *Postscript* buffer, hit:

    M-<  C-@  M->  M-|

and then type out the command:

    gv -

gv should then bring up a X window with the rendered PS.

You may need C-Space for C-@.

If you don't have gv installed, you may be able to do that with
another viewer.

You can also make a macro from those keystrokes, name it, and bind
that to a key sequence if you will use if often.

Or you can write a quick lisp function that switches to *Postscript*
and calls (shell-command-on-region (point-min) (point-max) "gv -").

To get the output into an Emacs buffer, you'd have to call gs rather
than gv, specifying one of the image backends Emacs can grok, and have
that output to a buffer.  It is doable, but I'd need to bone up on the
docs to figure it out.

-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 1024D/ED7DAEA6

  reply	other threads:[~2007-01-03 21:35 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-01 17:37 postscript output? Jan Brosius
2007-01-01 16:55 ` Peter Dyballa
2007-01-01 18:54   ` Jan Brosius
2007-01-01 18:24     ` Tom Rauchenwald
2007-01-02 10:42       ` Jan Brosius
2007-01-03 21:35         ` James Cloos [this message]
2007-01-04 15:10           ` Jan Brosius
2007-01-04 18:36             ` James Cloos
2007-01-09 14:07           ` Kevin Rodgers

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=m34pr7g5dp.fsf@lugabout.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=its.sec@gmx.net \
    /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).