unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Federico Beffa <federico.beffa@fbengineering.ch>
Cc: 73452@debbugs.gnu.org
Subject: bug#73452: Code lens support in eglot
Date: Tue, 24 Sep 2024 15:26:55 +0100	[thread overview]
Message-ID: <CALDnm51Mxo5_aTccnUBdzH2ObFJRDVBCCWQSMSRctTDSvQuLkA@mail.gmail.com> (raw)
In-Reply-To: <05f4d679-d2cd-409c-aafd-bfac2eda7a21@fbengineering.ch>

There is a discussion thread about this in the Eglot GitHub downstream tracker.

https://github.com/joaotavora/eglot/pull/71

The current consensus there is that the feature is not _that_ useful,
and that a clean implementation isn't really trivial since there is no
underlying Emcas support structure (like there is for documentation,
cross-referencing, diagnostics, snippets, etc)

João

On Tue, Sep 24, 2024 at 3:02 PM Federico Beffa
<federico.beffa@fbengineering.ch> wrote:
>
> Hi,
>
> This is not a bug report, but rather an inquiry or feature request. I'm wondering if there are any plans for eglot to support code lens.
>
> These provide quite useful functionality. For example, the Haskell language server allows putting expressions (typically for test or documentation) in comments with a special syntax. The server then offers to execute the code (in VSCode appearing as a small button above the expression). When pressed, it inserts the result in a comment just below. Here's an example after execution:
>
> ```haskell
> addOne :: (Num a) => a -> a
> addOne x = x + 1
>
> -- >>> addOne 2
> -- 3
> ```
>
> Thanks for the great work!
> Fede



-- 
João Távora





  reply	other threads:[~2024-09-24 14:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-24 14:02 bug#73452: Code lens support in eglot Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-24 14:26 ` João Távora [this message]
2024-09-24 15:48   ` Eli Zaretskii
2024-09-24 21:01     ` João Távora
2024-09-25 11:31       ` Eli Zaretskii
2024-09-26  8:09         ` João Távora
2024-09-26 15:35           ` Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-26 17:12             ` João Távora
2024-09-26 19:07               ` Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-26 23:47                 ` Dmitry Gutov
2024-09-27  5:55             ` Eli Zaretskii
2024-09-27  0:20         ` Dmitry Gutov
2024-09-27  6:53           ` Eli Zaretskii
2024-09-27 19:27             ` Dmitry Gutov
2024-09-25  7:04   ` Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-25  7:50     ` João Távora

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=CALDnm51Mxo5_aTccnUBdzH2ObFJRDVBCCWQSMSRctTDSvQuLkA@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=73452@debbugs.gnu.org \
    --cc=federico.beffa@fbengineering.ch \
    /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).