From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Reliable after-change-functions (via: Using incremental parsing in Emacs) Date: Tue, 31 Mar 2020 16:16:20 +0300 Message-ID: <83zhbw1x7f.fsf@gnu.org> References: <83o8sf3r7i.fsf@gnu.org> <2E218879-0F24-4A20-B210-263C8D0BEEA4@gmail.com> <87o8sdn0ot.fsf@gmail.com> <09E90C25-6119-44D4-85F2-A9CC4196FFE4@gmail.com> <83a73x3bh1.fsf@gnu.org> <87y2rhkwhk.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="71715"; mail-complaints-to="usenet@ciao.gmane.io" Cc: casouri@gmail.com, akrl@sdf.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: =?utf-8?B?xaB0xJtww6FuIE7Em21lYw==?= Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Mar 31 15:17:09 2020 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jJGlQ-000IWY-NW for ged-emacs-devel@m.gmane-mx.org; Tue, 31 Mar 2020 15:17:08 +0200 Original-Received: from localhost ([::1]:37762 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJGlP-0001ez-7x for ged-emacs-devel@m.gmane-mx.org; Tue, 31 Mar 2020 09:17:07 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40853) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJGkT-0000jt-HG for emacs-devel@gnu.org; Tue, 31 Mar 2020 09:16:10 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:37782) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jJGkT-0000jx-CX; Tue, 31 Mar 2020 09:16:09 -0400 Original-Received: from [176.228.60.248] (port=1264 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jJGkS-0003fc-00; Tue, 31 Mar 2020 09:16:08 -0400 In-Reply-To: <87y2rhkwhk.fsf@gmail.com> (message from =?utf-8?B?xaB0xJtw?= =?utf-8?B?w6FuIE7Em21lYw==?= on Tue, 31 Mar 2020 05:56:55 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:246091 Archived-At: > From: Štěpán Němec > Date: Tue, 31 Mar 2020 05:56:55 +0200 > Cc: Eli Zaretskii , emacs-devel , > Stefan Monnier , akrl@sdf.org > > > I see. Then I suggest mentioning it (when you should use the variable) in the documentation of `inhibit-modification-hooks'. > > I think the explanation in (info "(elisp) Change Hooks") is quite good, > but the doc string had better clarify the usage as well. > > How about the attached patch? Thanks, I think this is too wordy for a doc string. I think it should be enough to mention the two variables ("See also ...") and maybe add a link to the ELisp manual section you mention.