unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
To: Vladimir Sedach <vas@oneofus.la>
Cc: "Eli Zaretskii" <eliz@gnu.org>,
	"João Távora" <joaotavora@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: Tracking buffer positions across time, without markers (was Re: PL support)
Date: Mon, 11 May 2020 10:18:09 -0400	[thread overview]
Message-ID: <a1263512-e737-49bc-f968-c6144463b5f3@gmail.com> (raw)
In-Reply-To: <87ftc71g1l.fsf@t510.orion.oneofus.la>

On 10/05/2020 20.17, Vladimir Sedach wrote:
> 
> Clément Pit-Claudel <cpitclaudel@gmail.com> writes:
>> Since we don't know beforehand what positions the subprocess will
>> return, I don't think markers can help; right?
> 
> It sounds like the fundamental thing you need here is a function from
> the integers 1 to point-max of the buffer as it was when you sent
> its contents to the sub-process, to the integers 1 to point-max of
> the buffer as it is when the sub-process returns some results.

Yes, eactly, that's what I meant when I wrote "Visual Studio has a nice API for this: there is a way to snapshot a buffer, and to translate positions between two snapshots.  In my example, this allows you to translate 0:3 in the original buffer to 7:10 in the new one."

> Another refinement is to use Stefan's idea of delimiting unmodified
> intervals and only add properties in the modified interval.

Yes, I need to think more about that one :)

> A refinement would be to put the text property on tokens. Sticky text
> properties would do the right thing when changing identifier names.

Interesting idea.  At first I worried that this would be too costly, but font-lock uses text properties and is quite fast…
But wouldn't the process of mapping back from properties to spans of text be very costly?



  reply	other threads:[~2020-05-11 14:18 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
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 [this message]
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=a1263512-e737-49bc-f968-c6144463b5f3@gmail.com \
    --to=cpitclaudel@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=joaotavora@gmail.com \
    --cc=vas@oneofus.la \
    /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).