From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Daniel Colascione Newsgroups: gmane.emacs.devel Subject: Re: Unbalanced change hooks (part 2) [Documentation fix still remaining] Date: Mon, 29 Aug 2016 19:54:52 -0700 Message-ID: <341353e9-8388-103b-7c45-3c2a667081c5@dancol.org> References: <20160810161821.GB3413@acm.fritz.box> <83wpjofttf.fsf@gnu.org> <20160810185735.GD3413@acm.fritz.box> <20160811112951.GA2154@acm.fritz.box> <7e1478b6-cf00-fcbf-8c24-43bdaa57e2b6@dancol.org> <415d1cca-f32c-624e-a4be-9aadcf8a0f17@dancol.org> <83inujbpek.fsf@gnu.org> <83eg57bl8f.fsf@gnu.org> <5ee6ff4a-2d58-82f1-8e83-479c62f0b729@dancol.org> <837fazbjb4.fsf@gnu.org> <75100b15-d49f-5a1a-d73b-24db77c891bf@dancol.org> <831t17bged.fsf@gnu.org> <83shtn9e0z.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Trace: blaine.gmane.org 1472525723 31334 195.159.176.226 (30 Aug 2016 02:55:23 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 30 Aug 2016 02:55:23 +0000 (UTC) User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 Cc: emacs-devel@gnu.org To: Eli Zaretskii , Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 30 04:55:18 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 1beZCm-0007NS-38 for ged-emacs-devel@m.gmane.org; Tue, 30 Aug 2016 04:55:16 +0200 Original-Received: from localhost ([::1]:46652 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1beZCj-0007Bc-I2 for ged-emacs-devel@m.gmane.org; Mon, 29 Aug 2016 22:55:13 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36996) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1beZCZ-000795-T8 for emacs-devel@gnu.org; Mon, 29 Aug 2016 22:55:08 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1beZCU-0003i4-MW for emacs-devel@gnu.org; Mon, 29 Aug 2016 22:55:02 -0400 Original-Received: from dancol.org ([2600:3c01::f03c:91ff:fedf:adf3]:43904) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1beZCU-0003hb-As; Mon, 29 Aug 2016 22:54:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dancol.org; s=x; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version:Date:Message-ID:From:Cc:References:To:Subject; bh=j0pz2zvrFQ2GysZjYQxqhZ7Xrv8Lh7AUzY+Ey8xQNto=; b=h8oCr0BW35OCcRqwQKcw1odwF32KQgRzBiZPnj9QSXpzVtnqYgoOVkkcdg7SKMm9LP7mYIfe4/AY4QglxdB9FcDjPIWJ8+r9VfNP0So3GCKae/lsOfLc97zFWdzRU5eWs4Fd3/0Y4wWOdP3qjuZ/1HWg8Xgt7rx1HgfaCoU32EpwpP+KsbNQ5DdCTRyBWAn9cyTmJGF2ml/qcPy4mF+Lk1rVBTeCsocOAhYJ+GQubbySjpE8i8S0ieKq3yIB1kcCgfn7f+GPYdxUwE0aLFOLRZyxRmLcWjGkRRkLDJ/Fv443a38QTxCVQCJehTnPYfcR7FfgTjDEKZPoYmaPl1qZlg==; Original-Received: from c-73-97-199-232.hsd1.wa.comcast.net ([73.97.199.232] helo=[192.168.1.173]) by dancol.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.84_2) (envelope-from ) id 1beZCR-0001WJ-U6; Mon, 29 Aug 2016 19:54:55 -0700 In-Reply-To: <83shtn9e0z.fsf@gnu.org> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 2600:3c01::f03c:91ff:fedf:adf3 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:206915 Archived-At: On 08/29/2016 07:38 PM, Eli Zaretskii wrote: >> From: Stefan Monnier >> Cc: Daniel Colascione , emacs-devel@gnu.org >> Date: Mon, 29 Aug 2016 20:25:06 -0400 >> >>>> #1 breaks the entire b-c-f model --- "hey, I'm about to modify the >>>> buffer, so throw away caches" ---- and can lead to anything with a >>>> cache flush in b-c-f (like syntax-ppss) not properly discarding >>>> out-of-date buffer information. >>> That single case of #1 is revert-buffer, which conceptually throws >>> away the entire buffer and replaces it with what's on disk. That it >>> actually keeps portions of the buffer is an optimization, but the >>> concept still stands. So I don't see how it breaks the entire model, >>> at least not in practice. >> >> The optimization is beside the point: not calling b-c-f in some corner >> case breaks the entire model because a user such as syntax-ppss relies >> on b-c-f to know when to flush its cache, so if you don't call it when >> the buffer is modified, the cache ends up stale. > > I'm saying that flushing the entire cache in that case is not a > problem, it's what needs to be done anyway. How is a mode supposed to know that it's supposed to flush its cache?