From: Nick Helm <nick@tenpoint.co.nz>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
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: Mon, 18 Feb 2019 22:11:28 +0000 [thread overview]
Message-ID: <m2y36c927l.fsf@tenpoint.co.nz> (raw)
In-Reply-To: <87mumsss1k.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Mon, 18 Feb 2019 22:30:47 +0100")
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Nick Helm <nick@tenpoint.co.nz> writes:
>
>> But, the rest of the time, can't the indicator serve both purposes -
>> indicate a shrunken column and the presence of truncated cells - when it
>> is limited to places where text is hidden?
>
> I find it confusing -- you may actually miss the information that the
> current column is shrunk -- and not terribly useful. In particular, you
> can tweak the column width, and, more importantly, expand, and shrink
> again, the column quickly.
I guess we use org in quite different ways.
>> If I can't convince you to restore the default, would you consider
>> adding the previous behaviour as a configurable option?
>
> I'm not even convinced there's a real use-case for this behaviour that
> cannot be solved otherwise. Therefore, I don't think such a variable is
> needed.
That's a shame.
Could you tell me what functions govern this feature?
next prev parent reply other threads:[~2019-02-18 22:13 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
2019-02-18 8:11 ` Nick Helm
2019-02-18 21:30 ` Nicolas Goaziou
2019-02-18 22:11 ` Nick Helm [this message]
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=m2y36c927l.fsf@tenpoint.co.nz \
--to=nick@tenpoint.co.nz \
--cc=emacs-orgmode@gnu.org \
--cc=mail@nicolasgoaziou.fr \
/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).