From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Nick Helm <nick@tenpoint.co.nz>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
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: Sun, 17 Feb 2019 18:52:38 +0100 [thread overview]
Message-ID: <87ftsmti8p.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m2mumwdsp8.fsf@tenpoint.co.nz> (Nick Helm's message of "Sat, 16 Feb 2019 08:48:53 +0000")
Hello,
Nick Helm <nick@tenpoint.co.nz> writes:
> If that's the case, it's a significant loss of functionality. This would
> mean, for instance, that it's no longer possible to format financial
> data with a uniform column width.
"significant" may be relative. The feature has been available on master
for months, and this went unnoticed.
Anyway, I changed the algorithm, so shrinking should now obey to
alignment. Thank you for the feedback.
> Let me try to illustrate with another example. If you shrink this table
> with C-c TAB:
>
> | <5> |
> | one two |
> | one |
>
> you get the following:
>
> | <5> …|
> | one …|
> | one …|
>
> This is misleading - cell 3 contains no additional content yet the
> indicator says it does. It's also ambiguous - it's impossible to
> determine whether cell 2 or 3 contains the longer field.
>
> Compare with this, where such information is clearly conveyed:
>
> | <5> |
> | one …|
> | one |
This is not misleading. The "…" characters means the /column/ as a whole
is shrunk, not that an individual field is. Luckily, you can easily use,
for example, `C-TAB` for the rare case the situation requires
disambiguation.
> Has this been removed from 9.2 as well?
Yes, it has.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2019-02-17 17:52 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 0:29 Bug: Org 9.2.1 table issues [9.2.1 (9.2.1-dist @ /Users/nick/.emacs.d/lisp/org-9.2.1/)] Nick Helm
2019-02-15 10:50 ` Nicolas Goaziou
2019-02-16 8:48 ` Nick Helm
2019-02-17 17:52 ` Nicolas Goaziou [this message]
2019-02-18 8:11 ` Nick Helm
2019-02-18 21:30 ` Nicolas Goaziou
2019-02-18 22:11 ` Nick Helm
2019-02-18 22:44 ` Nicolas Goaziou
2019-02-19 3:16 ` Nick Helm
2019-02-19 10:10 ` Eric S Fraga
2019-02-19 11:46 ` Nick Helm
2019-02-21 20:42 ` Nick Helm
2019-02-26 10:10 ` Eric S Fraga
2019-02-19 12:17 ` Nick Helm
2019-02-19 16:07 ` 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=87ftsmti8p.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=nick@tenpoint.co.nz \
/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).