From: "João Távora" <joaotavora@gmail.com>
To: Damien Cassou <damien@cassou.me>
Cc: johnw@newartisans.com, 38378@debbugs.gnu.org,
clement.pitclaudel@live.com,
Stefan Monnier <monnier@iro.umontreal.ca>,
Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#38378: 26.3.50; [PATCH] Add the hierarchy library
Date: Mon, 9 Dec 2019 13:25:59 +0100 [thread overview]
Message-ID: <CALDnm512ZkKv-D_3WVTO9V5ntk-ohwWd7PfqJSc3mOZ8mG6qGg@mail.gmail.com> (raw)
In-Reply-To: <87pngx3d1c.fsf@cassou.me>
On Mon, Dec 9, 2019 at 1:21 PM Damien Cassou <damien@cassou.me> wrote:
>
> Dmitry Gutov <dgutov@yandex.ru> writes:
> > Eli said the core would benefit from it, but I wonder which existing
> > features exactly could use it now.
> >
> > If none, I think GNU ELPA is the better place for it. And as soon as
> > someone finds a specific use for it in the core, moving would be trivial.
FWIW, I agree with Dmitry here.
> Clément Pit-Claudel suggested "the tree displayed by profiler-report."
> in https://lists.gnu.org/archive/html/emacs-devel/2017-10/msg00675.html.
>
> Maybe proced's tree mode?
So why don't we add a comment to those libraries and say: "if
you're considering simplifying this code and adding some more features,
consider installing Damien Cassous's as a :core GNU ELPA package
in the core" .
Would this work for everyone?
Having it in ELPA is good for me if I ever want to upgrade it, then make SLY
use it. But the clincher would be that you implement mutable trees :-)
João
next prev parent reply other threads:[~2019-12-09 12:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 19:03 bug#38378: 26.3.50; [PATCH] Add the hierarchy library Damien Cassou
2019-12-09 7:31 ` Damien Cassou
2019-12-09 9:45 ` João Távora
2019-12-09 12:23 ` Damien Cassou
2019-12-09 12:27 ` João Távora
2019-12-13 19:56 ` Damien Cassou
2019-12-09 10:53 ` Dmitry Gutov
2019-12-09 12:21 ` Damien Cassou
2019-12-09 12:25 ` João Távora [this message]
2020-08-09 12:49 ` Lars Ingebrigtsen
2020-08-09 12:52 ` Lars Ingebrigtsen
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=CALDnm512ZkKv-D_3WVTO9V5ntk-ohwWd7PfqJSc3mOZ8mG6qGg@mail.gmail.com \
--to=joaotavora@gmail.com \
--cc=38378@debbugs.gnu.org \
--cc=clement.pitclaudel@live.com \
--cc=damien@cassou.me \
--cc=dgutov@yandex.ru \
--cc=johnw@newartisans.com \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.