From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: Gnus Summary buffer enhancement?
Date: Fri, 20 Nov 2020 10:50:29 -0800 [thread overview]
Message-ID: <87o8jr50cq.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <rietutknxoe.fsf@faulbaum.in-berlin.de>
Dieter Faulbaum <mail@faulbaum.in-berlin.de> writes:
> I think it would be nice if the summary buffer uses the
> tabulated-list-mode?
> Maybe the Group buffer too?
>
> Would the header line and sorting possibility be enhancements for that
> buffer(s)?
Without thinking about it very hard, this seems like a whole lot of work
without obvious benefit. The slow parts of summary buffer generation
include building the thread structure (if threading is used),
determining sort order, and calculating columns widths. All those things
would still have to be done under `tabulated-list-mode', so all we'd get
would be the surrounding "framework" code. That would be nice, but
probably not worth the work.
One significant improvement I'd like to see for the summary buffers is
"in-place" updates: inserting, re-ordering or re-drawing header lines
individually, without refreshing the entire buffer. I don't think
`tabulated-list-mode' would help here, either.
It might work for the group buffer, but probably not for topic mode,
where there are separate header lines, and groups can appear more than
once, under different topics.
It's worth thinking about, though...
Eric
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
prev parent reply other threads:[~2020-11-20 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-20 10:13 Dieter Faulbaum
2020-11-20 18:50 ` Eric Abrahamsen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87o8jr50cq.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=info-gnus-english@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.
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 NNTP newsgroup(s).