unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Adding to ps-print-hook problems
Date: Mon, 16 Sep 2002 21:39:46 +0200	[thread overview]
Message-ID: <vaf4rcpenb1.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Axoh9.62971$xm.12776983@twister.nyroc.rr.com

"Jeff Rancier" <jeff.rancier@softechnics.com> writes:

> So, I guess the next question is:  How do I bypass the interactive property
> of ps-print-buffer-with-faces(), and have my hook function be interactive?

You can have your hook function ask the user explicitly, rather than
via the `interactive' spec.  See read-from-minibuffer,
completing-read, and friends.

kai
-- 
~/.signature is: umop 3p!sdn    (Frank Nobis)

  reply	other threads:[~2002-09-16 19:39 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-16 15:17 Adding to ps-print-hook problems Jeff Rancier
2002-09-16 16:37 ` Kevin Rodgers
2002-09-16 17:29   ` Jeff Rancier
2002-09-16 19:39     ` Kai Großjohann [this message]
2002-09-17 11:33 ` Klaus Berndl
2002-09-17 11:51   ` Marco Lonsing

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=vaf4rcpenb1.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).