From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: cpitclaudel@gmail.com, 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 05:27:31 +0300 [thread overview]
Message-ID: <837dxjcijw.fsf@gnu.org> (raw)
In-Reply-To: <jwvtv0nh6e7.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sun, 10 May 2020 16:46:29 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org,
> João Távora
> <joaotavora@gmail.com>
> Date: Sun, 10 May 2020 16:46:29 -0400
>
> 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.
This is all possible, of course, but I don't (yet) see why it would be
necessary. We survive without this complexity when using JIT
font-lock, and any alternative back-end for the same job should be
able to reuse the same basic architecture.
next prev parent reply other threads:[~2020-05-11 2:27 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 [this message]
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=837dxjcijw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cpitclaudel@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=joaotavora@gmail.com \
--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.
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).