From: "William M. Perry" <wmperry@aventail.com>
Cc: ding@ifi.uio.no
Subject: Re: Catchup command request
Date: Sat, 25 Jan 1997 08:36:15 -0800 [thread overview]
Message-ID: <199701251636.IAA00518@wmperry.in.aventail.com> (raw)
In-Reply-To: <m2hgk61aib.fsf@altair.xemacs.org>
Steven L. Baur writes:
>May I respectfully request that the c) atchup command in the *Summary*
>buffer use yes-or-no-p instead of y-or-n-p?
>
>Yes, I just destroyed another nnml group by typing `cd ' in XEmacs
>when I thought an xterm had keyboard focus :-(.
This should be customizable. W3 has a variable for controlling what
yes-or-no type function should be used for prompts. By defaults it is
yes-or-no-p, but can be changed to anything with the same calling
semantics.
-bp
next prev parent reply other threads:[~1997-01-25 16:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-25 7:26 Steven L Baur
1997-01-25 8:04 ` Lars Magne Ingebrigtsen
1997-01-26 19:50 ` Steven L Baur
1997-01-27 6:00 ` Lars Magne Ingebrigtsen
1997-01-25 16:36 ` William M. Perry [this message]
1997-01-27 19:46 ` Karl Anderson
1997-01-27 20:57 ` Steven L Baur
1997-01-27 21:50 ` David Moore
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=199701251636.IAA00518@wmperry.in.aventail.com \
--to=wmperry@aventail.com \
--cc=ding@ifi.uio.no \
/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).