From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: Do we need gnus-yes-or-no-p and gnus-y-or-n-p?
Date: Sun, 06 Jan 2008 10:25:28 +0100 [thread overview]
Message-ID: <v9wsqni9vb.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4mzlvjolbi.fsf@jpl.org>
On Sun, Jan 06 2008, Katsumi Yamaoka wrote:
>>>>>> Reiner Steib <reinersteib+gmane@imap.cc> wrote:
>> I fail to see anything wrong here.
>
> Hm, but if the function to query is `yes-or-no-p', the echo area
> is cleared just after entering `n o <RET>'. I think that that
> `y-or-n-p' leaves the question and the answer in the echo area
> is not intentional.
Maybe, maybe not. I could imagine that it is intentional: In contrast
to yes-or-no-p it is much easier to type y, n, SPC, DEL, etc
accidentally, so it might be useful for the user to see what he has
typed.
Do you or anyone have real life examples (in Gnus) where leaving the
message in the echo area after `(gnus-)y-or-n-p' is confusing?
> If anything, we may call it a bug.
If so, it would be a general bug in (X)Emacs and should be fixed
there, not in Gnus, IMHO.
Would you like to ask if it's intentional on emacs-devel/xemacs-beta?
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2008-01-06 9:25 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
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 [this message]
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=v9wsqni9vb.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
--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).