unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
	Jonas Bernoulli <jonas@bernoul.li>,
	60740@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#60740: 29.0.60; Broken isearch-emoji-by-name
Date: Thu, 12 Jan 2023 10:57:34 +0100	[thread overview]
Message-ID: <87mt6of52p.fsf@gmail.com> (raw)
In-Reply-To: <838ri8krtv.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 12 Jan 2023 11:47:08 +0200")

>>>>> On Thu, 12 Jan 2023 11:47:08 +0200, Eli Zaretskii <eliz@gnu.org> said:

    >> But typing e.g. 'C-s C-x 8 e RET waving hand RET' fails with:
    >> 
    >> ⛔ Error (transient): Inconsistent transient state detected.
    >> This should never happen.
    >> Please open an issue and post the shown command log.
    >> This is a heisenbug, so any additional details might help.
    >> Thanks!

I get it straight from 'emacs -Q', so obviously the quantum
probabilities are different here 😀

    Eli> Looks like a problem with any Emoji that has variants, where you need
    Eli> to select one of the variants?

Could be. The transient command log looks like this:

    e           ;; transient:emoji--command-Choose Emoji:👋🏾
    C-s         ;; isearch-repeat-forward
    C-x 8 e RET ;; isearch-emoji-by-name
    w           ;; self-insert-command
    a           ;; self-insert-command
    v           ;; self-insert-command
    i           ;; self-insert-command
    n           ;; self-insert-command
    g           ;; self-insert-command
    SPC         ;; minibuffer-complete-word
    h           ;; self-insert-command
    a           ;; self-insert-command
    n           ;; self-insert-command
    d           ;; self-insert-command
    RET         ;; minibuffer-complete-and-exit
    e           ;; isearch-printing-char

(should that really be calling `isearch-printing-char' at the end
there?)

'C-x 8 e RET' for the same emoji works fine.

Robert
-- 





  reply	other threads:[~2023-01-12  9:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11 19:45 bug#60740: 29.0.60; Broken isearch-emoji-by-name Juri Linkov
2023-01-12  9:47 ` Eli Zaretskii
2023-01-12  9:57   ` Robert Pluim [this message]
2023-01-12 11:25   ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-12 17:29     ` Juri Linkov
2023-01-21  7:24   ` Eli Zaretskii
2023-01-22 19:25   ` Jonas Bernoulli
2023-01-23  7:06     ` Kévin Le Gouguec
2023-01-23 12:09     ` Eli Zaretskii
2023-01-26  7:45       ` Eli Zaretskii
2023-01-26 15:43         ` Jonas Bernoulli
2023-01-26 16:38           ` Eli Zaretskii
2023-01-30  9:09             ` Jonas Bernoulli
2023-01-30 13:10               ` Eli Zaretskii
2023-01-30 17:40                 ` Juri Linkov
2023-01-30 18:03                   ` Eli Zaretskii
2023-01-30 18:12                     ` Juri Linkov

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=87mt6of52p.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=60740@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jonas@bernoul.li \
    --cc=juri@linkov.net \
    --cc=larsi@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.
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).