From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Helm Subject: Re: Bug: Org 9.2.1 table issues [9.2.1 (9.2.1-dist @ /Users/nick/.emacs.d/lisp/org-9.2.1/)] Date: Mon, 18 Feb 2019 22:11:28 +0000 Message-ID: References: <874l95qq9c.fsf@nicolasgoaziou.fr> <87ftsmti8p.fsf@nicolasgoaziou.fr> <87mumsss1k.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([209.51.188.92]:58589) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gvrAT-0005XG-5g for emacs-orgmode@gnu.org; Mon, 18 Feb 2019 17:13:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gvr8Q-0000yV-0L for emacs-orgmode@gnu.org; Mon, 18 Feb 2019 17:11:34 -0500 Received: from mail-eopbgr1370117.outbound.protection.outlook.com ([40.107.137.117]:14752 helo=AUS01-SY3-obe.outbound.protection.outlook.com) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gvr8P-0000xi-Ei for emacs-orgmode@gnu.org; Mon, 18 Feb 2019 17:11:33 -0500 In-Reply-To: <87mumsss1k.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Mon, 18 Feb 2019 22:30:47 +0100") Content-Language: en-US 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: Nicolas Goaziou Cc: "emacs-orgmode@gnu.org" Nicolas Goaziou writes: > Nick Helm writes: > >> But, the rest of the time, can't the indicator serve both purposes - >> indicate a shrunken column and the presence of truncated cells - when it >> is limited to places where text is hidden? > > I find it confusing -- you may actually miss the information that the > current column is shrunk -- and not terribly useful. In particular, you > can tweak the column width, and, more importantly, expand, and shrink > again, the column quickly. I guess we use org in quite different ways.=20 >> If I can't convince you to restore the default, would you consider >> adding the previous behaviour as a configurable option? > > I'm not even convinced there's a real use-case for this behaviour that > cannot be solved otherwise. Therefore, I don't think such a variable is > needed.=20 That's a shame. Could you tell me what functions govern this feature?=20