From: Harald Kirsch <pifpafpuf@gmx.de>
To: emacs-devel@gnu.org
Subject: Re: eglot-cthier.el --- show call hierarchy with Eglot (formally called eglot-hierarchy)
Date: Wed, 11 Dec 2024 11:07:20 +0100 [thread overview]
Message-ID: <ebd895dc-89e6-4d0a-acb5-68180551e3da@gmx.de> (raw)
In-Reply-To: <m2ttbbsil6.fsf@gmail.com>
Hi Gerd.
On 10.12.24 15:44, Gerd Möllmann wrote:
> Harald Kirsch <pifpafpuf@gmx.de> writes:
>
>> This shows a call hierarchy as a foldable tree, unfolded on demand.
>>
>> Through nice feedback here, on codeberg and on @HaraldKi@nrw.social, it
>> got a significant update with bug fixes, enhancements and code improvements.
>>
>> I test this with eglipse-jdts (Java) and tsc (TypeScript).
>>
>> https://codeberg.org/harald/eglot-supplements#call-hierarchy
>>
>> Feedback welcome.
>
> Major improvement, thanks Harald!
>
> I have only one minor wish: could you bind TAB like RET? I think things
> like profiler-report do that, too.
Easy enough. I realize magit uses TAB too to unfold things.
https://codeberg.org/harald/eglot-supplements/issues/14
> Any plans for the other direction, i.e. functions called from another
> function?
Now we have incoming calls. There are also outgoing calls as well as
subtype and supertype hierarchies, all with a very similar API. I have
some code already for supertype. So ongoing. :-)
https://codeberg.org/harald/eglot-supplements/issues/13
Harald
next prev parent reply other threads:[~2024-12-11 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-10 12:29 eglot-cthier.el --- show call hierarchy with Eglot (formally called eglot-hierarchy) Harald Kirsch
2024-12-10 13:32 ` Gabriel Santos
2024-12-10 14:44 ` Gerd Möllmann
2024-12-11 10:07 ` Harald Kirsch [this message]
2024-12-11 11:01 ` Gerd Möllmann
2024-12-11 6:05 ` Filippo Argiolas
2024-12-11 10:36 ` Harald Kirsch
2024-12-11 12:14 ` Filippo Argiolas
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=ebd895dc-89e6-4d0a-acb5-68180551e3da@gmx.de \
--to=pifpafpuf@gmx.de \
--cc=emacs-devel@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.
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.