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 17:34:59 +0300 Message-ID: <83mu7w1tkc.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> <83zhbw1x7f.fsf@gnu.org> <87tv24lk8a.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="31143"; 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 16:35:33 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 1jJHzJ-0007zV-3X for ged-emacs-devel@m.gmane-mx.org; Tue, 31 Mar 2020 16:35:33 +0200 Original-Received: from localhost ([::1]:39080 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJHzI-0007OT-47 for ged-emacs-devel@m.gmane-mx.org; Tue, 31 Mar 2020 10:35:32 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:51964) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jJHyc-0006fi-I3 for emacs-devel@gnu.org; Tue, 31 Mar 2020 10:34:52 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:39383) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1jJHyc-0000Gb-2X; Tue, 31 Mar 2020 10:34:50 -0400 Original-Received: from [176.228.60.248] (port=2097 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jJHya-0004b5-Sx; Tue, 31 Mar 2020 10:34:49 -0400 In-Reply-To: <87tv24lk8a.fsf@gmail.com> (message from =?utf-8?B?xaB0xJtw?= =?utf-8?B?w6FuIE7Em21lYw==?= on Tue, 31 Mar 2020 15:36:21 +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:246102 Archived-At: > From: Štěpán Němec > Cc: casouri@gmail.com, emacs-devel@gnu.org, monnier@iro.umontreal.ca, > akrl@sdf.org > Date: Tue, 31 Mar 2020 15:36:21 +0200 > > > 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. > > In that case, could we add the "should" part (or something similar) to > the manual (in addition to the doc string reference you describe)? Most probably yes, but could you show the change you had in mind for the manual? > It is true that careful reading of the manual and the relevant doc > strings as they are now could suffice to make an informed decision > on when `inhibit-modification-hooks' is (in)appropriate, but I think > having some kind of explicit heads-up or dissuation regarding the > likely misuse would be better. I agree, and the manual is the place to have such discussions and recommendations. Thanks.