From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: master d014a5e: Use fixed-pitch font for display-line-numbers Date: Thu, 13 Jul 2017 22:02:24 +0300 Message-ID: <83k23cgny7.fsf@gnu.org> References: <20170711151708.4322.33014@vcs0.savannah.gnu.org> <20170711151709.2AE9822E0A@vcs0.savannah.gnu.org> <8760eyv7mc.fsf@holos> <83h8yhiuy3.fsf@gnu.org> <83wp7cgwie.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1499972633 5379 195.159.176.226 (13 Jul 2017 19:03:53 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Thu, 13 Jul 2017 19:03:53 +0000 (UTC) Cc: mvoteiza@udel.edu, emacs-devel@gnu.org To: Yuri Khan Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Jul 13 21:03:48 2017 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dVjOt-00018L-So for ged-emacs-devel@m.gmane.org; Thu, 13 Jul 2017 21:03:47 +0200 Original-Received: from localhost ([::1]:33588 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dVjOz-0003Ve-Cu for ged-emacs-devel@m.gmane.org; Thu, 13 Jul 2017 15:03:53 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59361) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dVjNi-0003To-B3 for emacs-devel@gnu.org; Thu, 13 Jul 2017 15:02:35 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dVjNd-0002N9-Vm for emacs-devel@gnu.org; Thu, 13 Jul 2017 15:02:34 -0400 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:44418) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dVjNd-0002N5-SU; Thu, 13 Jul 2017 15:02:29 -0400 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3682 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1dVjNc-0008KU-O1; Thu, 13 Jul 2017 15:02:29 -0400 In-reply-to: (message from Yuri Khan on Fri, 14 Jul 2017 01:07:21 +0700) 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:216599 Archived-At: > From: Yuri Khan > Date: Fri, 14 Jul 2017 01:07:21 +0700 > Cc: Mark Oteiza , Emacs developers > > On Thu, Jul 13, 2017 at 10:57 PM, Eli Zaretskii wrote: > > >> Maybe, but the name ‘fixed-pitch-serif’ suggests a particular > >> presentation (a serif font), while ‘fixed-pitch’ does not. > > > > AFAIU, fixed-pitch just means Sans Serif, so it is also a particular > > presentation in that sense. > > The name ‘fixed-pitch’ literally means only the fixedness of pitch and > says nothing about presence or absence of serifs. The name alone might suggest that, but the code tells a different story. I thought you looked in the code and saw there something I missed, thus my questions. > Anyway, with that history, it should not be used for line numbers, > which should strive to use the same typeface as default if at all > possible. I did strive, as "git log" will show. That's the best I could come up with, without complicating this stuff even more. IMO, it's not that bad, so "should not be used for line numbers" sounds a bit radical to me. > Having three different typefaces for the buffer text, line numbers, > and menu bar, is just offensive. You forgot tooltips and the font used for the caption bar. > > And fixed-pitch definitely doesn't yield the > > same font as the default face on my system. > > I would suggest that is a bug. It's not a bug, since the code was written to produce that effect. (I think similar issue happens in the NS build.)