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 16:44:03 +0000 Message-ID: <86o8wkgk6k.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> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:46376) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ide2r-00014M-1k for emacs-orgmode@gnu.org; Sat, 07 Dec 2019 12:39:06 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ide2p-0006PR-AB for emacs-orgmode@gnu.org; Sat, 07 Dec 2019 12:39:04 -0500 Received: from 195-159-176-226.customer.powertech.no ([195.159.176.226]:59256 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ide2p-0006OZ-3R for emacs-orgmode@gnu.org; Sat, 07 Dec 2019 12:39:03 -0500 Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1iddBj-000DFw-DA for emacs-orgmode@gnu.org; Sat, 07 Dec 2019 17:44:11 +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 Fri 06 Dec 2019, Nicolas Goaziou wrote: > Hello, > > Andy Moreton writes: > >> This is still a regression. >> >> The old behaviour allowed display of fixed width columns, even if that >> is wider than the content of cells in that column. This is useful for >> display of several related tables with aligned column dividers. >> >> How do I get the old behaviour back, rather than the new breakage ? > > I will try to ignore the sarcasm, or whatever you may call it, from your > answer. No sarcasm intended, merely a re-statement that this change is a regression of user visible behaviour. > AFAICT, you still can have cells wider than their contents, e.g., try > `C-c TAB` on the table below. > > | <30> | > | foo | That still does not match the old behaviour though, as the table still shows the `org-table-shrunk-column-indicator' overlay which is undesireable. Dynamic shrink/expand is a fine feature to add, but why was it done in a way that broke the documented existing behaviour ? AndyM