From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: 44068@debbugs.gnu.org
Subject: bug#44068: 28.0.50; Faulty uses of tabulated-list-format
Date: Mon, 19 Oct 2020 21:43:57 +0300 [thread overview]
Message-ID: <831rhuoy36.fsf@gnu.org> (raw)
In-Reply-To: <877drm13j3.fsf@gmx.net> (message from Stephen Berman on Mon, 19 Oct 2020 20:20:16 +0200)
> From: Stephen Berman <stephen.berman@gmx.net>
> Cc: 44068@debbugs.gnu.org
> Date: Mon, 19 Oct 2020 20:20:16 +0200
>
> > Instead of manually fine-tuning each column's width, wouldn't it be
> > better to use the string-trim capabilities that replace excess
> > characters with an ellipsis?
>
> I'm not sure I understand your suggestion. If you mean to truncate the
> column label in the header line when displaying the sort indicator,
> e.g. change "Status" to "Sta… ▼", I'm dubious it's worth the effort,
> since most of the problematic cases in the Emacs sources are with the
> final column, where there's always enough space, but due to the
> misleading description in tabulated-list-format's doc string, many modes
> have made it unnecessarily narrow, preventing the display of the sort
> indicator. So to avoid the final column being labelled e.g. either
> "File" or "Fi… ▼" instead of "File ▼", it is necessary to change the
> width manually anyway. In other words, the truncation proposal would be
> an addition to manual fine-tuning (for non-final columns), not a
> substitute for it. Or did you mean something else?
Yes, I meant it as an addition, which will make this issue much more
future proof. Documentation update is definitely fine (and should
probably go to emacs-27, not to master, right?), and adjusting the
column widths to eliminate the ellipsis is also okay. I just don't
want us to end with these two and nothing else.
next prev parent reply other threads:[~2020-10-19 18:43 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-18 20:00 bug#44068: 28.0.50; Faulty uses of tabulated-list-format Stephen Berman
2020-10-18 21:33 ` Drew Adams
2020-10-18 22:01 ` Stefan Kangas
2020-10-18 22:15 ` Drew Adams
2020-10-18 22:18 ` Stephen Berman
2020-10-18 22:01 ` Stefan Kangas
2020-10-18 22:17 ` Stephen Berman
2020-10-18 22:35 ` Stephen Berman
2020-10-18 23:13 ` Stefan Kangas
2020-10-19 9:04 ` Stephen Berman
2020-10-19 13:52 ` Eli Zaretskii
2020-10-19 18:20 ` Stephen Berman
2020-10-19 18:43 ` Eli Zaretskii [this message]
2020-10-19 19:12 ` Stephen Berman
2020-10-20 16:09 ` Stephen Berman
2020-10-29 16:58 ` Stefan Kangas
2020-10-29 22:48 ` Stephen Berman
2020-10-30 1:06 ` Stefan Kangas
2020-10-30 21:44 ` Stephen Berman
2020-10-30 23:51 ` Stefan Kangas
2020-11-01 23:07 ` Stephen Berman
2020-11-02 17:12 ` Eli Zaretskii
2020-11-02 22:37 ` Stephen Berman
2020-11-03 3:27 ` Eli Zaretskii
2020-11-03 23:12 ` Stephen Berman
2020-11-04 15:09 ` Eli Zaretskii
2020-11-04 22:55 ` Stephen Berman
2020-11-04 12:02 ` Stefan Kangas
2020-11-04 22:53 ` Stephen Berman
2020-11-12 16:38 ` Stefan Kangas
2020-11-12 22:51 ` Stephen Berman
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=831rhuoy36.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44068@debbugs.gnu.org \
--cc=stephen.berman@gmx.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.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).