From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 44078@debbugs.gnu.org
Subject: bug#44078: 26.3; `tabulated-list-mode': Use it in any mode and for part of a buffer
Date: Tue, 20 Oct 2020 13:35:12 +0200 [thread overview]
Message-ID: <87pn5dgmfj.fsf@gnus.org> (raw)
In-Reply-To: <bcb23108-8e7d-4157-8eaa-7a77ed66f4e1@default> (Drew Adams's message of "Mon, 19 Oct 2020 09:03:24 -0700 (PDT)")
Drew Adams <drew.adams@oracle.com> writes:
> But for `tabulated-list-mode' I think we need more than just to add a
> minor-mode version. We really need a way to confine its effect to a
> part of a buffer.
Whenever I've done some work on tabulated-list-mode, I've been kinda
frustrated by its design. You'd ideally just be able to have a
functional interface where you just call a function with all the data
(and some commands to apply to the data), and then everything would
work. But instead it's a strange mixture of functional, buffer-local
data and updating functions.
A side effect of this is that the table isn't an "object" you can do
operations on -- there can only be one table per buffer, and it wants to
control the entire buffer.
So I'd welcome a more functional rewrite of tabulated-list-mode that
would constrain all actions to the area of the buffer where the table
is, and leave the rest of the buffer alone. And stash the table data in
the table instead of using the buffer-local variables.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-10-20 11:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 16:03 bug#44078: 26.3; `tabulated-list-mode': Use it in any mode and for part of a buffer Drew Adams
2020-10-20 11:35 ` Lars Ingebrigtsen [this message]
2020-10-20 16:20 ` Drew Adams
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=87pn5dgmfj.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=44078@debbugs.gnu.org \
--cc=drew.adams@oracle.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).