From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org
Subject: Re: Note on e65c307 breaks font-height
Date: Sat, 04 Jun 2016 13:52:09 +0300 [thread overview]
Message-ID: <83vb1pusyu.fsf@gnu.org> (raw)
In-Reply-To: <5752A3DA.3020009@gmx.at> (message from martin rudalics on Sat, 04 Jun 2016 11:48:10 +0200)
> Date: Sat, 04 Jun 2016 11:48:10 +0200
> From: martin rudalics <rudalics@gmx.at>
> CC: eggert@cs.ucla.edu, emacs-devel@gnu.org
>
> > IOW, the font selection code was not designed to support what you'd
> > like, not in general. That is why I strongly recommend to just state
> > a specific font of your liking, and move on.
>
> What I did (in the previous century, IIRC) was to select the procedure
> that I then considered best supported by the customization interface.
> Can you point me to a similar interface for the step you propose? IOW,
> I still think that mine is the way a newbie would use.
I don't understand why we are talking about customization interfaces.
I thought the problem was that requesting a font by specifying some of
its attributes doesn't work. Now I'm confused: what problem is at
hand?
> > -- Function: face-attribute face attribute &optional frame inherit
> > This function returns the value of the ATTRIBUTE attribute for FACE
> > on FRAME.
> >
> > And all the other functions in that node accept the FRAME argument.
>
> IIUC none of these bear any relation to the customization interface.
"M-x customize-face" changes the face definitions on all frames, but
you can invoke set-face-attribute with a specific frame to change the
face only on that frame.
> And I still don't see where the customization framework allows or
> suggests to specifiy a face for a frame or for "any" frame.
I don't think it does.
In any case, it looks like a simple question of mine led us aside for
no good reason. Whether faces are or aren't per frame has nothing to
do with the problem at hand.
next prev parent reply other threads:[~2016-06-04 10:52 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-26 10:44 Note on e65c307 breaks font-height martin rudalics
2016-05-26 15:05 ` Paul Eggert
2016-05-26 15:22 ` Eli Zaretskii
2016-05-26 15:33 ` Paul Eggert
2016-05-26 15:50 ` Eli Zaretskii
2016-05-26 15:57 ` Paul Eggert
2016-05-26 16:33 ` Eli Zaretskii
2016-05-27 13:18 ` martin rudalics
2016-05-28 10:17 ` Eli Zaretskii
2016-05-29 13:43 ` martin rudalics
2016-05-29 15:07 ` Eli Zaretskii
2016-05-30 8:00 ` martin rudalics
2016-06-04 7:28 ` Eli Zaretskii
2016-06-04 9:48 ` martin rudalics
2016-06-04 10:52 ` Eli Zaretskii [this message]
2016-06-04 13:07 ` martin rudalics
2016-05-28 10:38 ` Paul Eggert
2016-05-29 13:43 ` martin rudalics
2016-05-29 17:14 ` Paul Eggert
2016-05-30 8:00 ` martin rudalics
2016-05-26 15:16 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83vb1pusyu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
/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.