unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
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: Sun, 10 May 2020 16:46:29 -0400	[thread overview]
Message-ID: <jwvtv0nh6e7.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <9e98ccbd-6b01-d076-79eb-6bd06ab803fb@gmail.com> ("Clément Pit-Claudel"'s message of "Sun, 10 May 2020 15:27:47 -0400")

> The general problem is this: I send the contents of a buffer to
> a subprocess.  Some time later, the subprocess returns a list of positions
> (offsets from the beginning of the buffer, or line/column pairs, etc).
> At that point, these positions may be stale, since the contents of the
> buffer may have changed.  I need a way to translate these positions
> (relative to the old buffer contents) into positions relative to the new
> buffer contents.

As you said you should be able to use the undo-list for that.
It'll require a bit of work, but hopefully that can be used in
several places, justifying the investment.

If you have the option to ask for a more up-to-date version of the data
to be sent, you can obviously throw the data away, but even in that case
you should be able to do better with fairly little work: use an
after-change-function to keep track of just 2 markers that indicate the
beginning and end of the part of the buffer that's been modified.
Then you can easily translate all the positions before the first and
after the second marker and only discard the data between the two.


        Stefan




  parent reply	other threads:[~2020-05-10 20:46 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 [this message]
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=jwvtv0nh6e7.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=cpitclaudel@gmail.com \
    --cc=eliz@gnu.org \
    --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).