Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: emacs-devel@gnu.org, xemacs-beta@xemacs.org, ding@gnus.org
Subject: Re: Do we need gnus-yes-or-no-p and gnus-y-or-n-p?
Date: Mon, 07 Jan 2008 12:16:05 -0500	[thread overview]
Message-ID: <E1JBva1-000528-VY@fencepost.gnu.org> (raw)
In-Reply-To: <b4mabniw3cs.fsf@jpl.org> (message from Katsumi Yamaoka on Mon, 07 Jan 2008 15:34:43 +0900)

    The behavior of `y-or-n-p' that it doesn't clear the question
    and the answer is not serious of course, but I feel it is not
    cool.

It is intentional.

    Currently, it is commented out in the trunk by Reiner Steib.  He
    also wrote the benefit of leaving the question and the answer in
    the echo area as follows:

    (http://article.gmane.org/gmane.emacs.gnus.general/66061)
    > 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.

Yes, that is the reason.



  reply	other threads:[~2008-01-07 17:16 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
2008-01-07  6:33               ` Katsumi Yamaoka
2008-01-07  6:34                 ` Katsumi Yamaoka
2008-01-07 17:16                   ` Richard Stallman [this message]
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=E1JBva1-000528-VY@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=xemacs-beta@xemacs.org \
    --cc=yamaoka@jpl.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).