From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andy Moreton Subject: Re: Bug: Org 9.3 table columnwidth directive not working [9.3 (release_9.3 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)] Date: Sat, 07 Dec 2019 21:48:53 +0000 Message-ID: <86wob7dcxm.fsf@gmail.com> References: <0100016ed1d37aac-88e8671f-bb77-434f-a756-35131ada48db-000000@email.amazonses.com> <87lfrsc8zj.fsf@ucl.ac.uk> <0100016ed4392587-b1efb2eb-f2d2-49d2-b77c-572deb0fff17-000000@email.amazonses.com> <87eexjgx30.fsf@kyleam.com> <87k179w5n3.fsf@nicolasgoaziou.fr> <86o8wkgk6k.fsf@gmail.com> <87d0d0uhlh.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:33412) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1idhwn-0001le-Aj for emacs-orgmode@gnu.org; Sat, 07 Dec 2019 16:49:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1idhwm-0003Cn-5S for emacs-orgmode@gnu.org; Sat, 07 Dec 2019 16:49:05 -0500 Received: from 195-159-176-226.customer.powertech.no ([195.159.176.226]:47604 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1idhwl-0002zL-Qh for emacs-orgmode@gnu.org; Sat, 07 Dec 2019 16:49:04 -0500 Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1idhwj-000vH7-LB for emacs-orgmode@gnu.org; Sat, 07 Dec 2019 22:49:01 +0100 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 On Sat 07 Dec 2019, Nicolas Goaziou wrote: > Hello, > > Andy Moreton writes: > >> That still does not match the old behaviour though, as the table still >> shows the `org-table-shrunk-column-indicator' overlay which is >> undesireable. > > Why is it undesirable? It also always shows the shrink/expend overlay, even if that is not desired. I find it visually intrusive, and the extra character introduces a new misalignment. >> Dynamic shrink/expand is a fine feature to add, but why was it done in a >> way that broke the documented existing behaviour ? > > I think the current state is better. However, I initially explained the > motivation behind this change (see links in this thread). While everyone has their own preferences, developers should not impose their preferences on users, who may decide to make different choices. The dynamic shrink feature added a new capability that many will find useful, but it also removed the ability to do things the older and simpler way. It should have been added as an option, so either static or dynamic behaviour can be selected by the user. AndyM