From: Eli Zaretskii <eliz@gnu.org>
To: Evgeni Kolev <evgenysw@gmail.com>
Cc: dev@rjt.dev, casouri@gmail.com, 60407@debbugs.gnu.org
Subject: bug#60407: [PATCH] Update go-ts-mode to use Imenu facility
Date: Sun, 08 Jan 2023 12:59:14 +0200 [thread overview]
Message-ID: <83a62tqol9.fsf@gnu.org> (raw)
In-Reply-To: <CAMCrgaUG24ceXUECFSt99q-jbHMgOqtrgUVnyJPt5ZLLwdYFng@mail.gmail.com> (message from Evgeni Kolev on Sun, 8 Jan 2023 10:10:33 +0200)
> From: Evgeni Kolev <evgenysw@gmail.com>
> Date: Sun, 8 Jan 2023 10:10:33 +0200
> Cc: Randy Taylor <dev@rjt.dev>, Eli Zaretskii <eliz@gnu.org>, 60407@debbugs.gnu.org
>
> A side question - does it make sense to extend go-ts-mode with
> interactive functions?
>
> For example a function (go-ts-mode-docstring) which adds a docstring
> for the current type:
> with Go code:
> func sum(a, b int) int {...}
> the function would add a comment above the func:
> // sum
> func sum(a, b int) int {...}
>
> This is something I've implemented for myself, I'm wondering if it
> makes sense to contribute it to go-ts-mode.
It makes sense, but it will have to wait until Emacs 30. The release
branch is frozen, and no new features are accepted.
> Or should I first discuss this in the devel mail list? Or maybe send
> another patch and have the discussion there?
Either one would be good.
Thanks.
next prev parent reply other threads:[~2023-01-08 10:59 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
2023-01-08 0:20 ` Yuan Fu
2023-01-08 8:10 ` Evgeni Kolev
2023-01-08 10:59 ` Eli Zaretskii [this message]
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=83a62tqol9.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60407@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=dev@rjt.dev \
--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.