From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rick Frankel Subject: Re: [RFC] Shrink columns dynamically Date: Wed, 12 Jul 2017 15:14:29 -0400 Message-ID: <20170712191429.pfos63zjpmxxboda@eyeBook.local> References: <874lujv26h.fsf@nicolasgoaziou.fr> <87o9srxtec.fsf@mat.ucm.es> <87r2xntd3k.fsf@nicolasgoaziou.fr> <87fue3xjsl.fsf@mat.ucm.es> <877ezftb39.fsf@nicolasgoaziou.fr> <87fue23i4l.fsf@nicolasgoaziou.fr> <87iniyrug0.fsf@yandex.com> <87vamy0xjd.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35264) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dVN6c-0003ER-47 for emacs-orgmode@gnu.org; Wed, 12 Jul 2017 15:15:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dVN6Y-00023y-4t for emacs-orgmode@gnu.org; Wed, 12 Jul 2017 15:15:26 -0400 Received: from mail.cybercode.nyc ([45.55.183.129]:49324) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dVN6X-0001uV-UO for emacs-orgmode@gnu.org; Wed, 12 Jul 2017 15:15:22 -0400 Received: from authenticated-user (mail.cybercode.nyc [45.55.183.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.cybercode.nyc (Postfix) with ESMTPSA id 367F41404DD for ; Wed, 12 Jul 2017 15:14:30 -0400 (EDT) Content-Disposition: inline In-Reply-To: <87vamy0xjd.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode@gnu.org So I haven't posted in a while, but i use table a lot, so here's my $0.02. Personally, my use of width cookies has been mostly for visual display of columns are very long and will wrap in an html or latex table export, but would force the display too wide. My ideal default would be to have a setting which would shrink tables a reasonable (fill-column?, window-width?) visual display, with perhaps a min-column-width option and trying to balance the width of each column base on its un-narrowed total width, perhaps trying to keep narrow columns as-is in the process. For me this would probably align cognitively with how much info is needed to grok the cell contents. As to your behavior questions: On Wed, Jul 12, 2017 at 12:17:26PM +0200, Nicolas Goaziou wrote: > - Do we need two commands, one for narrowing (to a given number of > characters) and one for shrinking (to one character only)? Or would > a command toggling between the three states be sufficient? I like a single cycling command. > - Is there some rule of thumb to narrow a column when no width cookie is > supplied or should we consider this kind of columns has only two > states, shrunk and expanded? So i think you are saying that a column w/ a width cookie would have three states and one without only two? I think this in some ways negates the appeal of separating narrowing from the cookies. Also, my suggested default narrowing approach above would probably remove the need for cookies in many if not most cases. > - Supposing we focus on a single, cycling, command, how should it behave > when called on multiple columns at a time? Since some columns may have > two states and other ones three, it may end up being confusing for the > user. Wouldn't a min-column-width setting to use when there is no cookie solve the the bi- vs tri-state problem (every column has three states) rick P.S. and (somewhat) off topic: The doc string for `org-ascii-table-use-ascii-art' is out of date. `ascii-art-to-unicode.el' is now in elpa and the url no longer works.