From: Randy Taylor <dev@rjt.dev>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Evgeni Kolev <evgenysw@gmail.com>,
60407@debbugs.gnu.org, Yuan Fu <casouri@gmail.com>
Subject: bug#60407: [PATCH] Update go-ts-mode to use Imenu facility
Date: Sun, 01 Jan 2023 13:08:33 +0000 [thread overview]
Message-ID: <9d56GnQJmiljnB4ZyywBFQc5TUzr19_OEQaO8ujwM8_cftSULjDL5pKCM3z1jknmwndVbBsejsyvMK9ZzCchuuDLN5IBwDkHwYp4QMcWlH4=@rjt.dev> (raw)
In-Reply-To: <83y1qm39o3.fsf@gnu.org>
On Sunday, January 1st, 2023 at 04:07, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > From: Evgeni Kolev evgenysw@gmail.com
>
> > Date: Thu, 29 Dec 2022 18:05:49 +0200
> >
> > This patch updates go-ts-mode to use Imenu facility added in
> > https://git.savannah.gnu.org/cgit/emacs.git/commit/?h=emacs-29&id=b39dc7ab27a696a8607ab859aeff3c71509231f5
> >
> > The Imenu items are extended to support "Method", in addition to
> > "Function" and "Type".
> >
> > The current Imenu approach uses "type_spec" to identify "Type" which
> > acts as a catch-all for many Go constructs, for example struct and
> > interface definitions. This catch-all approach is not optimal because
> > structs and interfaces are put in the same "Type" bucket. In a
> > follow-up patch I'll try to change the approach and have separate
> > "Interface" and "Struct" types.
> >
> > The patch is below.
>
>
> Randy, Yuan, are you looking into this?
Sorry, been preoccupied recently. It's on my radar and I'll take a look and test it out later today.
next prev parent reply other threads:[~2023-01-01 13:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-29 16:05 bug#60407: [PATCH] Update go-ts-mode to use Imenu facility Evgeni Kolev
2023-01-01 9:07 ` Eli Zaretskii
2023-01-01 13:05 ` Evgeni Kolev
2023-01-01 17:08 ` Evgeni Kolev
2023-01-01 22:31 ` Randy Taylor
2023-01-03 9:01 ` Evgeni Kolev
2023-01-03 14:30 ` Randy Taylor
2023-01-05 7:24 ` Evgeni Kolev
2023-01-05 14:21 ` Randy Taylor
2023-01-01 13:08 ` Randy Taylor [this message]
2023-01-08 0:20 ` Yuan Fu
2023-01-08 8:10 ` Evgeni Kolev
2023-01-08 10:59 ` Eli Zaretskii
2023-01-09 0:35 ` Yuan Fu
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='9d56GnQJmiljnB4ZyywBFQc5TUzr19_OEQaO8ujwM8_cftSULjDL5pKCM3z1jknmwndVbBsejsyvMK9ZzCchuuDLN5IBwDkHwYp4QMcWlH4=@rjt.dev' \
--to=dev@rjt.dev \
--cc=60407@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=eliz@gnu.org \
--cc=evgenysw@gmail.com \
/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.