From: Juri Linkov <juri@linkov.net>
To: Samuel Wales <samologist@gmail.com>
Cc: 64141@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#64141: 27.1 newly has clunky type-break y-or-n-p
Date: Tue, 20 Jun 2023 09:57:51 +0300 [thread overview]
Message-ID: <86y1ker574.fsf@mail.linkov.net> (raw)
In-Reply-To: <CAJcAo8s8yr8dHcbCQibuH4Sqow+uY3FnFRJHeZDCbgPj=62uqw@mail.gmail.com> (Samuel Wales's message of "Mon, 19 Jun 2023 15:00:34 -0700")
> just now in normal usage, the y-or-n-p popped up in the middle of an isearch.
>
> point was in the middle of hte isearch still. it was not trivial to
> answer the y-or-n-p (point not there) and fix state.
Reading type-break.el raised some questions: please confirm does the same
problem occur after using the default value of 'type-break-query-function'
that is 'yes-or-no-p', and not 'y-or-n-p'?
It looks like type-break uses 'run-at-time' and then tries to
call 'y-or-n-p' in the middle of an isearch. I tried both
(run-with-timer 5 5 #'yes-or-no-p "OK? ")
(run-with-timer 5 5 #'y-or-n-p "OK? ")
and activated isearch. Then the typed answer was added
to the search string. Emacs 28 has an option
'y-or-n-p-use-read-key' that you can set for type-break
that pops up the query at random times. But the problem
still exists for 'yes-or-no-p'.
next prev parent reply other threads:[~2023-06-20 6:57 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 1:17 bug#64141: 27.1 newly has clunky type-break y-or-n-p Samuel Wales
2023-06-18 7:26 ` Eli Zaretskii
2023-06-18 23:55 ` Samuel Wales
2023-06-19 0:07 ` Samuel Wales
2023-06-19 22:00 ` Samuel Wales
2023-06-20 6:57 ` Juri Linkov [this message]
2023-06-20 11:47 ` Eli Zaretskii
2023-06-20 16:46 ` Juri Linkov
2023-06-20 22:44 ` Samuel Wales
2023-06-21 6:18 ` Juri Linkov
2023-06-21 6:49 ` Juri Linkov
2023-06-21 11:08 ` Eli Zaretskii
2023-06-21 15:54 ` Juri Linkov
2023-07-11 22:19 ` Samuel Wales
2023-07-12 6:43 ` Juri Linkov
2023-07-19 5:58 ` Samuel Wales
2023-07-19 6:41 ` Juri Linkov
2023-07-19 7:11 ` Samuel Wales
2023-07-23 5:26 ` Samuel Wales
2023-07-24 17:24 ` Juri Linkov
2023-09-02 22:04 ` Stefan Kangas
2023-06-21 11:25 ` Eli Zaretskii
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=86y1ker574.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=64141@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=samologist@gmail.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.