From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: Do we need gnus-yes-or-no-p and gnus-y-or-n-p?
Date: Mon, 17 Dec 2007 10:44:06 +0900 [thread overview]
Message-ID: <b4m63yygknt.fsf@jpl.org> (raw)
In-Reply-To: <v9y7bxq8zn.fsf@marauder.physik.uni-ulm.de>
>>>>> Reiner Steib wrote:
> On Wed, Aug 29 2007, Reiner Steib wrote:
>> do we really need gnus-yes-or-no-p and gnus-y-or-n-p?
>>
>> They are there since almost forever. From the comment, I'd guess it
>> could have been a workaround for a bug in the corresponding Emacs
>> functions.
>>
>> ,----[ 3.1 (larsi 04-Mar-97) ]
>>| ;; Two silly functions to ensure that all `y-or-n-p' questions clear
>>| ;; the echo area.
> [...]
> I defaliased them to the original Emacs functions. If nobody
> complains after some time, we can get rid of the aliases and use the
> original functions.
Sorry for my lazy response. I wish that a command like the
following clears a question out after I answer.
(defun foo ()
"Switch to buffer named foo."
(interactive)
(when (y-or-n-p "Switch to buffer foo? ")
(switch-to-buffer "foo")))
This should be fixed if it is considered to be a bug of Emacs,
and we will be able to remove `gnus-y-or-n-p' at last when Gnus
comes not to support the versions of Emacsen having the bug. In
other words, if we don't use `gnus-y-or-n-p' we have to keep
having `(message "")' with `y-or-n-p' that doesn't follow a
function that clears or changes the echo area (minibuffer?)
until Gnus comes not to support buggy Emacsen. I think.
next prev parent reply other threads:[~2007-12-17 1:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 18:24 Reiner Steib
2007-12-14 21:09 ` Reiner Steib
2007-12-17 1:44 ` Katsumi Yamaoka [this message]
2007-12-17 2:26 ` Katsumi Yamaoka
2007-12-18 23:01 ` Katsumi Yamaoka
2007-12-19 2:37 ` Katsumi Yamaoka
2008-01-05 20:46 ` Reiner Steib
2008-01-06 0:21 ` Katsumi Yamaoka
2008-01-06 9:25 ` Reiner Steib
2008-01-07 6:33 ` Katsumi Yamaoka
2008-01-07 6:34 ` Katsumi Yamaoka
2008-01-07 17:16 ` Richard Stallman
2008-01-07 22:52 ` Katsumi Yamaoka
2008-02-16 12:22 ` Reiner Steib
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=b4m63yygknt.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.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.
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).