From: Dmitry Gutov <dmitry@gutov.dev>
To: "João Távora" <joaotavora@gmail.com>
Cc: Juri Linkov <juri@linkov.net>,
Ihor Radchenko <yantar92@posteo.net>,
Eli Zaretskii <eliz@gnu.org>,
Morgan.J.Smith@outlook.com, emacs-orgmode@gnu.org,
58131@debbugs.gnu.org, emacs-devel@gnu.org
Subject: Re: [FR] Allow flattened imenu index
Date: Tue, 12 Dec 2023 01:23:13 +0200 [thread overview]
Message-ID: <303c567e-7f0d-1fac-1ab4-0099bd98d8dd@gutov.dev> (raw)
In-Reply-To: <CALDnm51HqN5Dc8o1qe_VZ18uAUVqRfSKqBTsYyEo938xzAbvDQ@mail.gmail.com>
On 12/12/2023 01:10, João Távora wrote:
> On Mon, Dec 11, 2023 at 7:24 PM Dmitry Gutov<dmitry@gutov.dev> wrote:
>> It's no invention, it's docstring syntax for reference to a method.
> In Ruby right?
Yes, in RDoc. Or Javadoc, for that matter. Probably some other languages
as well.
>> But if the LS will produce distinct strings, good.
> All imenu backends, at least all the ones I've seen, produce
> trees, not strings.
There are exceptions, like the previously mentioned one.
> If you collect all the paths from the root to
> all the nodes into lists and make strings thereof, the resulting
> set will always be a distinct strings. So I don't understand the
> problem you were surfacing: any particular imenu backend in mind?
Do you have an example of such tree produced by Eglot when a class
contains an instance and a singleton method with the same name?
next prev parent reply other threads:[~2023-12-11 23:23 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 20:52 [PATCH] Add new option 'org-imenu-flatten' Morgan Smith
2023-12-08 22:19 ` Ihor Radchenko
2023-12-09 1:46 ` Morgan Smith
2023-12-09 2:01 ` William Denton
2023-12-09 10:57 ` [FR] Allow flattened imenu index (was: [PATCH] Add new option 'org-imenu-flatten') Ihor Radchenko
2023-12-09 11:28 ` Eli Zaretskii
2023-12-09 11:39 ` Ihor Radchenko
2023-12-09 17:37 ` [FR] Allow flattened imenu index Juri Linkov
2023-12-11 11:51 ` João Távora
2023-12-11 17:20 ` Juri Linkov
2023-12-11 17:40 ` João Távora
2023-12-11 17:43 ` Dmitry Gutov
2023-12-11 18:00 ` João Távora
2023-12-11 19:24 ` Dmitry Gutov
2023-12-11 23:10 ` João Távora
2023-12-11 23:23 ` Dmitry Gutov [this message]
2023-12-11 23:35 ` João Távora
2023-12-11 23:41 ` Dmitry Gutov
2023-12-11 23:48 ` João Távora
2023-12-11 23:54 ` Dmitry Gutov
2023-12-11 23:57 ` João Távora
2023-12-11 19:30 ` Ihor Radchenko
2023-12-11 23:07 ` João Távora
2023-12-14 23:11 ` Spencer Baugh
2023-12-15 12:13 ` Dmitry Gutov
2024-05-11 9:41 ` [PATCH] Add new option 'org-imenu-flatten' Ihor Radchenko
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=303c567e-7f0d-1fac-1ab4-0099bd98d8dd@gutov.dev \
--to=dmitry@gutov.dev \
--cc=58131@debbugs.gnu.org \
--cc=Morgan.J.Smith@outlook.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=joaotavora@gmail.com \
--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 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.