From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [RFC] Shrink columns dynamically Date: Thu, 27 Jul 2017 13:47:50 +0200 Message-ID: <87379iw17d.fsf@nicolasgoaziou.fr> 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> <20170712191429.pfos63zjpmxxboda@eyeBook.local> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48833) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1dahGj-0004WM-PI for emacs-orgmode@gnu.org; Thu, 27 Jul 2017 07:47:54 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1dahGi-0006ZN-Un for emacs-orgmode@gnu.org; Thu, 27 Jul 2017 07:47:53 -0400 Received: from relay3-d.mail.gandi.net ([2001:4b98:c:538::195]:54153) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1dahGi-0006Y4-Ok for emacs-orgmode@gnu.org; Thu, 27 Jul 2017 07:47:52 -0400 Received: from saiph.selenimh (000043010000000000000469.ipv6.commingeshautdebit.fr [IPv6:2a03:a0a0:0:4301::469]) (Authenticated sender: mail@nicolasgoaziou.fr) by relay3-d.mail.gandi.net (Postfix) with ESMTPSA id 21586A80DF for ; Thu, 27 Jul 2017 13:47:50 +0200 (CEST) Received: from ngz by saiph.selenimh with local (Exim 4.89) (envelope-from ) id 1dahGg-00013f-K2 for emacs-orgmode@gnu.org; Thu, 27 Jul 2017 13:47:50 +0200 In-Reply-To: <20170712191429.pfos63zjpmxxboda@eyeBook.local> (Rick Frankel's message of "Wed, 12 Jul 2017 15:14:29 -0400") 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 Hello, Rick Frankel writes: > 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. It would be a fun optimization problem to solve, but I doubt it would be much useful (e.g., pathological cases getting in the way...). > I like a single cycling command. [...] > 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) For the sake of simplicity, I opted for two states cycling in the latest proof of concept. It means that columns with a width cookie cannot be narrowed to 1 character, but I assume it is an acceptable restriction since the width cookie is probably there for a reason. > 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. Fixed. Thank you. Regards, -- Nicolas Goaziou