From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Xref/tags/lsp possible bug
Date: Mon, 25 Apr 2022 16:05:10 -0400 [thread overview]
Message-ID: <jwvee1l0wga.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: CAJczNmDcg-woUxwwY9aFY_z6Lx56pe9w5KLncozEhSJXxW2bAw@mail.gmail.com
> Okay, it's not a real problem, but I wonder why is it, though.
> I suppose LSP does have a sort of symbol table kept in memory, so
> I think it wouldn't be a big problem to allow the user to query it.
> I suppose it's something that can be added in a future specification.
I must say I don't know why that is, but FWIW in my local experimental
language (Typer) it makes some sense: Typer has no top-level
environment, so if a file is defined as:
fun1 x = <foo>;
fun2 y = <bar>;
...
it's really the same as if it was:
let fun1 x = <foo>
in let fun2 y = <bar>;
in ...
You can still try to cobble up some kind of "list of top-levelish
definitions" but it's inevitably a hack.
OTOH, LSP could define the set of possible choices as the set of
possible "breadcrumbs" info.
Stefan
next prev parent reply other threads:[~2022-04-25 20:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-25 10:01 Xref/tags/lsp possible bug Alessandro Bertulli
2022-04-25 20:05 ` Stefan Monnier via Users list for the GNU Emacs text editor [this message]
2022-04-25 20:29 ` Dmitry Gutov
2022-04-25 21:48 ` Stefan Monnier
2022-04-26 1:41 ` Dmitry Gutov
-- strict thread matches above, loose matches on Subject: below --
2022-04-23 15:28 Alessandro Bertulli
2022-04-23 12:17 Alessandro Bertulli
2022-04-23 12:52 ` Eli Zaretskii
2022-04-24 23:06 ` Dmitry Gutov
2022-04-25 1:32 ` Dmitry Gutov
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=jwvee1l0wga.fsf-monnier+emacs@gnu.org \
--to=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.
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).