From: Simon Josefsson <jas@extundo.com>
Subject: Re: [PATCH] Autoload `message-y-or-n-p' macro in gnus.el at compile
Date: Thu, 15 Jan 2004 14:28:07 +0100 [thread overview]
Message-ID: <iluad4pbau0.fsf@latte.josefsson.org> (raw)
In-Reply-To: <microsoft-free.871xq1v4m2.fsf@eicq.dnsalias.org> (Steve Youngs's message of "Thu, 15 Jan 2004 21:22:13 +1000")
Steve Youngs <sryoungs@bigpond.net.au> writes:
> * Simon Josefsson <jas@extundo.com> writes:
>
> > Steve Youngs <sryoungs@bigpond.net.au> writes:
> >> Over at XEmacs.org, they've got a couple of awk scripts to help them
> >> find mis-compiled macros and stuff. It turned up this
> >> one... `message-y-or-n-p', which is defined in message.el isn't
> >> getting picked up in gnus.el (where it's used in `gnu-read-group').
>
> > I think gnus-read-group should be fixed. There is a `gnus-y-or-n-p'.
>
> Who says it's broken? And besides, `gnus-y-or-n-p' and
> `message-y-or-n-p' are _very_ different animals. The former is not
> much more that `y-or-no-p' with a different name, but the latter has
> the option of displaying a "help" buffer as well as the prompt.
Ah, sorry. Then I agree with your patch, but shouldn't there be
another nil in there? (autoload 'message-y-or-n-p "message" nil
'macro) makes the INTERACTIVE argument 'macro, which seems weird.
(autoload FUNCTION FILE &optional DOCSTRING INTERACTIVE TYPE)
Fifth arg TYPE indicates the type of the object:
nil or omitted says FUNCTION is a function,
`keymap' says FUNCTION is really a keymap, and
`macro' or t says FUNCTION is really a macro.
> >> Anyway, I was just about to commit this when I had a thought (yep,
> >> occasionally I do have em). Should this patch go into gnus.el, or
> >> into dgnushack.el?
>
> > If gnus-read-group is fixed, is it still required?
>
> 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?
None, I was mislead by the function names. I assumed message-y-or-n-p
and gnus-y-or-n-p was yet another duplicated function definition.
OTTH, I guess the functionality provided by message-y-or-n-p might be
a candidate for moving into a "utilities" library, it seems generally
useful. Especially now that both Message and Gnus use it.
next prev parent reply other threads:[~2004-01-15 13:28 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
2004-01-15 13:28 ` Simon Josefsson [this message]
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=iluad4pbau0.fsf@latte.josefsson.org \
--to=jas@extundo.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 NNTP newsgroup(s).