From: Eli Zaretskii <eliz@gnu.org>
To: Mark Oteiza <mvoteiza@udel.edu>
Cc: emacs-devel@gnu.org
Subject: Re: master d014a5e: Use fixed-pitch font for display-line-numbers
Date: Wed, 12 Jul 2017 17:25:07 +0300 [thread overview]
Message-ID: <83lgntivgc.fsf@gnu.org> (raw)
In-Reply-To: <20170712031800.GA7133@holos.localdomain> (message from Mark Oteiza on Tue, 11 Jul 2017 23:18:00 -0400)
> Date: Tue, 11 Jul 2017 23:18:00 -0400
> From: Mark Oteiza <mvoteiza@udel.edu>
> Cc: emacs-devel@gnu.org
>
> > One disadvantage of that is that now any changes to fixed-pitch-serif
> > must also consider their effect on line-number.
>
> Ah, I considered it a good thing to have one less place where
> a particular typeface (well, in this case an alias) is specified.
> I think of fixed-pitch, fixed-pitch-serif, and variable-pitch as places
> to pick a family so other faces can inherit from them by default.
>
> Put another way, one would only have to change one face to change the
> monospace serif, instead of however each face specifying :family
> "Monospace Serif" or some other typeface. Though, perhaps I'm
> misunderstanding face-font-family-alternatives.
That's indeed the dilemma here: on the one hand this makes it easier
to change several faces, but OTOH the change must also satisfy the
requirements and user expectations of each of the inheriting faces. I
don't know which of these is more important. In practice, we did have
a couple of cases where some face was changed, and many moons later
someone complained that this had an adverse effect on one of the
inheriting faces.
next prev parent reply other threads:[~2017-07-12 14:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170711151708.4322.33014@vcs0.savannah.gnu.org>
[not found] ` <20170711151709.2AE9822E0A@vcs0.savannah.gnu.org>
2017-07-12 0:09 ` master d014a5e: Use fixed-pitch font for display-line-numbers Mark Oteiza
2017-07-12 2:39 ` Eli Zaretskii
2017-07-12 3:18 ` Mark Oteiza
2017-07-12 14:25 ` Eli Zaretskii [this message]
2017-07-13 20:18 ` Nicolas Petton
2017-07-14 6:30 ` Eli Zaretskii
2017-07-14 7:43 ` James Cloos
2017-07-14 11:16 ` Nicolas Petton
2017-07-14 12:38 ` Eli Zaretskii
2017-07-12 8:06 ` Yuri Khan
2017-07-12 14:36 ` Eli Zaretskii
2017-07-13 6:13 ` Yuri Khan
2017-07-13 15:57 ` Eli Zaretskii
2017-07-13 18:07 ` Yuri Khan
2017-07-13 19:02 ` Eli Zaretskii
2017-07-13 19:17 ` Yuri Khan
2017-07-13 19:49 ` Eli Zaretskii
2017-07-13 20:15 ` Alex
2017-07-14 6:47 ` Alex
2017-07-14 7:12 ` Eli Zaretskii
2017-07-14 6:56 ` Eli Zaretskii
2017-07-15 0:09 ` Alex
2017-07-15 7:08 ` Eli Zaretskii
2017-07-14 3:00 ` Stefan Monnier
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=83lgntivgc.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mvoteiza@udel.edu \
/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.