From: Paul Moore <p.f.moore@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 23689@debbugs.gnu.org
Subject: bug#23689: Daemon-mode on Windows - "w32-initialized" is set too early
Date: Tue, 14 Jun 2016 19:20:27 +0100 [thread overview]
Message-ID: <CACac1F8TBLs1T+H4uhqgNi+cY5dHZ8y1=da0LdVT0WfgP9_TXA@mail.gmail.com> (raw)
In-Reply-To: <83k2hrelwy.fsf@gnu.org>
On 14 June 2016 at 18:10, Eli Zaretskii <eliz@gnu.org> wrote:
>> What we're doing is attempting to select a font from a list provided
>> by the user.
>
> What do you mean by "select a font"? If the font you want to use is
> known in advance, then a parameter in default-frame-alist should be
> all you need. If the font is not known in advance, then how do you
> "select" it?
The user supplies a *list* of fonts. The code then goes through those
fonts in turn, checking (via find-font) whether the font exists, and
if it does, then sets it as the frame font and adds it to
default-frame-alist for the future.
The point here is for users who want to move their config between
machines, and don't always have the same fonts installed - so they
would typically put their preferred font first in the list, with
fallback options following.
Paul
next prev parent reply other threads:[~2016-06-14 18:20 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-03 10:33 bug#23689: Daemon-mode on Windows - "w32-initialized" is set too early Paul Moore
2016-06-04 10:07 ` Eli Zaretskii
2016-06-04 10:29 ` Paul Moore
2016-06-04 10:58 ` Eli Zaretskii
2016-06-04 12:54 ` Paul Moore
2016-06-04 15:01 ` Eli Zaretskii
2016-06-04 15:17 ` Paul Moore
2016-06-08 13:57 ` Paul Moore
2016-06-14 17:10 ` Eli Zaretskii
2016-06-14 18:20 ` Paul Moore [this message]
2016-06-14 18:55 ` Eli Zaretskii
2016-06-14 19:55 ` Paul Moore
2016-06-15 2:33 ` Eli Zaretskii
2016-06-15 7:08 ` Paul Moore
2016-06-15 11:11 ` Paul Moore
2016-06-15 14:55 ` Eli Zaretskii
2016-06-15 15:26 ` Paul Moore
2016-06-15 15:47 ` Eli Zaretskii
2016-06-15 16:58 ` Paul Moore
2019-11-02 1:07 ` 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='CACac1F8TBLs1T+H4uhqgNi+cY5dHZ8y1=da0LdVT0WfgP9_TXA@mail.gmail.com' \
--to=p.f.moore@gmail.com \
--cc=23689@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).