Gnus development mailing list
 help / color / mirror / Atom feed
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: Sun, 06 Jan 2008 09:21:37 +0900	[thread overview]
Message-ID: <b4mzlvjolbi.fsf@jpl.org> (raw)
In-Reply-To: <v9odc0q9v9.fsf@marauder.physik.uni-ulm.de>

>>>>> Reiner Steib <reinersteib+gmane@imap.cc> wrote:

> On Wed, Dec 19 2007, Katsumi Yamaoka wrote:

>>> So, I strongly oppose to making `gnus-y-or-n-p' alias to `y-or-n-p'
>>> or removing `gnus-y-or-n-p'.

>> Try `c' and `n' in the group buffer.

> You mean `c' for `gnus-group-catchup-current' or
> `gnus-topic-catchup-articles' and answering `n' to the y-or-n-p
> prompt?

Yes, I did.

> What I see in the echo area is:

> - c --> Mark all unread articles in ulm.test as read? (y or n)

> - n --> Mark all unread articles in ulm.test as read? (y or n) n

>   ... i.e. the response "n" stays there until you hit some other key
>   (e.g. `p', `n', ...).

> 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.  If anything, we may call it a bug.



  reply	other threads:[~2008-01-06  0:21 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 [this message]
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=b4mzlvjolbi.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).