From: Eli Zaretskii <eliz@gnu.org>
To: shingo.fg8@gmail.com, stefankangas@gmail.com
Cc: 53133@debbugs.gnu.org
Subject: bug#53133: 28.0.90; tabulated-list-sort doesn't work as expected
Date: Sun, 09 Jan 2022 13:30:28 +0200 [thread overview]
Message-ID: <83zgo516zv.fsf@gnu.org> (raw)
In-Reply-To: <8335lx2npc.fsf@gnu.org> (message from Eli Zaretskii on Sun, 09 Jan 2022 12:44:15 +0200)
> Date: Sun, 09 Jan 2022 12:44:15 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: 53133@debbugs.gnu.org
>
> > --- tabulated-list.el.org 2022-01-06 22:32:13.936852142 +0900
> > +++ tabulated-list.el 2022-01-07 15:15:42.000000000 +0900
> > @@ -574,7 +581,8 @@
> > (when not-last-col
> > (when (> pad-right 0) (insert (make-string pad-right ?\s)))
> > (insert (propertize
> > - (make-string (- width (min width label-width)) ?\s)
> > + ;; We need at least one space to align correctly.
> > + (make-string (- width (min 1 width label-width)) ?\s)
> > 'display `(space :align-to ,next-x))))
> > (put-text-property opoint (point) 'tabulated-list-column-name name)
> > next-x)))
>
> You are right.
>
> Stefan, I reverted that change and I'm reopening bug#48639. This
> problem is a much more serious regression than what happens sometimes
> when text-size is scaled. We will need to find another fix for that
> bug, most probably in one of the hooks used by tabulated-list.el, by
> adding the display property only when actually needed.
To help debugging the original problem: the 'display' property that
was always present caused move-to-column in tabulated-list-print to
stop at the wrong position, where the tabulated-list-column-name
property had the wrong value. So either the 'display' property should
be used only when actually needed, or the tabulated-list-column-name
property should be also put on the text covered by the 'display'
property.
prev parent reply other threads:[~2022-01-09 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 2:03 bug#53133: 28.0.90; tabulated-list-sort doesn't work as expected Shingo Tanaka
2022-01-09 10:44 ` Eli Zaretskii
2022-01-09 11:30 ` Eli Zaretskii [this message]
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=83zgo516zv.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=53133@debbugs.gnu.org \
--cc=shingo.fg8@gmail.com \
--cc=stefankangas@gmail.com \
/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).