all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: 36288@debbugs.gnu.org
Subject: bug#36288: 27.0.50; Cannot use menu-set-font
Date: Sun, 23 Jun 2019 15:50:11 +0200	[thread overview]
Message-ID: <m2imswif70.fsf@gmail.com> (raw)
In-Reply-To: <wlk1dcg68g.wl-mituharu@math.s.chiba-u.ac.jp> (YAMAMOTO Mitsuharu's message of "Sun, 23 Jun 2019 15:34:23 +0900")

>>>>> On Sun, 23 Jun 2019 15:34:23 +0900, YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp> said:
    >> On second thought, it seems to be better to leave the font type
    >> unspecified.  Hard-coding the wanted font type was introduced as a
    >> "fix" for Bug#3228, but I suspect its reasoning is no longer valid (I
    >> couldn't find fonts.alias in the Type1 font directory in CentOS or
    >> Linux Mint).  Also, probably we should set the :family font property
    >> instead of :name.

Thanks, that fixed things for me, with font-backend '(xfthb x) and '(x xfthb)

Iʼve not looked at Bug#3228, but at least on my Ubuntu machine I have:

/usr/share/fonts/X11/Type1/fonts.alias
/usr/share/fonts/X11/misc/fonts.alias

but given the prevalence of opentype and truetype fonts, Iʼm not sure
that thereʼs anything to worry about.

Robert





  reply	other threads:[~2019-06-23 13:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19  7:48 bug#36288: 27.0.50; Cannot use menu-set-font Robert Pluim
2019-06-20  2:54 ` YAMAMOTO Mitsuharu
2019-06-20  7:51   ` Robert Pluim
2019-06-20  8:32     ` Robert Pluim
2019-06-20 12:56       ` Eli Zaretskii
2019-06-20 14:19         ` Robert Pluim
2019-06-20 16:21           ` Eli Zaretskii
2019-06-21 13:52             ` Robert Pluim
2019-06-23  6:34   ` YAMAMOTO Mitsuharu
2019-06-23 13:50     ` Robert Pluim [this message]
2019-06-30  7:02       ` YAMAMOTO Mitsuharu

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=m2imswif70.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=36288@debbugs.gnu.org \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    /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.