unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "T.V Raman" via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 60312@debbugs.gnu.org
Subject: bug#60312: Acknowledgement (30.0.50; Feature Request: Customize yes-or-n-p prompt from elisp:)
Date: Sun, 25 Dec 2022 07:53:13 -0800	[thread overview]
Message-ID: <p91r0wn32fq.fsf__22251.4680282742$1671983664$gmane$org@google.com> (raw)
In-Reply-To: <handler.60312.B.167198177811134.ack@debbugs.gnu.org> (GNU bug Tracking System's message of "Sun, 25 Dec 2022 15:23:02 +0000")

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=gb18030, Size: 441 bytes --]

Additional note:

At present, yes-or-no-p calls y-or-n-p from within the C layer if
use-short-answers is turned on; this feels convoluted.

Worse the implementation of y-or-n-p  also feels fairly round-about --
perhaps use-short-answers could be handled   in either C or in elisp,
but calling back and forth feels  fragile.

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
7©4 Id: kg:/m/0285kf1  •0Ü8





  parent reply	other threads:[~2022-12-25 15:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-25 15:22 bug#60312: 30.0.50; Feature Request: Customize yes-or-n-p prompt from elisp: T.V Raman via Bug reports for GNU Emacs, the Swiss army knife of text editors
     [not found] ` <handler.60312.B.167198177811134.ack@debbugs.gnu.org>
2022-12-25 15:53   ` T.V Raman via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-12-25 17:19 ` Jean Louis
2023-01-03 14:52   ` Robert Pluim
2023-01-03 15:06     ` T.V Raman via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-03 15:12       ` Robert Pluim
2023-01-03 15:32         ` Eli Zaretskii
2023-01-23  8:23           ` Robert Pluim
2023-09-10 17:35             ` Stefan Kangas

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='p91r0wn32fq.fsf__22251.4680282742$1671983664$gmane$org@google.com' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=60312@debbugs.gnu.org \
    --cc=raman@google.com \
    /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).