From: Paul Eggert <eggert@cs.ucla.edu>
To: Rostislav Svoboda <rostislav.svoboda@gmail.com>,
"emacs-devel@gnu.org Development" <emacs-devel@gnu.org>
Subject: Re: [bug-report] e65c307 breaks font-height
Date: Tue, 29 Mar 2016 18:47:30 -0700 [thread overview]
Message-ID: <56FB3032.6030104@cs.ucla.edu> (raw)
In-Reply-To: <CAEtmmexx2U0Eakxo9MBteGutQ3vJNk-2ZkUcz-R6jcWFAp22NQ@mail.gmail.com>
On 03/29/2016 05:48 AM, Rostislav Svoboda wrote:
> It looks like the semicolon in ":user-spec" causes unexpected
> font-height increase.
> I'm not sure if screenshots help:
> http://picpaste.com/emacs-bad-e65c307.png
> http://picpaste.com/emacs-good-c8b868b.png
>
> Is there a problem in the e65c307 or in my emacs configuration?
It's pretty clear that the intent here (and elsewhere in Emacs) is that
the C identifier 'QCuser_spec' stands for the Emacs symbol ':user-spec',
not for the Emacs symbol 'user-spec'.
It is possible that the change exposed some other bug in Emacs (perhaps
related to font-setting-change-default-font? perhaps you could put a
breakpoint on that function and see what it's doing). Or, it's
conceivable that your Emacs configuration uses 'user-spec' where it
should use ':user-spec'.
> thx Bost
>
>
> ~/dev/emacs-25 $ git show
> commit e65c3079c65595d95749348366af9811fafff062
> Author: Paul Eggert<eggert@cs.ucla.edu>
> Date: Sun Mar 27 15:02:37 2016 -0700
>
> * src/font.c (QCuser_spec): Add missing colon to :user-spec.
>
> diff --git a/src/font.c b/src/font.c
> index 5ab3b3e..2519599 100644
> --- a/src/font.c
> +++ b/src/font.c
> @@ -5317,7 +5317,7 @@ syms_of_font (void)
> DEFSYM (Qja, "ja");
> DEFSYM (Qko, "ko");
>
> - DEFSYM (QCuser_spec, "user-spec");
> + DEFSYM (QCuser_spec, ":user-spec");
next prev parent reply other threads:[~2016-03-30 1:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-29 12:48 [bug-report] e65c307 breaks font-height Rostislav Svoboda
2016-03-30 1:47 ` Paul Eggert [this message]
2016-03-31 9:10 ` Rostislav Svoboda
2016-04-01 9:24 ` Paul Eggert
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=56FB3032.6030104@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=rostislav.svoboda@gmail.com \
/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).