From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: rewriting y-or-n-p to use read-char-choice
Date: Thu, 10 Mar 2011 16:54:28 -0600 [thread overview]
Message-ID: <87k4g6io2j.fsf@lifelogs.com> (raw)
In-Reply-To: FD8F51F9969D4F659BD617EAE0EB97BD@us.oracle.com
On Thu, 10 Mar 2011 14:35:49 -0800 "Drew Adams" <drew.adams@oracle.com> wrote:
>> Stefan Monnier asked me to look at rewriting `y-or-n-p' to use
>> `read-char-choice'.
DA> Completely missing from your exposition of implementation issues is why. Why
DA> rewrite `y-or-n-p'? What advantages are sought/expected?
See bug #8050. The original need was, I believe, to reuse code.
Ted
next prev parent reply other threads:[~2011-03-10 22:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-10 18:50 rewriting y-or-n-p to use read-char-choice Ted Zlatanov
2011-03-10 19:10 ` Edward O'Connor
2011-03-10 19:46 ` Ted Zlatanov
2011-03-10 22:35 ` Drew Adams
2011-03-10 22:54 ` Ted Zlatanov [this message]
2011-03-10 23:48 ` Drew Adams
2011-03-11 2:05 ` Stefan Monnier
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k4g6io2j.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).