From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Note on e65c307 breaks font-height Date: Sat, 04 Jun 2016 10:28:43 +0300 Message-ID: <83shwtwgyc.fsf@gnu.org> References: <5746D38F.4010203@gmx.at> <4cdc1b55-2fe2-2457-1115-33ff68a9a65d@cs.ucla.edu> <5748490A.6020906@gmx.at> <8337p2zdt5.fsf@gnu.org> <574AF1ED.7020404@gmx.at> <837fecykbd.fsf@gnu.org> <574BF309.7070701@gmx.at> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: ger.gmane.org 1465025314 23463 80.91.229.3 (4 Jun 2016 07:28:34 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 4 Jun 2016 07:28:34 +0000 (UTC) Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org To: martin rudalics Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 04 09:28:29 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1b960Q-0000MP-Cq for ged-emacs-devel@m.gmane.org; Sat, 04 Jun 2016 09:28:26 +0200 Original-Received: from localhost ([::1]:59723 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b960P-0005iL-EB for ged-emacs-devel@m.gmane.org; Sat, 04 Jun 2016 03:28:25 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37626) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b960K-0005iG-4Z for emacs-devel@gnu.org; Sat, 04 Jun 2016 03:28:21 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b960G-00076v-TV for emacs-devel@gnu.org; Sat, 04 Jun 2016 03:28:20 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:35451) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b960G-00076C-Q1; Sat, 04 Jun 2016 03:28:16 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:2225 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1b960E-0000RI-RT; Sat, 04 Jun 2016 03:28:15 -0400 In-reply-to: <574BF309.7070701@gmx.at> (message from martin rudalics on Mon, 30 May 2016 10:00:09 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:204183 Archived-At: > Date: Mon, 30 May 2016 10:00:09 +0200 > From: martin rudalics > CC: eggert@cs.ucla.edu, emacs-devel@gnu.org > > >> Maybe because I also want to specify things like 'background', 'box' > >> or 'underline' for my faces. > > > > You can specify these separately. > > But it's easier to look at all of them in one and the same customization > buffer. At least that's what a beginner would do IMO. Not sure about beginners (as this is not newbie stuff at all). I agree that it would be more convenient to specify them all, but we don't have such a facility. What you did instead is instruct the font selection process about some of your preferences. Try stepping through the code which implements font/fontset selection, and if you don't get lost immediately, you will see how many semi-arbitrary decisions that code makes. 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. > > I'm not sure I follow: isn't the default face supposed to be per > > frame? > > That's the way it's implemented. But where do we tell that in our > documentations? -- 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. It will do no harm, though, to say that explicitly at the beginning of the chapter; patches welcome. > >> Lisp Backtrace: > >> "internal-set-lisp-face-attribute" (0xffffb4f0) > >> "set-face-attribute" (0xffffbd70) > >> "font-setting-change-default-font" (0xffffc620) > >> "dynamic-setting-handle-config-changed-event" (0xffffcfb0) > >> "funcall-interactively" (0xffffcfa8) > >> "call-interactively" (0xffffd460) > >> "command-execute" (0xffffdd28) > > > > Hmm... why is command-execute in the backtrace? Isn't this Emacs > > starting up? > > Apparently we get a config-changed-event during start-up. Does anyone > know how these get injected? I'm not sure I follow: command-execute is called by startup.el only once: if there's a -f SOMETHING command-line argument. Is that what happened in your case? > > then can you > > show the backtrace from the first time this breakpoint breaks? > > OK. Below you'll get more than you asked for. The breakpoint is hit > four times, the third (with a value of 15) when my .emacs is read and > the fourth (with a value of 18 again) when the > ‘dynamic-setting-handle-config-changed-event’ is processed (the fourth > is the one I posted before). Thanks, I will look into that and see what it tells.