From: Julius Dittmar <Julius.Dittmar@gmx.de>
To: emacs-orgmode@gnu.org
Subject: Re: Feature request: shrink according to alignment (was Re: Org table columns without width cookies get shrunk on TAB)
Date: Mon, 19 Feb 2018 12:29:30 +0100 [thread overview]
Message-ID: <97d48f48-a6b4-eaf6-5f31-8e38525b25a6@gmx.de> (raw)
In-Reply-To: <87bmgll2rh.fsf@nicolasgoaziou.fr>
Am 19.02.2018 um 10:58 schrieb Nicolas Goaziou:
> Julius Dittmar <Julius.Dittmar@gmx.de> writes:
>> I think what the OP really would like is something like this: remove
>> leading whitespace until everything can be displayed or no more leading
>> whitespace remains, then truncate at the end if necessary. That way as
>> much meaningful contents as possible is displayed. At least that's what
>> I would wish in this situation.
>
> I understand the idea, but the implementation seems tricky. It means Org
> may sometimes have to hide characters on both sides of a field. and
> sometimes not. It doesn't sound visually appealing.
>
> I may be wide off the mark, tho. Do you have some specifications in
> mind, or at least some examples?
Up to the moment I read the original post I wasn't even aware any table
cell width restricting syntax exists, so I don't have any full-fledged
examples. Not even half-working ones.
What I think this was about: Assume, the following table is set up for
right-aligned output (that's one of the things I don't know how to do,
but that's fine with me):
| a very long entry which enforces a long table cell |
| a moderately long entry |
| a short entry |
Assume further that this table is to be displayed showing only 19
characters. As I understand the original post, the outcome at the moment
would be something like :
| a very long entr... |
| ... |
| ... |
What I would prefer is:
| a very long entr... |
| a moderately lon... |
| a short entry |
This does not really mean cutting on both ends, at least not more than
org already does. Org already does add or subtract leading or trailing
whitespace as needed. The change I'd love would spell something like
"first remove all whitespace, then cut (at the end) to length if needed,
and then add whitespace to archieve the defined alignment".
Regards,
Julius
next prev parent reply other threads:[~2018-02-19 11:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-14 15:58 Org table columns without width cookies get shrunk on TAB Kaushal Modi
2018-02-14 17:50 ` Nicolas Goaziou
2018-02-14 17:54 ` Kaushal Modi
2018-02-14 19:19 ` Nicolas Goaziou
2018-02-15 9:25 ` Eric S Fraga
2018-02-15 12:05 ` Kaushal Modi
2018-02-15 12:41 ` Eric S Fraga
2018-02-14 18:58 ` Kaushal Modi
2018-02-15 9:32 ` Feature request: shrink according to alignment (was Re: Org table columns without width cookies get shrunk on TAB) Eric S Fraga
2018-02-15 13:44 ` Nicolas Goaziou
2018-02-15 14:04 ` Julius Dittmar
2018-02-19 9:58 ` Nicolas Goaziou
2018-02-19 11:29 ` Julius Dittmar [this message]
2018-02-20 15:16 ` Eric S Fraga
2018-02-21 11:45 ` Nicolas Goaziou
2018-02-21 12:11 ` Julius Dittmar
2018-02-15 16:01 ` Eric S Fraga
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=97d48f48-a6b4-eaf6-5f31-8e38525b25a6@gmx.de \
--to=julius.dittmar@gmx.de \
--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).