From: Stephen Leake <stephen_leake@stephe-leake.org>
To: Sebastian Poeplau <sebastian.poeplau@mailbox.org>
Cc: emacs-devel@gnu.org
Subject: Re: eglot's interface for major modes
Date: Sat, 08 Apr 2023 03:30:40 -0700 [thread overview]
Message-ID: <86r0suu0mn.fsf@stephe-leake.org> (raw)
In-Reply-To: <87mt3i3ebu.fsf@mailbox.org> (Sebastian Poeplau's message of "Sat, 08 Apr 2023 11:26:52 +0200")
Sebastian Poeplau <sebastian.poeplau@mailbox.org> writes:
> And then there's one more thing I'm exploring with this major mode. The
> Language Server Protocol has a concept of "semantic tokens" [1] -
> essentially server-provided fontification. The VS Code plugin for Ada
> uses it, and I've been able to make it work in Emacs with lsp-mode.
> (eglot support for semantic tokens seems to be work in progress [2].)
That will be supported by ada-mode when eglot supports it. I was also
working on a patch for eglot for that
(https://github.com/stephe-ada-guru/eglot), but decided to work on
tree-sitter first, partly because of bugs in ada_language_server, mostly
because ada_language_server is not very good for indenting, because the error
recovery is poor.
> The approach is probably inferior to the tree-sitter support for Ada
> that you and others are working on,
Why do you think that? ada_language_server does some semantic analysis
(mostly name resolution), so the results are more precise than a syntax
parser like wisitoken or tree-sitter can provide. ada_language_server is
not incremental, but it's _very_ fast, so you have to have _very_ large
files to notice a delay while editing.
--
-- Stephe
next prev parent reply other threads:[~2023-04-08 10:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 18:20 eglot's interface for major modes Sebastian Poeplau
2023-04-07 21:26 ` Stephen Leake
2023-04-08 9:13 ` Felician Nemeth
2023-04-08 9:37 ` Sebastian Poeplau
2023-04-11 14:05 ` Felician Nemeth
2023-04-13 19:24 ` Sebastian Poeplau
2023-04-13 16:22 ` João Távora
2023-04-13 17:43 ` Felician Nemeth
2023-04-13 19:36 ` Sebastian Poeplau
2023-04-08 9:26 ` Sebastian Poeplau
2023-04-08 10:30 ` Stephen Leake [this message]
2023-04-08 10:53 ` Sebastian Poeplau
2023-04-12 23:06 ` Stephen Leake
2023-04-13 19:23 ` Sebastian Poeplau
2023-04-15 16:38 ` Stephen Leake
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=86r0suu0mn.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--cc=emacs-devel@gnu.org \
--cc=sebastian.poeplau@mailbox.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 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).