From: "João Távora" <joaotavora@gmail.com>
To: Yuan Fu <casouri@gmail.com>
Cc: eliz@gnu.org, 58431@debbugs.gnu.org
Subject: bug#58431: 29.0.50; [Eglot] Add "breadcrumb.el" feature based on imenu.el/project.el services
Date: Wed, 12 Oct 2022 09:30:01 +0100 [thread overview]
Message-ID: <87bkqhphpy.fsf@gmail.com> (raw)
In-Reply-To: <F0219975-55A7-423E-BD9F-3E1778F83854@gmail.com> (Yuan Fu's message of "Tue, 11 Oct 2022 23:22:48 -0700")
Yuan Fu <casouri@gmail.com> writes:
> Thanks for your explanation! I didn’t know which-func can just use
> imenu--index-alist. I already have support for imenu, just need to let
> which-func do its thing.
Yup.
> What you said for breakcumb.el makes total sense. It sounds pretty
> straightforward, just get file path from project.el and function path
> from imenu and put them together.
Yes, that's exactly it. It should be reasonably straightforward yes.
Maybe, to make a fancy breadcrumb, with icons like lsp-mode's we will
need some small augmentations to imenu--index-alist, but I don't see
that as a big difficulty.
> I can work on it later if no one
> come around and adopt it, I’ve got a lot of stuff on my plate already
> ;-)
Same here. Drop a line a line if start working on this, so we don't
duplicate each other's work.
João
next prev parent reply other threads:[~2022-10-12 8:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 9:17 bug#58431: 29.0.50; [Eglot] Add "breadcrumb.el" feature based on imenu.el/project.el services João Távora
2022-10-11 15:38 ` Yuan Fu
2022-10-11 23:50 ` João Távora
2022-10-12 6:22 ` Yuan Fu
2022-10-12 8:30 ` João Távora [this message]
2023-05-12 13:09 ` João Távora
2023-05-17 21:31 ` Yuan Fu
2023-04-08 19:47 ` Daniel Martín via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-18 18:10 ` bug#58431: 29.0.50; [Eglot] Add "breadcrumb.el" feature based, " Adam Porter
2023-04-18 18:26 ` João Távora
2023-04-20 4:27 ` Adam Porter
2023-04-20 9:22 ` João Távora
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=87bkqhphpy.fsf@gmail.com \
--to=joaotavora@gmail.com \
--cc=58431@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=eliz@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 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).