From: Adam Porter <adam@alphapapa.net>
To: Eli Zaretskii <eliz@gnu.org>, Ihor Radchenko <yantar92@posteo.net>
Cc: 69305@debbugs.gnu.org, juri@linkov.net
Subject: bug#69305: outline-minor-mode for tabulated-list-mode
Date: Sun, 25 Feb 2024 01:53:55 -0600 [thread overview]
Message-ID: <fbec6380-3ed4-43a7-bb21-231521f9b714@alphapapa.net> (raw)
In-Reply-To: <86o7c5y9x7.fsf@gnu.org>
By the way, with regard to grouping buffers specifically, this is what
my Bufler package does, again in an extensible, user-programmable way:
https://github.com/alphapapa/bufler.el
I wrote it after putting significant effort into using Ibuffer's
grouping features, which didn't meet my needs.
Bufler supports grouping buffers by many different attributes, such as
directory, filename, mode, project, parent-project, TRAMP status, etc.
And, significantly, it does such grouping dynamically at multiple
levels. For example, within a "~/src/emacs" directory, subgroups for
git projects within that directory can be created dynamically, providing
a grouping like:
+ Dir: ~/src/emacs
|-+ Project: ~/src/emacs/bufler.el
| |- *magit-status: bufler.el*
|-+ Project: ~/src/emacs/activities.el
|- README.org
If org-super-agenda was my exploration of the topic, Bufler served as
the prototype of a better API, which I then factored out into Taxy.
Eventually I'll rebase Bufler on top of Taxy.
next prev parent reply other threads:[~2024-02-25 7:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 17:34 bug#69305: outline-minor-mode for tabulated-list-mode Juri Linkov
2024-02-21 19:12 ` Eli Zaretskii
2024-02-22 7:44 ` Juri Linkov
2024-02-22 8:20 ` Eli Zaretskii
2024-02-22 17:30 ` Juri Linkov
2024-02-22 19:10 ` Eli Zaretskii
2024-02-23 7:09 ` Juri Linkov
2024-02-23 8:13 ` Eli Zaretskii
2024-02-24 17:43 ` Juri Linkov
2024-02-24 18:09 ` Eli Zaretskii
2024-02-24 18:13 ` Eli Zaretskii
2024-02-25 8:00 ` Adam Porter
2024-02-25 17:25 ` Juri Linkov
2024-02-25 19:17 ` Eli Zaretskii
2024-02-27 7:30 ` Juri Linkov
2024-02-27 8:31 ` Eli Zaretskii
2024-02-27 17:40 ` Juri Linkov
2024-02-27 18:44 ` Eli Zaretskii
2024-02-28 7:36 ` Juri Linkov
2024-02-28 12:16 ` Eli Zaretskii
2024-02-29 7:45 ` Juri Linkov
2024-02-29 16:33 ` Eli Zaretskii
2024-02-29 17:50 ` Juri Linkov
2024-03-03 6:53 ` Jean Louis
2024-03-03 7:52 ` Juri Linkov
2024-02-24 18:06 ` Ihor Radchenko
2024-02-24 18:16 ` Eli Zaretskii
2024-02-24 18:36 ` Ihor Radchenko
2024-02-24 18:49 ` Eli Zaretskii
2024-02-25 7:45 ` Adam Porter
2024-02-25 17:36 ` Juri Linkov
2024-02-26 3:31 ` Adam Porter
2024-03-06 17:37 ` Juri Linkov
2024-03-08 23:13 ` Adam Porter
2024-02-25 7:53 ` Adam Porter [this message]
2024-02-25 8:26 ` Eli Zaretskii
2024-02-25 17:20 ` Juri Linkov
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=fbec6380-3ed4-43a7-bb21-231521f9b714@alphapapa.net \
--to=adam@alphapapa.net \
--cc=69305@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--cc=yantar92@posteo.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).