From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Paul Eggert Newsgroups: gmane.emacs.devel Subject: Re: Variable-width font indentation Date: Fri, 9 Mar 2018 09:52:28 -0800 Organization: UCLA Computer Science Department Message-ID: References: <87inaiss6l.fsf@web.de> <6FCF6ACA-4F29-4B6B-BE9D-D7130C6E9495@gnu.org> <87fu5moe4c.fsf@web.de> <877eqyocro.fsf@web.de> <83zi3uz4nb.fsf@gnu.org> <0b1dd3fa-e0b0-ed20-a256-dd92d1c1826f@dancol.org> <8bc3c4c7-dfc7-987a-95e7-bd309e2326c6@cs.ucla.edu> <03118DC0-39DA-4AB5-980E-A33809B9A5EE@raeburn.org> <83vaeas8uz.fsf@gnu.org> <83lgf6s3aa.fsf@gnu.org> <838tb5rxoe.fsf@gnu.org> <83lgf5q73p.fsf@gnu.org> <4742f0ae-86b5-48f9-4601-4dbba9e6380d@gmail.com> <83bmfzreaq.fsf@gnu.org> <83lgf3przh.fsf@gnu.org> <42d0c18b-8d14-bfe2-8f09-112787e8b0b4@gmail.com> <83zi3io9tr.fsf@gnu.org> <859ec725-acc3-22e4-ca26-28108c3e5e26@gmail.com> <83sh9ao086.fsf@gnu.org> <83muzhodkx.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1520620121 24801 195.159.176.226 (9 Mar 2018 18:28:41 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 9 Mar 2018 18:28:41 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 Cc: emacs-devel@gnu.org To: Eli Zaretskii , =?UTF-8?Q?Cl=c3=a9ment_Pit-Claudel?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 09 19:28:37 2018 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 1euMku-0006Jh-JW for ged-emacs-devel@m.gmane.org; Fri, 09 Mar 2018 19:28:36 +0100 Original-Received: from localhost ([::1]:47300 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1euMmx-0004Fy-Fu for ged-emacs-devel@m.gmane.org; Fri, 09 Mar 2018 13:30:43 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38650) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1euMC4-0005qf-B1 for emacs-devel@gnu.org; Fri, 09 Mar 2018 12:52:37 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1euMC3-0002eo-Fy for emacs-devel@gnu.org; Fri, 09 Mar 2018 12:52:36 -0500 Original-Received: from zimbra.cs.ucla.edu ([131.179.128.68]:33284) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1euMBz-0002d5-Ll; Fri, 09 Mar 2018 12:52:31 -0500 Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id DD0BB161626; Fri, 9 Mar 2018 09:52:29 -0800 (PST) Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 4D9SXJEwfoyJ; Fri, 9 Mar 2018 09:52:29 -0800 (PST) Original-Received: from localhost (localhost [127.0.0.1]) by zimbra.cs.ucla.edu (Postfix) with ESMTP id 318AE16168D; Fri, 9 Mar 2018 09:52:29 -0800 (PST) X-Virus-Scanned: amavisd-new at zimbra.cs.ucla.edu Original-Received: from zimbra.cs.ucla.edu ([127.0.0.1]) by localhost (zimbra.cs.ucla.edu [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id iFydBhw7Sl79; Fri, 9 Mar 2018 09:52:29 -0800 (PST) Original-Received: from Penguin.CS.UCLA.EDU (Penguin.CS.UCLA.EDU [131.179.64.200]) by zimbra.cs.ucla.edu (Postfix) with ESMTPSA id 17D1B161626; Fri, 9 Mar 2018 09:52:29 -0800 (PST) In-Reply-To: <83muzhodkx.fsf@gnu.org> Content-Language: en-US X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [fuzzy] X-Received-From: 131.179.128.68 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:223553 Archived-At: On 03/09/2018 12:30 AM, Eli Zaretskii wrote: > I don't think that approach is appropriate for > code indentation, because leading whitespace in code blocks_must_ > always align, IMO. I don't quite follow this objection, since the prototype does align leading whitespace in code blocks. That is, in any particular block of code consisting of lines prefaced by equivalent white space, the approach displays the block with equally-indented lines, so the leading whitespace does align. If the objection is that different blocks of code are indented differently (e.g., an if-part might be indented slightly differently from the corresponding then-part), then I agree that might irritate some users. However, the irritation is quite small to me, and I imagine it wouldn't bother other users much either, in the sense that they'll be willing to put up with this minor irritation in order to get the benefits that the algorithm has elsewhere. So it still sounds like a reasonable thing to support, if a user wants to use it. Of course other display algorithms are possible, but I haven't seen any other improvement proposed for variable-pitch fonts that is nearly as simple and easy to understand. Simplicity is a virtue here.