From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: How to make Emacs popular again: Use monospaced fonts less Date: Tue, 13 Oct 2020 17:40:48 +0300 Message-ID: <83zh4q195b.fsf@gnu.org> References: <835z7vjrg3.fsf@gnu.org> <83tuvegkmo.fsf@gnu.org> <83v9ftf6n9.fsf@gnu.org> <835z7qfp6h.fsf@gnu.org> <87ft6lgw5y.fsf_-_@gnus.org> <1F8F3522-1E6C-40A3-B61A-B9B84FC0AD18@gnu.org> <87blh9gthg.fsf@gnus.org> <87tuv1f2y9.fsf@gnus.org> <87o8l9f1dl.fsf@gnus.org> <83lfgc50gb.fsf@gnu.org> <875z7gflpl.fsf@gnus.org> <83imbf2xux.fsf@gnu.org> <87lfgbarkk.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="36438"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 13 16:43:03 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kSLW3-0009QD-3i for ged-emacs-devel@m.gmane-mx.org; Tue, 13 Oct 2020 16:43:03 +0200 Original-Received: from localhost ([::1]:56228 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kSLW2-0002LM-4S for ged-emacs-devel@m.gmane-mx.org; Tue, 13 Oct 2020 10:43:02 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:39918) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kSLTk-000084-JR for emacs-devel@gnu.org; Tue, 13 Oct 2020 10:40:41 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:36503) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kSLTk-00036l-9Y; Tue, 13 Oct 2020 10:40:40 -0400 Original-Received: from [176.228.60.248] (port=2291 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kSLTj-0003m6-Fd; Tue, 13 Oct 2020 10:40:40 -0400 In-Reply-To: <87lfgbarkk.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue, 13 Oct 2020 02:38:03 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:257538 Archived-At: > From: Lars Ingebrigtsen > Cc: emacs-devel@gnu.org > Date: Tue, 13 Oct 2020 02:38:03 +0200 > > >> (setq mode-line-thing > >> `(:propertize > >> "some-string" > >> :min-width 15)) > >> > >> which could have well-defined semantics, like "this element should have > >> the width of at least 15 typical characters", and be pretty easy to use? > > > > This stuff is basically unworkable without having a window in whose > > context the string will be shown. That's because we need metrics of > > each character glyph, and that presumes fonts, and that presumes faces > > and other stuff. > > > > This is why we use 'display' property: when the text is displayed, we > > have this data by definition. But not when we just have a string. > > I'm not sure I understand you. The mode line elements are only used > when we display them, so we know all that stuff, and can apply some > padding after the element if we have a :min-width thing here. Then perhaps I didn't understand your suggestion: how would the above be different from what you originally had in mind about :min-width?