GNU bug report logs - #73452
Code lens support in eglot

Previous Next

Full log

Message #58 received at 73452 <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Gutov <dmitry <at> gutov.dev>
To: Felician Nemeth <felician.nemeth <at> gmail.com>
Cc: 73452 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>,
 federico.beffa <at> fbengineering.ch,
 João Távora <joaotavora <at> gmail.com>
Subject: Re: bug#73452: Code lens support in eglot
Date: Thu, 3 Oct 2024 02:26:40 +0300

On 02/10/2024 14:57, Felician Nemeth wrote:
> Dmitry Gutov<dmitry <at> gutov.dev> writes:
> 
>> Running tests is the #1 use I found for them when writing some Go
>> recently. Eglot doesn't have a built-in test launcher of any sort, so
>> that feels like an omission.
> Rust-analyzer has some protocol extensions to work together with a
> remote "Test Explorer".  It seems a test explorer module is part of
> Visual Studio and VS Code.  I think a similar Emacs package that lets
> the user organize/run tests and review test results would be a good ELPA
> package.  (Even if it does not work with Eglot at the beginning.)
> 
> https://learn.microsoft.com/en-us/visualstudio/test/run-unit-tests-with- 
> test-explorer?view=vs-2022
> https://github.com/rust-lang/rust-analyzer/blob/master/docs/dev/lsp- 
> extensions.md#test-explorer

That looks useful, thank you.

I wonder how many of the popular servers implement this, though. And 
what UI an Emacs implementation should prefer (overall that seems a fair 
bit more work than adding buttons inside Eglot-managed buffers).

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.