From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Patrice Dumas Newsgroups: gmane.emacs.devel,gmane.comp.tex.texinfo.general Subject: Re: @anchor on @item line (was: emacs-29 889a550ca08: ; Fix Texinfo warnings) Date: Tue, 7 Nov 2023 11:29:24 +0100 Message-ID: References: <83mswaq5q6.fsf@gnu.org> <87fs218qk6.fsf@localhost> <83lebto6e5.fsf@gnu.org> <87bkcp8oai.fsf@localhost> <838r7to1mu.fsf@gnu.org> <87v8aw75cj.fsf@localhost> <834jigmeb3.fsf@gnu.org> <87msvs5tel.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="15010"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Ihor Radchenko , Eli Zaretskii , help-texinfo@gnu.org, arash@gnu.org, emacs-devel@gnu.org To: Gavin Smith Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Nov 07 11:30:01 2023 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 1r0JLN-0003lK-P3 for ged-emacs-devel@m.gmane-mx.org; Tue, 07 Nov 2023 11:30:01 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r0JL0-0006RB-N9; Tue, 07 Nov 2023 05:29:39 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r0JKw-0006Qy-JN; Tue, 07 Nov 2023 05:29:34 -0500 Original-Received: from smtp1-g21.free.fr ([2a01:e0c:1:1599::10]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1r0JKu-0006FM-Rm; Tue, 07 Nov 2023 05:29:34 -0500 Original-Received: from localhost (unknown [193.55.115.42]) (Authenticated sender: pertusus@free.fr) by smtp1-g21.free.fr (Postfix) with ESMTPSA id E6F06B0054E; Tue, 7 Nov 2023 11:29:22 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=free.fr; s=smtp-20201208; t=1699352968; bh=t5JW1Y677DQz/mQTlFxCyJGc2+Omx7AXB2o/OA+PYRM=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=iFOtOqOn31l2sTuNxtvlBzGcIqbJi36c2I21CRarFRcaWOhVLXwJVNOb8AVRadVMh PFxFpmT8GO2ev8k5UW1HYAScihALjn//WuKPSnMtR6sIZYi+1OuwQ2Ajugzc6D9iRL +9UYWLuo3hCtsCKasB4s/XOFKprdOFnR9dZ1l/j1tb0mtM1jzBc/TQY3kFKyQpJKVM iT5Wf5RtkjfKrOVKNxkdHsmF8gJusRKcOf069MgoAtueh5qBNJaqoI+mf+89zZeFsz c6l9P3+ghH2piqm2G4au6BdoU1/Y7GSrJbpWcopjGTKFEFFoW9CsK0ak7lu+nGE/AS kh/XIQJOZsDAQ== Mail-Followup-To: Patrice Dumas , Gavin Smith , Ihor Radchenko , Eli Zaretskii , help-texinfo@gnu.org, arash@gnu.org, emacs-devel@gnu.org Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=2a01:e0c:1:1599::10; envelope-from=pertusus@free.fr; helo=smtp1-g21.free.fr X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:312292 gmane.comp.tex.texinfo.general:3347 Archived-At: On Mon, Nov 06, 2023 at 07:29:50PM +0000, Gavin Smith wrote: > On Sun, Nov 05, 2023 at 11:30:42AM +0000, Ihor Radchenko wrote: > > May someone please explain the correct usage of @anchor in the above > > example and why the warning is being thrown? > > I don't think there's really much wrong with it. We added more warnings > for nested commands, trying to define which commands should occur in > certain contexts. We have given the @item command a class of > "contain_basic_inline", which excludes anchor commands, as well as > the cross-reference commands. > > I don't remember, or never knew to start with, what the justification > was for giving @item this class. I agree that accepting @anchor and @*ref on @item in @*table line would be ok. > However, for whatever reason, this use of @anchor on an @item line > didn't trigger the warning in earlier releases. My guess is that the code has been fixed to really use the 'flags' of item_LINE and not the flags of @item that appears in @itemize, @enumerate and @multitable which alreay has no restrictions in its content. > It would be easy, I expect, to remove this warning: > > diff --git a/tp/Texinfo/command_data.txt b/tp/Texinfo/command_data.txt > index 7d07b8bd54..df63c6ccd7 100644 > --- a/tp/Texinfo/command_data.txt > +++ b/tp/Texinfo/command_data.txt > @@ -254,8 +254,8 @@ printindex line,formattable_line,close_paragraph,global,contain_pla > listoffloats line,formattable_line,close_paragraph,global,contain_basic_inline LINE_line > exdent line,formatted_line,close_paragraph LINE_line > # or nobrace skipspace, depending on the context > -item_LINE line,formatted_line,close_paragraph,contain_basic_inline LINE_line > -itemx line,formatted_line,close_paragraph,contain_basic_inline LINE_line > +item_LINE line,formatted_line,close_paragraph LINE_line > +itemx line,formatted_line,close_paragraph LINE_line > nodedescription line,close_paragraph LINE_line > # in index entries > subentry line,in_index,contain_basic_inline LINE_line > 0$ > > However, I would like to wait to see if anybody else has any comments first. Looks good to me. -- Pat