From: Arash Esbati <arash@gnu.org>
To: Visuwesh <visuweshm@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
larsi@gnus.org, juri@linkov.net, emacs-devel@gnu.org
Subject: Re: master 371c4f642a 1/2: Add new commands to zoom emojis
Date: Thu, 07 Jul 2022 11:42:25 +0200 [thread overview]
Message-ID: <86h73tz2bi.fsf@gnu.org> (raw)
In-Reply-To: <86sfnfh107.fsf@gnu.org> (Arash Esbati's message of "Tue, 05 Jul 2022 20:23:36 +0200")
[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]
Arash Esbati <arash@gnu.org> writes:
> Thanks, that works. Now I have this in my .emacs and 'C-x 8 e +' works
> as expected:
>
> (set-fontset-font t 'emoji
> (font-spec :family "Segoe UI Emoji"
> :registry "iso10646-1")
> nil 'prepend)
>
> (add-to-list 'face-font-rescale-alist
> '("Segoe UI Emoji" . 0.93)
> t)
Following up myself, I'm facing a strange behavior with the code above
in combination with:
(setq inhibit-splash-screen t)
I started Emacs with a minimal .emacs like this:
--8<---------------cut here---------------start------------->8---
;;; -*- lexical-binding: t; -*-
(set-fontset-font t 'emoji
(font-spec :family "Segoe UI Emoji"
:registry "iso10646-1")
nil 'prepend)
(add-to-list 'face-font-rescale-alist
'("Segoe UI Emoji" . 0.93))
(setq inhibit-splash-screen t)
(custom-set-faces
'(default ((t (:family "Source Code Pro Medium" :foundry "outline" :slant normal :weight medium :height 90 :width normal)))))
--8<---------------cut here---------------end--------------->8---
Then I hit 'C-x 5 2' and the new frame is opened with Arial and not with
Source Code Pro like this:
[-- Attachment #2: x.png --]
[-- Type: image/png, Size: 82469 bytes --]
[-- Attachment #3: Type: text/plain, Size: 170 bytes --]
If I comment out either the face-font-rescale-alist or the
inhibit-splash-screen part, the new frame pops up with Source Code Pro.
Am I missing something?
Best, Arash
next prev parent reply other threads:[~2022-07-07 9:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165657886980.22137.11785189028438514501@vcs2.savannah.gnu.org>
[not found] ` <20220630084754.DED31C016A1@vcs2.savannah.gnu.org>
2022-06-30 9:18 ` master 371c4f642a 1/2: Add new commands to zoom emojis Lars Ingebrigtsen
2022-06-30 14:59 ` [External] : " Drew Adams
2022-06-30 16:10 ` Juri Linkov
2022-07-01 9:15 ` Lars Ingebrigtsen
2022-07-01 15:36 ` Juri Linkov
2022-07-04 16:57 ` Arash Esbati
2022-07-04 17:03 ` Eli Zaretskii
2022-07-04 17:23 ` Arash Esbati
2022-07-04 17:40 ` Eli Zaretskii
2022-07-04 18:06 ` Arash Esbati
2022-07-04 18:14 ` Eli Zaretskii
2022-07-05 7:15 ` Arash Esbati
2022-07-05 11:00 ` Eli Zaretskii
2022-07-05 12:40 ` Arash Esbati
2022-07-05 11:18 ` Lars Ingebrigtsen
2022-07-05 11:35 ` Eli Zaretskii
2022-07-05 12:34 ` Arash Esbati
2022-07-05 12:58 ` Eli Zaretskii
2022-07-05 12:55 ` Visuwesh
2022-07-05 18:23 ` Arash Esbati
2022-07-07 9:42 ` Arash Esbati [this message]
2022-07-07 10:50 ` Eli Zaretskii
2022-07-10 8:35 ` Eli Zaretskii
2022-07-10 17:01 ` Arash Esbati
2022-07-10 17:09 ` Eli Zaretskii
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=86h73tz2bi.fsf@gnu.org \
--to=arash@gnu.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=visuweshm@gmail.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 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).