unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Tor Kringeland <tor.kringeland@ntnu.no>
Cc: 58632@debbugs.gnu.org
Subject: bug#58632: Setting Apple's emoji font on macOS in daemon mode
Date: Wed, 19 Oct 2022 15:27:22 +0200	[thread overview]
Message-ID: <874jw0ueo5.fsf@gmail.com> (raw)
In-Reply-To: <m2h700hunc.fsf@ntnu.no> (Tor Kringeland's message of "Wed, 19 Oct 2022 12:20:53 +0000")

>>>>> On Wed, 19 Oct 2022 12:20:53 +0000, Tor Kringeland <tor.kringeland@ntnu.no> said:

    Tor> Minimal reproducing example:
    Tor> Run

    Tor>   emacs -Q --daemon --eval "(set-fontset-font t 'unicode \"Apple Color Emoji\")"

    Tor> and insert an emoji.  It will not be rendered by the Apple Color Emoji
    Tor> font.  This wasn't the case on the build from a week or two ago (and
    Tor> builds for many months before that).

I find that surprising, Iʼd expect it to never work. Can you identify
exactly when it changed? And please do

    (set-fontset-font t 'emoji \"Apple Color Emoji\")

What you have slows down font lookup for all codepoints.

    Tor> It works if I do not run Emacs in
    Tor> daemon mode or explicitly set the font after having connected a client.
    Tor> Is this a bug or is there another way I should specify the emoji font?

Emacs in daemon mode doesnʼt have a gui frame to work with, so things
like setting fonts tend not to work [1]. You can either use
`default-frame-alist' to set the `font' frame parameter, or you can
add code to `server-after-make-frame-hook' to set it.

Iʼm not saying there isnʼt a bug, but Iʼm not saying there is one
either 😀

Robert

Footnotes:
[1]  Iʼll admit to not understanding the attraction of daemon-mode,
     but I guess tastes differ.

-- 





  reply	other threads:[~2022-10-19 13:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-19 12:20 bug#58632: Setting Apple's emoji font on macOS in daemon mode Tor Kringeland
2022-10-19 13:27 ` Robert Pluim [this message]
2023-09-03  9:31   ` Stefan Kangas

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=874jw0ueo5.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=58632@debbugs.gnu.org \
    --cc=tor.kringeland@ntnu.no \
    /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).