From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: [PATCH] Autoload `message-y-or-n-p' macro in gnus.el at compile
Date: Thu, 15 Jan 2004 13:18:45 +0100 [thread overview]
Message-ID: <v9brp5o15m.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <microsoft-free.871xq1v4m2.fsf@eicq.dnsalias.org>
On Thu, Jan 15 2004, Steve Youngs wrote:
> By the time you "fixed" `gnus-read-group', _maintaining it's current
> intended functionality_, you will have re-invented `message-y-or-n-p'.
> So what'd be the point, especially when a quick (eval-when-compile
> (autoload macro)) will do the job just as well?
I don't know which solution is preferable:
(1) Your suggestion:
(eval-when-compile
(autoload 'message-y-or-n-p "message" nil 'macro))
(2) Adding `message-y-or-n-p' to the existing `eval-and-compile' form:
,----
| ;; Define some autoload functions Gnus might use.
| (eval-and-compile
|
| ;; This little mapcar goes through the list below and marks the
| ;; symbols in question as autoloaded functions.
| [...]
`----
--8<---------------cut here---------------start------------->8---
--- gnus.el.~7.6.~ Sun Jan 11 18:44:40 2004
+++ gnus.el Thu Jan 15 13:11:48 2004
@@ -2556,7 +2556,7 @@
("qp" quoted-printable-decode-region quoted-printable-decode-string)
("ps-print" ps-print-preprint)
("message" :interactive t
- message-send-and-exit message-yank-original)
+ message-send-and-exit message-yank-original message-y-or-n-p)
("babel" babel-as-string)
("nnmail" nnmail-split-fancy nnmail-article-group)
("nnvirtual" nnvirtual-catchup-group nnvirtual-convert-headers)
--8<---------------cut here---------------end--------------->8---
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2004-01-15 12:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 9:36 [PATCH] Autoload `message-y-or-n-p' macro in gnus.el at compile time Steve Youngs
2004-01-15 9:51 ` [PATCH] Autoload `message-y-or-n-p' macro in gnus.el at compile Simon Josefsson
2004-01-15 11:22 ` Steve Youngs
2004-01-15 12:18 ` Reiner Steib [this message]
2004-01-15 13:28 ` Simon Josefsson
2004-01-15 21:51 ` Steve Youngs
2004-01-16 20:56 ` Xavier Maillard
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=v9brp5o15m.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.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 NNTP newsgroup(s).