unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Kenichi Handa <handa@m17n.org>
Cc: monnier@iro.umontreal.ca, cloos@jhcloos.com, emacs-devel@gnu.org
Subject: Re: Fixed-pitch and variable-pitch faces
Date: Mon, 09 Jun 2008 00:49:53 -0400	[thread overview]
Message-ID: <87bq2bus9a.fsf@stupidchicken.com> (raw)
In-Reply-To: <E1K5Xbt-0005vU-Gy@etlken.m17n.org> (Kenichi Handa's message of "Mon, 09 Jun 2008 11:59:53 +0900")

Kenichi Handa <handa@m17n.org> writes:

> As far as I know, fontconfig's API FcFontMatch is very
> difficult to use here.  It always returns a font that
> fontconfig thinks best matching with the given pattern.  If
> the family name of the returned font is different from the
> requested one, there's no way to know whether the requested
> family name is remapped (or selected as an alias) by some
> config file or not.
>
> So, Emacs currently uses FcFontList only (except for such
> generic families; monospace, sans-serit, serif).

I see.

What if Emacs always uses FcFontMatch if it's compiled with fontconfig
support?  IIUC, this means that fonts using the x font backend are never
selected, since fontconfig will always try to find a match.  But this
may be acceptable in practice.

The alternative is to keep things as they are now, and deprecate the use
of the `fixed-pitch' and `variable-pitch' faces within Emacs.  Stop
using them in the startup screen.  This is not really optimal, since the
underlying problem is unsolved.  In particular, there would be no way
for an Elisp package to say "use an anti-alised courier font" and have
it work reliably.

WDYT?

> In your case, what is returned by this?
> % fc-list courier

~ $ fc-list courier
~ $ 

This is on Ubuntu 8.04.




  reply	other threads:[~2008-06-09  4:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-07 16:23 Fixed-pitch and variable-pitch faces Chong Yidong
2008-06-07 16:28 ` Chong Yidong
2008-06-07 18:56 ` Stefan Monnier
2008-06-07 20:33   ` David Hansen
2008-06-07 21:34   ` James Cloos
2008-06-08 11:29     ` Kenichi Handa
2008-06-09  1:29       ` Chong Yidong
2008-06-09  2:59         ` Kenichi Handa
2008-06-09  4:49           ` Chong Yidong [this message]
2008-06-09  5:17             ` Miles Bader
2008-06-09  5:34               ` Kenichi Handa
2008-06-09  6:14                 ` Miles Bader
2008-06-09  6:20                   ` Miles Bader
2008-06-09  7:20                     ` Kenichi Handa
2008-06-09  7:56                       ` Miles Bader
2008-06-09 11:06                         ` Kenichi Handa
2008-06-09 11:38                           ` Miles Bader
2008-06-09 12:06                             ` Kenichi Handa
2008-06-09 12:09                               ` Miles Bader
2008-06-09 11:26                         ` Kenichi Handa
2008-06-09  6:35                   ` Kenichi Handa
2008-06-09  6:41                     ` Miles Bader
2008-06-09 13:40                 ` Chong Yidong
2008-06-10  1:06                 ` Stefan Monnier
2008-06-10  1:44                   ` David De La Harpe Golden
2008-06-10  8:01                     ` James Cloos

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=87bq2bus9a.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=cloos@jhcloos.com \
    --cc=emacs-devel@gnu.org \
    --cc=handa@m17n.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).