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:54:14 +0200 [thread overview]
Message-ID: <7eab6e94-cb8e-9ae1-d2cd-c0eb1b3bab43@gutov.dev> (raw)
In-Reply-To: <CALDnm53tZAM4Cw6M0nQEkq1j3ue1_A=fynh2UGDDntZERAwj4A@mail.gmail.com>
On 12/12/2023 01:48, João Távora wrote:
> On Mon, Dec 11, 2023 at 11:41 PM Dmitry Gutov<dmitry@gutov.dev> wrote:
>> On 12/12/2023 01:35, João Távora wrote:
>>> Or maybe say what the ruby-mode imenu backend
>>> does?
>> Juri just posted a long example of what ruby-mode does (and ruby-ts-mode
>> too) in his last message in this thread.
> OK, and doesn't it answer_your_ question? With Eglot
>
> Method > ModuleExample::ClassExample > instance_method
> Method > ClassExample > class_method
>
> If both methods were named "foo" no problem, right?
But this doesn't look right: if 'class_method' is in a class called
ModuleExample::ClassExample, shouldn't its entry look like
Method > ModuleExample::ClassExample > class_method
as well?
And then, if both 'instance_method' and 'class_method' actually are
called 'foo', then we'd have a problem.
This entry from his message also looks odd:
Module > > ModuleExample
next prev parent reply other threads:[~2023-12-11 23:54 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CH3PR84MB34240DD3259A46D28C406019C58BA@CH3PR84MB3424.NAMPRD84.PROD.OUTLOOK.COM>
[not found] ` <87plzgbalt.fsf@localhost>
[not found] ` <CH3PR84MB3424C475913C9D2A3F9EDD73C589A@CH3PR84MB3424.NAMPRD84.PROD.OUTLOOK.COM>
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
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 [this message]
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
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=7eab6e94-cb8e-9ae1-d2cd-c0eb1b3bab43@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 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).