From: Stefan Monnier <monnier@iro.umontreal.ca>
To: phillip.lord@newcastle.ac.uk (Phillip Lord)
Cc: emacs-devel@gnu.org
Subject: Re: [Request for Mentor] subst-char-in-region
Date: Mon, 15 Dec 2014 09:29:07 -0500 [thread overview]
Message-ID: <jwv61ddm2p0.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87a92pyur5.fsf@newcastle.ac.uk> (Phillip Lord's message of "Mon, 15 Dec 2014 12:15:10 +0000")
> Initially, because I wasn't sure that the a-c-f gave me all the
> information that I needed. I thought it might do, but I was confused by
> the third argument which is "length in bytes of the pre-change text". Is
> "length in bytes" the same as "char position". I presumed note.
Ha, nicely spotted, that's a bug in the docstring. It passes (or
should anyway) the length in characters.
> The difficulty is that in some cases the conversion function uses the
> contents of this buffer to work out the equivalent location in that
> buffer. When the b-c-f is called the two buffers are in sync, so this
> conversion works. But when the a-c-f is called, the two buffers are not
> in sync because we haven't percolated the change yet.
So, rather than the length of the previous text, you'd need to actually
know the previous text? Of course, you can use b-c-f to stash the
"previous text", but indeed it won't necessarily always be exactly
right, in the sense that the previous text stashed in b-c-f may not have
the exact same boundaries, so you'll need to massage it a bit.
The way I see it, you'll need to do something like
(defvar-local my-before-change-text nil)
(defun my-bcf (beg end)
(setq my-before-change-text
(if (null my-before-change-text)
(cons beg (buffer-substring beg end))
(let* ((oldbeg (car my-before-change-text))
(oldtext (cdr my-before-change-text))
(oldend (+ oldbeg (length oldtext)))
(newbeg (min beg oldbeg))
(newend (max end oldend)))
(cl-assert (equal oldtext (buffer-substring oldbeg oldend)))
(if (or (< newbeg oldbeg) (> newend oldend))
(cons newbeg (buffer-substring newbeg newend))
my-before-change-text)))))
(add-hook 'before-change-functions #'my-bcf)
And then in after-change-functions, you'll need something like
(defun my-acf (beg end oldlen)
(let ((oldtext (substring (cdr my-before-change-text)
(- beg (car my-before-change-text))
(+ oldlen (- beg (car my-before-change-text))))))
(setq my-before-change-text nil)
...))
-- Stefan
next prev parent reply other threads:[~2014-12-15 14:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 11:43 [Request for Mentor] subst-char-in-region Phillip Lord
2014-12-12 14:35 ` Stefan Monnier
2014-12-12 15:05 ` Phillip Lord
2014-12-12 16:17 ` Stefan Monnier
2014-12-15 12:15 ` Phillip Lord
2014-12-15 14:29 ` Stefan Monnier [this message]
2014-12-16 11:30 ` Phillip Lord
2014-12-16 14:07 ` Stefan Monnier
2014-12-16 16:05 ` Phillip Lord
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=jwv61ddm2p0.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=phillip.lord@newcastle.ac.uk \
/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).