From: Damien Cassou <damien@cassou.me>
To: Dmitry Gutov <dgutov@yandex.ru>, 38378@debbugs.gnu.org
Cc: johnw@newartisans.com, clement.pitclaudel@live.com,
joaotavora@gmail.com, monnier@IRO.UMontreal.CA
Subject: bug#38378: 26.3.50; [PATCH] Add the hierarchy library
Date: Mon, 09 Dec 2019 13:21:19 +0100 [thread overview]
Message-ID: <87pngx3d1c.fsf@cassou.me> (raw)
In-Reply-To: <8ccb16d7-34b5-c399-4270-aa7ae84fd9ff@yandex.ru>
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.
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?
I stated my opinion about this matter in the past (see
https://lists.gnu.org/archive/html/emacs-devel/2017-10/msg00686.html):
Damien Cassou wrote:
> If you think Emacs would benefit from having hierarchy included,
> please do include it. My philosophy is more in the opposite direction
> (getting rid of as much as possible in the core to facilitate release
> and to let package maintainers use the tools they want)
To which Eli answered:
Eli Zaretskii wrote:
> As much as possible, but no more than that, I presume? Then the issue
> here is whether this capability should or shouldn't be in core, as
> other basics. I think it should.
I let you decide.
--
Damien Cassou
"Success is the ability to go from one failure to another without
losing enthusiasm." --Winston Churchill
next prev parent reply other threads:[~2019-12-09 12:21 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 [this message]
2019-12-09 12:25 ` João Távora
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
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=87pngx3d1c.fsf@cassou.me \
--to=damien@cassou.me \
--cc=38378@debbugs.gnu.org \
--cc=clement.pitclaudel@live.com \
--cc=dgutov@yandex.ru \
--cc=joaotavora@gmail.com \
--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 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).