unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: larsi@gnus.org, 60740@debbugs.gnu.org, juri@linkov.net
Subject: bug#60740: 29.0.60; Broken isearch-emoji-by-name
Date: Mon, 30 Jan 2023 15:10:01 +0200	[thread overview]
Message-ID: <837cx45fti.fsf@gnu.org> (raw)
In-Reply-To: <87bkmgxub5.fsf@bernoul.li> (message from Jonas Bernoulli on Mon,  30 Jan 2023 10:09:34 +0100)

> From: Jonas Bernoulli <jonas@bernoul.li>
> Cc: larsi@gnus.org, 60740@debbugs.gnu.org, juri@linkov.net
> Date: Mon, 30 Jan 2023 10:09:34 +0100
> 
> Unfortunately there is a major bug in transient, which I am struggling
> to fix.  I have a working solution but it is quite abstruse and still
> needs testing.  I also have a nicer solution that doesn't really work
> yet.  If I knew I had time, I would work on the latter.  But since the
> pre-release could happen any time now, I should probably work on the
> former.

What kind of time frame are you talking when you say "if I knew I had
time"?

> Please warn me a day before you create the pre-release, so I can switch
> my focus in time to merge the best solution I can come up by then into
> Emacs.

Will do.

> I probably won't have time to fix isearch-emoji-by-name by then.  One
> problem is that emoji (not just this particular command) uses transient
> in a way it was never intended to be used.  I pointed that out when it
> was originally added.  But somehow it worked, so I never got around to
> redo it.
> 
> I have actually rewritten how emoji uses transient a day ago, and while
> it works in principal, it is not finished yet.  I had some faint hope
> that doing so would also magically fix isearch-emoji-by-name.  It did
> not.  But it lays the ground work for doing that eventually.
> 
> I don't have the time to do that anymore.  It would probably be best to
> remove this command from Emacs 29.0.90.

Since the command works for many Emoji, I prefer to leave it and live
with the known issues.

Thanks.





  reply	other threads:[~2023-01-30 13:10 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
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 [this message]
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=837cx45fti.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=60740@debbugs.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).