From: "João Távora" <joaotavora@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 50816@debbugs.gnu.org, Augusto Stoffel <arstoffel@gmail.com>
Subject: bug#50816: 28.0.50; [eglot] Nonstandard SymbolKind values for imenu
Date: Fri, 2 Sep 2022 12:06:29 +0100 [thread overview]
Message-ID: <CALDnm509D6inOLpLpXoTQ5fP5N_-+M=X57i1h83t+GoHNpru_w@mail.gmail.com> (raw)
In-Reply-To: <877d2mxd30.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 1170 bytes --]
From reading the original description, I do think this is more about LSP
than Eglot.
I haven't given much thought into it, but I don't think Eglot can do
anything
reasonable outside the standard here. And even if it could, not sure if it
should.
I'd venture to say that this should be brought up with Microsoft's
specification
instead.
João
On Fri, Sep 2, 2022 at 11:52 AM Lars Ingebrigtsen <larsi@gnus.org> wrote:
> Augusto Stoffel <arstoffel@gmail.com> writes:
>
> > The main constituents of a TeX document outline are chapters, sections
> > and environments. However, the `kind' attribute of a DocumentSymbol is
> > not just some name, as one would reasonably expect. Instead, it's a
> > number, which the LSP client then looks up in a hardcoded table [🤦].
> > So in theory one is constrained to the SymbolKinds mentioned in the
> > spec, none of which is remotely suitable for TeX.
> >
> > Is there some Eglot-friendly way to get around this silly limitation?
>
> This was almost a year ago, so I'm not sure whether it's still relevant,
> but in case it is -- João, do you have any comments here?
>
--
João Távora
[-- Attachment #2: Type: text/html, Size: 1752 bytes --]
next prev parent reply other threads:[~2022-09-02 11:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-26 12:46 bug#50816: 28.0.50; [eglot] Nonstandard SymbolKind values for imenu Augusto Stoffel
2022-09-02 10:52 ` Lars Ingebrigtsen
2022-09-02 11:06 ` João Távora [this message]
2022-09-02 12:13 ` Augusto Stoffel
2022-09-02 12:24 ` Lars Ingebrigtsen
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='CALDnm509D6inOLpLpXoTQ5fP5N_-+M=X57i1h83t+GoHNpru_w@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=50816@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--cc=larsi@gnus.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 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.