all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Clément Pit-Claudel" <cpitclaudel@gmail.com>
Cc: 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 22:49:10 +0300	[thread overview]
Message-ID: <838shzd0zt.fsf@gnu.org> (raw)
In-Reply-To: <9e98ccbd-6b01-d076-79eb-6bd06ab803fb@gmail.com> (message from Clément Pit-Claudel on Sun, 10 May 2020 15:27:47 -0400)

> From: Clément Pit-Claudel <cpitclaudel@gmail.com>
> Date: 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.

If by the time the output arrives the user have edited the buffer, you
will have to throw the output away, and send a new request.  Rinse,
repeat.  Eventually, the user will stop typing, at least for a short
time, and the output that arrives after that could be used for
fontifying because no changes have been done.  But if this never
happens, i.e. the user keeps being ahead of the subprocess, it would
mean the buffer will not be fontified for a time that is long enough
to be an annoyance.  Which means the solution is not workable.  Right?

IOW, the process of sending whatever you need to send and receiving
the output should be fast enough to be completed before the user types
a lot, or at least short enough to hold off buffer modifications, or
else this is simply not going to work.  Think of the current JIT
font-lock: if it doesn't finish fontifying the current windowful by
the time the user decides to type something, the user will complain,
right?



  parent reply	other threads:[~2020-05-10 19:49 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=838shzd0zt.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.