From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: "João Távora" <joaotavora@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Tracking buffer positions across time, without markers (was Re: PL support)
Date: Sat, 9 May 2020 18:22:24 -0400 [thread overview]
Message-ID: <942a8cb1-0382-cf83-5ff9-4e776c2660f0@gmail.com> (raw)
In-Reply-To: <CALDnm51N=9Ynh85M5ttpoZ46MuS8bBdnXKg570AnBNg3tBWdvg@mail.gmail.com>
On 09/05/2020 17.38, João Távora wrote:
> On Sat, May 9, 2020 at 8:47 PM Clément Pit-Claudel <cpitclaudel@gmail.com <mailto:cpitclaudel@gmail.com>> wrote:
>
> Can you clarify what you mean by 'a solved problem'?
>
>
> I meant it in the context of LSP.
>
>
> One long-standing issue that I've had with Emacs is that I don't know of a way to track buffer positions without adding markers. Here's a concrete example:
>
> I start with a buffer that contains "int foo ()", and send that to a subprocess (say a syntax highlighter, for example). It returns [0:3:type; 4:7:name]. In the meantime, the user has inserted more text in the buffer, which now contains "static int foo ()". If I apply the highlighting as-is, it will be all wrong!
>
>
> Some idle time after you type, Eglot will inform the LSP server
> that things have changed, and it will reply with more stuff
> to highlight.
>
> This is how I interpret this. It's the way it works with, say syntax
> errors, which are already supported. I've NOT looked at the spec.
>
> Did this help?
A bit. But this works only if the interaction is fast enough, right? (Same for syntax errors: positions may well be outdated by the time the errors come back)
next prev parent reply other threads:[~2020-05-09 22:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 19:47 Tracking buffer positions across time, without markers (was Re: PL support) Clément Pit-Claudel
2020-05-09 21:38 ` João Távora
2020-05-09 22:22 ` Clément Pit-Claudel [this message]
2020-05-09 23:26 ` João Távora
2020-05-10 3:45 ` Clément Pit-Claudel
2020-05-10 4:32 ` Eli Zaretskii
2020-05-10 19:27 ` Clément Pit-Claudel
2020-05-10 19:42 ` Drew Adams
2020-05-10 19:49 ` Eli Zaretskii
2020-05-10 20:52 ` Clément Pit-Claudel
2020-05-11 14:24 ` Eli Zaretskii
2020-05-11 15:03 ` Clément Pit-Claudel
2020-05-11 15:25 ` Stefan Monnier
2020-05-10 20:46 ` Stefan Monnier
2020-05-11 2:27 ` Eli Zaretskii
2020-05-11 3:19 ` Stefan Monnier
2020-05-11 0:17 ` Vladimir Sedach
2020-05-11 14:18 ` Clément Pit-Claudel
2020-05-11 15:16 ` João Távora
2020-05-11 15:33 ` Clément Pit-Claudel
2020-05-11 15:44 ` João Távora
2020-05-11 16:02 ` Clément Pit-Claudel
2020-05-11 16:11 ` João Távora
2020-05-11 17:20 ` Stefan Monnier
2020-05-11 14:39 ` Eli Zaretskii
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=942a8cb1-0382-cf83-5ff9-4e776c2660f0@gmail.com \
--to=cpitclaudel@gmail.com \
--cc=emacs-devel@gnu.org \
--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).