From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Columns and proportional fonts (was: bug#19872: 24.4; UTF8 characters of unusual width (Gnus markers)) Date: Thu, 19 Feb 2015 11:12:36 -0500 Message-ID: References: <86bnkvilxl.fsf@example.com> <86r3tqchqt.fsf@example.com> <83zj8dua5s.fsf@gnu.org> <87oaotyxwn.fsf@building.gnus.org> <83fva47dak.fsf@gnu.org> <878ufwcamp.fsf@building.gnus.org> <83k2zf6g08.fsf@gnu.org> <87r3tmjvr2.fsf@building.gnus.org> <83lhju4dmw.fsf@gnu.org> <831tlm3snc.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1424362413 14143 80.91.229.3 (19 Feb 2015 16:13:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 19 Feb 2015 16:13:33 +0000 (UTC) Cc: sva-news@mygooglest.com, larsi@gnus.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Feb 19 17:13:24 2015 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 1YOTj7-0001Gj-7t for ged-emacs-devel@m.gmane.org; Thu, 19 Feb 2015 17:13:21 +0100 Original-Received: from localhost ([::1]:56948 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YOTj5-0004co-DE for ged-emacs-devel@m.gmane.org; Thu, 19 Feb 2015 11:13:19 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52499) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YOTir-0004cj-Bo for emacs-devel@gnu.org; Thu, 19 Feb 2015 11:13:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YOTiq-0008UQ-G4 for emacs-devel@gnu.org; Thu, 19 Feb 2015 11:13:05 -0500 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:50403) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YOTim-0008Sp-0F; Thu, 19 Feb 2015 11:13:00 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AlgJAPOG1lTO+LI//2dsb2JhbABVBoMGg1/GOAQCAoENRAEBAQEBAXyEDQEEAVYjBQs/BwsUGA0kiDgIziMBAQEBBgEBAQEejzVDB4QqBYonn0uBRSKCMoFaIIJzAQEB X-IPAS-Result: AlgJAPOG1lTO+LI//2dsb2JhbABVBoMGg1/GOAQCAoENRAEBAQEBAXyEDQEEAVYjBQs/BwsUGA0kiDgIziMBAQEBBgEBAQEejzVDB4QqBYonn0uBRSKCMoFaIIJzAQEB X-IronPort-AV: E=Sophos;i="5.09,536,1418101200"; d="scan'208";a="110923669" Original-Received: from 206-248-178-63.dsl.teksavvy.com (HELO pastel.home) ([206.248.178.63]) by ironport2-out.teksavvy.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 19 Feb 2015 11:12:58 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id B76E91760; Thu, 19 Feb 2015 11:12:36 -0500 (EST) In-Reply-To: <831tlm3snc.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 19 Feb 2015 16:03:35 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:183299 Archived-At: > I agree in general, but cannot see why this particular case couldn't > be resolved reasonably well, e.g. by adding one more column "just in > case", before the :align-to property. In mpc.el I list the current songs with various of their info (duration, title, artist, ...) in columns, so I have the same problem there. I use truncate-string-to-width and do keep one extra column, but it's not always sufficient to avoid misalignment when the proportional font has some "very wide" chars. Also, I suffer from the reverse problem, that for columns where the text contains lots of narrow chars, truncate-string-to-width ends up being pessimistic, which is less harmful but wastes valuable screen estate and looks weird. My understanding of the redisplay engine makes me believe that a `:truncate-at' display property (and/or a combined :truncate-at-or-align-to) should be doable with good efficiency without too much extra gymnastics. And no, sorry, I'm not volunteering to implement it. Stefan