From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: Note on e65c307 breaks font-height Date: Sat, 04 Jun 2016 11:48:10 +0200 Message-ID: <5752A3DA.3020009@gmx.at> 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> <83shwtwgyc.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: ger.gmane.org 1465033736 9422 80.91.229.3 (4 Jun 2016 09:48:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 4 Jun 2016 09:48:56 +0000 (UTC) Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jun 04 11:48:47 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 1b98CE-0002Il-JF for ged-emacs-devel@m.gmane.org; Sat, 04 Jun 2016 11:48:46 +0200 Original-Received: from localhost ([::1]:60124 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b98CE-0001Wi-0H for ged-emacs-devel@m.gmane.org; Sat, 04 Jun 2016 05:48:46 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58524) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b98C6-0001Vj-Iy for emacs-devel@gnu.org; Sat, 04 Jun 2016 05:48:39 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1b98C4-0000fc-1W for emacs-devel@gnu.org; Sat, 04 Jun 2016 05:48:37 -0400 Original-Received: from mout.gmx.net ([212.227.17.22]:52169) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1b98Bz-0000fC-Op; Sat, 04 Jun 2016 05:48:32 -0400 Original-Received: from [192.168.1.101] ([212.95.7.93]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0Lf0M7-1bpbkE12ul-00qlcN; Sat, 04 Jun 2016 11:48:17 +0200 In-Reply-To: <83shwtwgyc.fsf@gnu.org> X-Provags-ID: V03:K0:lTsgAX3YmB11BKTTc2SrU9b0KbEAdTdwiBwbRc7uWQ4DTNR1m/r fQ99JIDm18a1oRgA8vyncAfKsUBx7p1LJ8DqFzP+gXGhFc5dB7v2Zm7lXq1mNCvqHLoCw9W p81ZMNnJjq7JylZw/pDqwy5tP/soFG3ZjVpkNnk4AdPujf9189OOJlBjSyj628vRAnZ1XNM lfm2rxKTMpZznN2bOcFUA== X-UI-Out-Filterresults: notjunk:1;V01:K0:jgZowHNDv8g=:bNnGdI0pN+cF1fiawCGvMT /Kl5SGEgTkSEPhgIiO8SZCfjbDpWPSQxgouRL+xrh3WbclLy8IvS/KSfqwPUNI3oSE4BWJQCy GOStNq2DWIm4avCKPsUg/oXU0WHszsAH/zyxyyefiZ/0d3ZL5GtvrImzR53s4g+OJ9hipgGrz uDVuBChMLsfqpeo8H26Xo/cWK+5dKHO8lx2lauy3TY73atwW+OXReANasmPYC9hqgxXhePS1D gYElwKvXZGD5CPgWf8+E7vWJunCL1nOkU/ng+WeKY5INFYOiooYc49gAUmjlwnPvyb5AnTfe0 DhssuokHr6Wl7jdlChUCQ/PXu2PX+cBq4Na70W0ASgm9O76PzNXfM9dTVF7Q5LxSoB9vgasDa hCDS8RI7p3inZ33NfEX557nNe17w0/Rp6DKHc9yijnv+M5UNy7gGOWZKzCMljTA1D3y9pBS5F m0mMzYB8ITTPC5+XuHq1hD4p+YV2uKKz0ENWbWREUVDpU75qArLgxo1p9UwlLyRaTr2/jUyXR WJgJNZenWsL8T7QmtAK1GVcvKg4/lz25P5GVVr3wCBEVffjfuq3PsXw1P07LjjB0kli6vACJu eTRS2deQnUuQbC2iK/5vSOMeYpfIb4k1NVa1iCa7FegVP0P46juyh7pTZGJKRVsRSlm7X4eSR cSWRW1Cvbg+Bjcoah0VSqzUsqUv7RjI04AzuxNRBJLU+Aq7DpkIVOkDF40WC3kCM2AjY7fVCd A+OS9uNomkRNBxSC4GPaSxhtBmNNfQs3L8JJ31FX4EyfLLyZuoXijV+end4KY1AiezAwZ+zz X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 212.227.17.22 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:204188 Archived-At: >> But it's easier to look at all of them in one and the same customizat= ion >> 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. 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'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 F= ACE > 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. When someone wants to save a face attribute in her .emacs, she usually wants to do that for "all frames created in the future". There's no specific frame at that time. And I still don't see where the customization framework allows or suggests to specifiy a face for a frame or for "any" frame. > It will do no harm, though, to say that explicitly at the beginning of= > the chapter; patches welcome. I don't want to talk you into anything. But I think that this part of the customization interface is still missing something important. Till then, the documentation should describe how to achieve the desired setting. >> >> 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 anyon= e >> 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? No. The event is stored there by apply_xft_settings in that line store_config_changed_event (Qfont_render, XCAR (dpyinfo->name_list_element)); All this is severely underdocumented and undercommented :-( > Thanks, I will look into that and see what it tells. Currently, I defalias =E2=80=98dynamic-setting-handle-config-changed-even= t=E2=80=99 to =E2=80=98ignore=E2=80=99. I don't think we can recommend that to users. = Maybe we should invent a new option like =E2=80=98x-handle-configuration-changes=E2= =80=99 which defaults to t. Users encoutering problems like me could then set it to nil in their .emacs. In any case, I think that this part has not been given much testing due to the bug Paul uncovered. martin