unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Gregory Heytings <gregory@heytings.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	monnier@iro.umontreal.ca, 64024@debbugs.gnu.org
Subject: bug#64024: 29.0.91; `emoji-insert` shows me confusing empty lists
Date: Thu, 15 Jun 2023 10:30:41 +0200	[thread overview]
Message-ID: <87zg51dt5a.fsf@gmail.com> (raw)
In-Reply-To: <2e319d6dd8ae9e3f7b9e@heytings.org> (Gregory Heytings's message of "Thu, 15 Jun 2023 08:12:45 +0000")

>>>>> On Thu, 15 Jun 2023 08:12:45 +0000, Gregory Heytings <gregory@heytings.org> said:

    >>>>> Perhaps the emoji-* commands (C-x 8 e [eilrs]) should simply
    >>>>> error out when (list-fonts (font-spec :script 'emoji)) is nil?
    >>>>

That would stop you using them in tty frames, where they work fine.

    >>>> FWIW, I do like being able to insert some emojis even if I don't
    >>>> have access to all of them (and actually I'd even be happy to
    >>>> insert them without being able to see them, assuming I can see
    >>>> their name instead :-)
    >>> 
    >>> Yes, but you can still do that with C-x 8 RET, right?  The C-x 8 e
    >>> commands use transient menus, and (as you described in the bug
    >>> report) don't quite work when a suitable emoji font is not
    >>> available.
    >>> 
    >>> In theory, another option would be to display, in these transient
    >>> menus, emoji names instead of emoji characters when no emoji font
    >>> is available, but there is not enough room for list of names such
    >>> as "SMILING FACE WITH SMILING EYES AND HAND COVERING MOUTH" (which
    >>> fit better in *Completions*).
    >>

"C-x 8 e s" already does that, we could extend it to "C-x 8 e e". Once
youʼre down to half a dozen emoji it should fit fine.

Robert
-- 





  reply	other threads:[~2023-06-15  8:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-12 18:15 bug#64024: 29.0.91; `emoji-insert` shows me confusing empty lists Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-13  2:29 ` Eli Zaretskii
2023-06-14 20:49   ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-14 21:36   ` Gregory Heytings
2023-06-14 22:49     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-14 23:05       ` Gregory Heytings
2023-06-15  5:17         ` Eli Zaretskii
2023-06-15  8:12           ` Gregory Heytings
2023-06-15  8:30             ` Robert Pluim [this message]
2023-06-15  8:41               ` Gregory Heytings
2023-06-15  8:44                 ` Gregory Heytings

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=87zg51dt5a.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=64024@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=gregory@heytings.org \
    --cc=monnier@iro.umontreal.ca \
    /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).