From: Karl Fogel <kfogel@red-bean.com>
To: Lars Tveito <larstvei@ifi.uio.no>
Cc: emacs-devel@gnu.org
Subject: Re: Detect all changes in a buffer
Date: Fri, 15 Jul 2016 16:07:03 -0500 [thread overview]
Message-ID: <87r3autxu0.fsf@red-bean.com> (raw)
In-Reply-To: <m2poqekgc0.fsf@ifi.uio.no> (Lars Tveito's message of "Fri, 15 Jul 2016 18:37:35 +0200")
Lars Tveito <larstvei@ifi.uio.no> writes:
>I am developing a minor mode that enables real-time collaboration. I
>wish to detect /all/ changes made to a buffer. So far I'm using
>`before-change-functions' to detect deletions and
>`after-change-functions' to detect insertions.
You might already know about these, but just in case:
There was some work on this in the past -- the effort I remember was based on a collaboration protocol called "Obby", but now that I look at https://www.emacswiki.org/emacs/CollaborativeEditing I see there were some other efforts as well.
I don't know if anything there would save you time, but wanted to point it out just in case.
(You raise a good question about `inhibit-modification-hooks', and I don't know the answer to it.)
Best regards,
-Karl
>The problem is that some functions utilizes
>`inhibit-modification-hooks', even though they make changes to the
>buffer. An example is `eshell-send-input'.
>
>The first question is whether you have any suggestions as to how to get
>around this? The second is whether it is considered OK for functions to
>use this hook even though the function makes changes to the buffer? The
>documentation for change hooks states "These hook variables let you
>arrange to take notice of all changes in all buffers" which is not
>really true if changes are done whilst `inhibit-modification-hooks' is
>non-nil.
>
>- Lars
next prev parent reply other threads:[~2016-07-15 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-15 16:37 Detect all changes in a buffer Lars Tveito
2016-07-15 21:07 ` Karl Fogel [this message]
2016-07-16 2:24 ` raman
2016-07-16 3:43 ` Stefan Monnier
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=87r3autxu0.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=emacs-devel@gnu.org \
--cc=larstvei@ifi.uio.no \
/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).