unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Harald Joerg <harald.joerg@fujitsu-siemens.com>
Subject: Re: network printing on an Win2k network.
Date: 09 Apr 2003 12:07:36 +0200	[thread overview]
Message-ID: <uvfxonfvb.fsf@pgtd1425.mch.fsc.net> (raw)
In-Reply-To: r88c97oi.fsf@online.no

pjacklam@online.no (Peter J. Acklam) writes:

> I use this on Windows XP and it works perfectly ("HOST" and
> "Printer" must be set appropriately)
> 
>       (setq-default ps-lpr-command "print")
>       (setq-default ps-printer-name "\\\\HOST\\Printer")
>       [...]

That's what I had, too, but...

> With Ghostscript installed one can get the usual Windows printer
> dialog thing with
> 
>       (setq-default ps-lpr-command "gsprint.exe")
>       (setq-default ps-printer-name t)
>       (setq-default ps-printer-name-option nil)
>       (setq ps-lpr-switches '("-query")) ; show printer dialog

I really like this one!  Thanks for the hint!

This inspired me to look for a solution for emacs under cygwin.  Under
cygwin, emacs appears *not* to create a file which can be fed to
gsprint (Customize claims that it does so under "MS-DOS and MS-Windows
systems"), but to pipe the buffer (or region) to whatever is defined
in ps-lpr-command.  I came up with a small shell procedure gsprint.sh:

    #!/usr/bin/bash
    TMPFILE=`mktemp -t emacs.print.XXXXX` || exit 1
    cat >$TMPFILE
    /$CYGPATH_TO_gsview/gsprint.exe -query "`cygpath -w $TMPFILE`"

...and set ps-lpr-command to "gsprint.sh".
-- 
Cheers,
haj

  reply	other threads:[~2003-04-09 10:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-07 18:25 network printing on an Win2k network Robert Correllus
2003-04-08  4:18 ` Eli Zaretskii
     [not found] ` <mailman.4255.1049771971.21513.help-gnu-emacs@gnu.org>
2003-04-08 18:15   ` Peter J. Acklam
2003-04-09 10:07     ` Harald Joerg [this message]
     [not found] <mailman.4219.1049740066.21513.help-gnu-emacs@gnu.org>
2003-04-08  0:26 ` Data64

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=uvfxonfvb.fsf@pgtd1425.mch.fsc.net \
    --to=harald.joerg@fujitsu-siemens.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.
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).