unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: 73452@debbugs.gnu.org, federico.beffa@fbengineering.ch
Subject: bug#73452: Code lens support in eglot
Date: Tue, 24 Sep 2024 18:48:11 +0300	[thread overview]
Message-ID: <86v7ylcatg.fsf@gnu.org> (raw)
In-Reply-To: <CALDnm51Mxo5_aTccnUBdzH2ObFJRDVBCCWQSMSRctTDSvQuLkA@mail.gmail.com> (message from João Távora on Tue, 24 Sep 2024 15:26:55 +0100)

> Cc: 73452@debbugs.gnu.org
> From: João Távora <joaotavora@gmail.com>
> Date: Tue, 24 Sep 2024 15:26:55 +0100
> 
> 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)

What infrastructure would be needed?

Perhaps you or someone would like to describe the missing
infrastructure, and we could then at least add that to TODO.  And
maybe someone would even like to work on that.

Thanks.





  reply	other threads:[~2024-09-24 15:48 UTC|newest]

Thread overview: 20+ 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
2024-09-24 15:48   ` Eli Zaretskii [this message]
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-10-02 11:57           ` Felician Nemeth
2024-10-02 23:26             ` Dmitry Gutov
2024-10-03 22:43               ` João Távora
2024-10-07 23:33                 ` 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=86v7ylcatg.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=73452@debbugs.gnu.org \
    --cc=federico.beffa@fbengineering.ch \
    --cc=joaotavora@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 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).