From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Unbalanced change hooks (part 2) [Documentation fix still remaining] Date: Tue, 30 Aug 2016 14:00:54 -0400 Message-ID: References: <20160811112951.GA2154@acm.fritz.box> <7e1478b6-cf00-fcbf-8c24-43bdaa57e2b6@dancol.org> <415d1cca-f32c-624e-a4be-9aadcf8a0f17@dancol.org> <83inujbpek.fsf@gnu.org> <20160830171222.GA6672@acm.fritz.box> <5857ab7e-e85c-c6ae-ba1a-b1337ae57f2c@dancol.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1472677574 17823 195.159.176.226 (31 Aug 2016 21:06:14 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 31 Aug 2016 21:06:14 +0000 (UTC) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 31 23:06:11 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bfChv-0003p1-8j for ged-emacs-devel@m.gmane.org; Wed, 31 Aug 2016 23:06:03 +0200 Original-Received: from localhost ([::1]:55999 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bfChs-0002p1-WE for ged-emacs-devel@m.gmane.org; Wed, 31 Aug 2016 17:06:01 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51971) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bfCfR-0001P5-DN for emacs-devel@gnu.org; Wed, 31 Aug 2016 17:03:30 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bfCfK-0005L9-8W for emacs-devel@gnu.org; Wed, 31 Aug 2016 17:03:28 -0400 Original-Received: from [195.159.176.226] (port=45727 helo=blaine.gmane.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bfCfK-0005Kp-1z for emacs-devel@gnu.org; Wed, 31 Aug 2016 17:03:22 -0400 Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1benKQ-0002f7-V7 for emacs-devel@gnu.org; Tue, 30 Aug 2016 20:00:06 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 31 Original-X-Complaints-To: usenet@blaine.gmane.org Cancel-Lock: sha1:i+Lxc5MOVgMCBdHjIpuzPrTpXYA= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 195.159.176.226 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:207038 Archived-At: > +The region given to each of these functions is a conservative > +approximation of the region about to changed. After running the > +before-change-functions, Emacs will make zero or more fine-grained > +buffer changes and run after-change-functions for each. Do not expect > +before-change-functions and after-change-functions to be called in > +balanced pairs. Looks OK to me. > - Do @emph{not} expect the before-change hooks and the after-change > -hooks be called in balanced pairs around each buffer change. Also > -don't expect the before-change hooks to be called for every chunk of > -text Emacs is about to delete. These hooks are provided on the > -assumption that Lisp programs will use either before- or the > -after-change hooks, but not both, and the boundaries of the region > -where the changes happen might include more than just the actual > -changed text, or even lump together several changes done piecemeal. > + Do @emph{not} expect the before-change hooks and the after-change > +hooks be called in balanced pairs around each buffer change. > +The before-change-functions region is a conservative bound on the zero > +or more fine-grained changes to follow. Emacs informs user code about > +the actual changes to the buffer through calls to > +after-change-functions; these fine-grained changes will always fall > +inside the broad change region Emacs describes by calling > +before-change-functions. Repeats the previous, but otherwise looks fine to me. thanks, Stefan