all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: Bob Rogers <rogers@rgrjr.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Uwe Brauer <oub@mat.ucm.es>,
	emacs-devel@gnu.org
Subject: Re: has the emoji support been enhanced on master?
Date: Sun, 12 Feb 2023 08:45:12 +0100	[thread overview]
Message-ID: <87a61jiayf.fsf@mat.ucm.es> (raw)
In-Reply-To: 25575.65199.775648.183146@orion.rgrjr.com

[-- Attachment #1: Type: text/plain, Size: 1096 bytes --]


>    From: Eli Zaretskii <eliz@gnu.org>
>    Date: Sat, 11 Feb 2023 21:41:53 +0200


>    Well, others do see it in Emacs, so it's still most probably something
>    local on your system.

> I am seeing the same symptoms as Uwe on openSUSE 15.4:  The first emoji
> shows in emacs but not the second, but both are visible in chrome.
> Moreover, I've had the distro-supplied noto-coloremoji-fonts RPM since I
> installed 15.4 last summer, so it would seem to be a difference between
> the way emacs and chrome go about finding that font.  But I don't know
> enough about that code to dig further.

Thanks for confirming. On my Ubuntu distribution (and I cannot upgrade
till summer) that font package is still not available so I installed it
manually, right now even in 

 /usr/share/fonsts/truetype

But it does not help.

I will try out Tim's suggestion but there seems a problem, Eli is not
facing, 

@Eli you are on windows, if I remember correctly: now another user confirmed
the problem on a different Linux distribution.

Any idea suggestion how to debug this?

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]

  reply	other threads:[~2023-02-12  7:45 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-11 14:39 has the emoji support been enhanced on master? Uwe Brauer
2023-02-11 15:31 ` Eli Zaretskii
2023-02-11 16:13   ` Uwe Brauer
2023-02-11 16:32     ` Eli Zaretskii
2023-02-11 17:06       ` Uwe Brauer
2023-02-11 17:13         ` Eli Zaretskii
2023-02-11 17:26           ` Uwe Brauer
2023-02-11 17:40             ` Eli Zaretskii
2023-02-11 19:17               ` Uwe Brauer
2023-02-11 19:21                 ` Eli Zaretskii
2023-02-11 19:38                   ` Uwe Brauer
2023-02-11 19:41                     ` Eli Zaretskii
2023-02-11 20:46                       ` Bob Rogers
2023-02-12  7:45                         ` Uwe Brauer [this message]
2023-02-12  8:05                           ` Eli Zaretskii
2023-02-12  9:26                             ` Uwe Brauer
2023-02-12 11:53                               ` Eli Zaretskii
2023-02-12 13:10                                 ` Uwe Brauer
2023-02-12 13:22                                   ` Eli Zaretskii
2023-02-12 20:19                                     ` Bob Rogers
2023-02-12 20:22                                       ` Eli Zaretskii
2023-02-12 20:44                                         ` Bob Rogers
2023-02-12  8:32                           ` Werner LEMBERG
2023-02-12  9:33                             ` Uwe Brauer
2023-02-12  9:59                               ` Werner LEMBERG
2023-02-12 10:34                                 ` Uwe Brauer
2023-02-12 12:14                                   ` Werner LEMBERG
2023-02-12 13:10                                     ` Uwe Brauer
2023-02-12 10:36                             ` Po Lu
2023-02-12 14:43                               ` Werner LEMBERG
2023-02-12 15:37                                 ` Po Lu
2023-02-12 16:56                               ` Benjamin Riefenstahl
2023-02-13  2:32                                 ` Po Lu
2023-02-13 14:25                                   ` Benjamin Riefenstahl
2023-02-13 15:08                                     ` Po Lu
2023-02-13 18:21                                       ` Benjamin Riefenstahl
2023-02-11 20:30                 ` Tim Cross

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=87a61jiayf.fsf@mat.ucm.es \
    --to=oub@mat.ucm.es \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rogers@rgrjr.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.