From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: rudalics@gmx.at, emacs-devel@gnu.org
Subject: Re: Note on e65c307 breaks font-height
Date: Thu, 26 May 2016 18:50:05 +0300 [thread overview]
Message-ID: <8360u03jki.fsf@gnu.org> (raw)
In-Reply-To: <1fef7fee-835b-b5f4-f69c-ebd4ac14251c@cs.ucla.edu> (message from Paul Eggert on Thu, 26 May 2016 08:33:08 -0700)
> Cc: rudalics@gmx.at, emacs-devel@gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Thu, 26 May 2016 08:33:08 -0700
>
> On 05/26/2016 08:22 AM, Eli Zaretskii wrote:
> > we should debug the problem,
> > understand exactly why it happens, and only then discuss how to fix it
> > on the release branch.
>
> Yes, and my patch was an attempt to be part of the first step in doing
> that; it was part of a series of questions I gave to Martin about his
> configuration and what sort of perturbations make it work or not work. I
> had no intent to install the patch willy-nilly. Sorry if I wasn't clear.
No, it wasn't clear.
And you do see the difference between the frame's font parameter and
the font of the frame's default face, yes?
next prev parent reply other threads:[~2016-05-26 15:50 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 [this message]
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
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
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=8360u03jki.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 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).