From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Is a `max-width' spec feasible? Date: Fri, 26 Nov 2021 12:07:54 -0500 Message-ID: References: <87pmqmsx36.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3238"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Nov 26 18:15:23 2021 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 1mqeok-0000dR-QQ for ged-emacs-devel@m.gmane-mx.org; Fri, 26 Nov 2021 18:15:23 +0100 Original-Received: from localhost ([::1]:38854 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mqeoj-0007NS-6y for ged-emacs-devel@m.gmane-mx.org; Fri, 26 Nov 2021 12:15:21 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:44184) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mqehj-0006ib-Ei for emacs-devel@gnu.org; Fri, 26 Nov 2021 12:08:07 -0500 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:40950) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mqehb-00083W-4Y for emacs-devel@gnu.org; Fri, 26 Nov 2021 12:08:01 -0500 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id EDE48806A7; Fri, 26 Nov 2021 12:07:56 -0500 (EST) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 4C8C18005D; Fri, 26 Nov 2021 12:07:55 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1637946475; bh=nESBg5jUZwLbacmEghUtI8RqqXEszNv10uCRjPTpGrY=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=mAipGYM9ETLTG/1lOtiF14wpAFEEPg4yZ9+VmVw05IO5cGsqMzSY6fbii/I1znSen 9xnij/UzCby1qN+qmBbYhCKVGqQo1EPx+ef/1xStSJq3wJXmwXoUtu3x1xJqcpeojv dMMcjhHlgbc1nH/IaP9PlpV29hE06QHLOcKBbbVIEnfLWSDxnVPbA/7PeOJvGZY86/ ojzDhRueuTarnAzFyctGVyXnZcvrOziPnwnEdy3Knr44CIobjc66bNXEwmj0eiaCsq U33w0m86qJmZTG2HPDNq5yWYeXqw5pAoyTVLfMAf4o8WDJOjh5UrEo9iJ6IASCamxN xPFIk/IH+hTaQ== Original-Received: from ceviche (modemcable124.78-161-184.mc.videotron.ca [184.161.78.124]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 277A21207BE; Fri, 26 Nov 2021 12:07:55 -0500 (EST) In-Reply-To: <87pmqmsx36.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 26 Nov 2021 17:25:33 +0100") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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:280265 Archived-At: > I haven't looked at this at all, so I'm just throwing this out there so > I don't forget (before going out): Would a `max-width' display spec be > feasible? I'm not the right person to answer. But I'd welcome this functionality, indeed. > That is, it's like `min-width', but if we've reached an it->current_x > that's wider than the spec, then we throw out all glyphs we've already > prepared, back to the desired width? Side note: `truncate-string-to-width` doesn't just throw away the excess but also inserts an ellipsis to announce the truncation, so if we add such a `max-width` it'd be desirable to make it display an ellipsis as well when truncating text. Stefan