From: Kyle Meyer <kyle@kyleam.com>
To: Pankaj Jangid <p4j@j4d.net>, "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Bug: Org 9.3 table columnwidth directive not working [9.3 (release_9.3 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)]
Date: Thu, 05 Dec 2019 00:28:35 -0500 [thread overview]
Message-ID: <87eexjgx30.fsf@kyleam.com> (raw)
In-Reply-To: <0100016ed4392587-b1efb2eb-f2d2-49d2-b77c-572deb0fff17-000000@email.amazonses.com>
Pankaj Jangid <p4j@j4d.net> writes:
> C-c TAB is working but earlier the behaviour was to apply <width>
> directive by default on next electric formatting. Has the behaviour
> changed in 9.3?
9.2, I believe, more specifically 6d6a30d4c (org-table: Implement shrunk
columns, 2017-06-27). The relevant NEWS entry, added in 6e5598dc3
(Document new column display, 2017-08-19), is
*** =align= STARTUP value no longer narrow table columns
Columns narrowing (or shrinking) is now dynamic. See [[*Dynamically
narrow table columns]] for details. In particular, it is decoupled from
aligning.
If you need to automatically shrink columns upon opening an Org
document, use =shrink= value instead, or in addition to align:
#+BEGIN_EXAMPLE
,#+STARTUP: align shrink
#+END_EXAMPLE
Quickly digging, here are some related threads on the mailing list:
https://lists.gnu.org/archive/html/emacs-orgmode/2017-07/msg00214.html
https://lists.gnu.org/archive/html/emacs-orgmode/2017-09/msg00217.html
next prev parent reply other threads:[~2019-12-05 5:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 16:52 Bug: Org 9.3 table columnwidth directive not working [9.3 (release_9.3 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)] Pankaj Jangid
2019-12-04 17:10 ` Fraga, Eric
2019-12-05 4:02 ` Pankaj Jangid
2019-12-05 5:28 ` Kyle Meyer [this message]
2019-12-05 8:50 ` Pankaj Jangid
2019-12-06 13:28 ` Andy Moreton
2019-12-06 20:39 ` Nicolas Goaziou
2019-12-07 16:44 ` Andy Moreton
2019-12-07 18:16 ` Nicolas Goaziou
2019-12-07 21:48 ` Andy Moreton
2019-12-08 8:24 ` Nicolas Goaziou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87eexjgx30.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=p4j@j4d.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).