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: Wed, 14 Oct 2020 17:54:42 +0300 Message-ID: <83r1q0zwlp.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> <83zh4q195b.fsf@gnu.org> <87sgah1mjz.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="2639"; 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 Wed Oct 14 16:55:45 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 1kSiBt-0000an-2u for ged-emacs-devel@m.gmane-mx.org; Wed, 14 Oct 2020 16:55:45 +0200 Original-Received: from localhost ([::1]:33500 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kSiBs-0008Ry-39 for ged-emacs-devel@m.gmane-mx.org; Wed, 14 Oct 2020 10:55:44 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42144) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kSiAi-0006sG-PX for emacs-devel@gnu.org; Wed, 14 Oct 2020 10:54:32 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:58902) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kSiAi-0000KH-E0; Wed, 14 Oct 2020 10:54:32 -0400 Original-Received: from [176.228.60.248] (port=4228 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kSiAh-0006qC-E8; Wed, 14 Oct 2020 10:54:31 -0400 In-Reply-To: <87sgah1mjz.fsf@gnus.org> (message from Lars Ingebrigtsen on Wed, 14 Oct 2020 06:03:28 +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:257636 Archived-At: > From: Lars Ingebrigtsen > Cc: emacs-devel@gnu.org > Date: Wed, 14 Oct 2020 06:03:28 +0200 > > Eli Zaretskii writes: > > >> >> (setq mode-line-thing > >> >> `(:propertize > >> >> "some-string" > >> >> :min-width 15)) > > [...] > > > Then perhaps I didn't understand your suggestion: how would the above > > be different from what you originally had in mind about :min-width? > > When rendering the mode line, Emacs knows what pixel it started the > first glyph of each mode line element on, and it knows where it ends, so > it sounds conceptually sound to add a :min-width spec here (since it can > just insert some space of the required length at the end). Yes, this can be done. But we'd need fort to decide what is the semantics of this: (setq mode-line-thing `(:propertize "%12b" :min-width 10)) IOW, when the format and :min-width contradict, who "wins"? Or maybe we should re-purpose the WIDTH parameter of such formats to mean "min-width"?