unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eli Zaretskii" <eliz@elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: Windows port: using Windows' default printer
Date: Wed, 24 Sep 2003 20:25:08 +0200	[thread overview]
Message-ID: <2719-Wed24Sep2003202507+0300-eliz@elta.co.il> (raw)
In-Reply-To: <3F7074C8.5010206@runestig.com> (peter@runestig.com)

> Date: Tue, 23 Sep 2003 18:28:56 +0200
> From: "Peter 'Luna' Runestig" <peter@runestig.com>
> > 
> >> If I understand you correctly, we already have such a function in
> >> lpr.el: it's `print-region-function'.  dos-w32.el defines it for the
> >> Windows and the DOS ports.
> > 
> > Does ps-print.el use it ?
> > If so, great, we just need to add the `default-printer-name' stuff
> > to it and be done with It\x7f,
> 
> Isn't this what my patch does?

Yes, but why did you need to test for default-printer-name to be
fboundp?  It should simply be called unconditionally, and we should
have some provision for the user to override that with printer-name.

> I also tampered with the following files, but maybe that isn't necessary:
> 
> lpr.el: Add `default-printer-name' stuff to `print-region-1'.
> ps-print.el: Add `default-printer-name' stuff to `ps-do-despool'.
> play/handwrite.el: Add `default-printer-name' stuff to `handwrite'.

This shouldn't be necessary.

I still think that, even for Windows, it's overhead to call
default-printer-name each time we print something.  But that's me.

  reply	other threads:[~2003-09-24 18:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-20 13:18 Windows port: using Windows' default printer Peter 'Luna' Runestig
2003-02-20 23:05 ` Jason Rumney
2003-02-21  6:52   ` Peter 'Luna' Runestig
2003-02-21  8:20     ` Jason Rumney
2003-09-12 19:34       ` Peter 'Luna' Runestig
2003-09-13 10:04         ` Eli Zaretskii
2003-09-13 10:35           ` Jason Rumney
2003-09-13 14:39             ` Eli Zaretskii
2003-09-13 19:44               ` Peter 'Luna' Runestig
2003-09-13 20:32                 ` Kai Grossjohann
2003-09-13 22:13                   ` Jason Rumney
2003-09-13 23:44                 ` Eli Zaretskii
2003-09-14  9:40                   ` Peter 'Luna' Runestig
2003-09-15 14:52         ` Stefan Monnier
2003-09-21 13:19           ` Eli Zaretskii
2003-09-21 19:51             ` Stefan Monnier
2003-09-22  6:07               ` Eli Zaretskii
2003-09-23 16:28               ` Peter 'Luna' Runestig
2003-09-24 18:25                 ` Eli Zaretskii [this message]
2003-09-24 19:22                   ` Luc Teirlinck
2003-09-25 13:26                   ` Peter 'Luna' Runestig
2003-10-22 10:35                     ` Peter 'Luna' Runestig
2003-10-22 11:15                       ` Jason Rumney
2003-10-22 15:58                       ` Eli Zaretskii
2003-11-26 11:55                         ` Peter 'Luna' Runestig

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=2719-Wed24Sep2003202507+0300-eliz@elta.co.il \
    --to=eliz@elta.co.il \
    --cc=emacs-devel@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).