emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Andy Moreton <andrewjmoreton@gmail.com>
Cc: 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: Sat, 07 Dec 2019 19:16:10 +0100	[thread overview]
Message-ID: <87d0d0uhlh.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <86o8wkgk6k.fsf@gmail.com> (Andy Moreton's message of "Sat, 07 Dec 2019 16:44:03 +0000")

Hello,

Andy Moreton <andrewjmoreton@gmail.com> 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?

> 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).

Feel free to suggest, and possibly implement, if users agree, a better
way. Or, please point where the documented behaviour does not match the
current state.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2019-12-07 18:16 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
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 [this message]
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=87d0d0uhlh.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=andrewjmoreton@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).