From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: emacs-29 889a550ca08: ; Fix Texinfo warnings Date: Mon, 23 Oct 2023 17:27:05 +0300 Message-ID: <838r7to1mu.fsf@gnu.org> References: <169796650463.2984.6470791064475342706@vcs2.savannah.gnu.org> <20231022092145.0486AC09BDB@vcs2.savannah.gnu.org> <83mswaq5q6.fsf@gnu.org> <87fs218qk6.fsf@localhost> <83lebto6e5.fsf@gnu.org> <87bkcp8oai.fsf@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10037"; mail-complaints-to="usenet@ciao.gmane.io" Cc: arash@gnu.org, emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Oct 23 16:28:14 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 1quvuc-0002In-JX for ged-emacs-devel@m.gmane-mx.org; Mon, 23 Oct 2023 16:28:10 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1quvto-000465-U4; Mon, 23 Oct 2023 10:27:21 -0400 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 1quvtk-00041K-5K for emacs-devel@gnu.org; Mon, 23 Oct 2023 10:27:16 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1quvti-0002OF-EY; Mon, 23 Oct 2023 10:27:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=g7jMn5Lp3QStQsc3O25slOBHOBCck2NJJkGPUe9iQ3c=; b=ND252VluPu81mwxw8KU1 j+hHCTClnZqeiY3UTXTCEyjHAcBVzz9lqswRVsoq0Tx9f0y82Nihvhd0AZuezvTDPMrUXaRSKQKrF Vw1J6St0gfQX84ZSUcDGu8lMguqA64O+1WespnV+pByIrUive8LPhu5VVXutPN3hrzdoFYBUTAfrq r71jmbvrzGHnl1mb5U0kItuZAHTmFcUr9+oktLJBfaRtNFf06M9IqNbrCBWnD3WcjbvaBkCzbJSJf ++gQ5AMvNbK+2xrIMh6fGZNWhCppbBq3n1Ev8+6qImLqNda5G8kDjdhx9p41o6nyyigWus/5GPTGf Khq+jdLROqnxaA==; In-Reply-To: <87bkcp8oai.fsf@localhost> (message from Ihor Radchenko on Mon, 23 Oct 2023 13:24:21 +0000) 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:311716 Archived-At: > From: Ihor Radchenko > Cc: arash@gnu.org, emacs-devel@gnu.org > Date: Mon, 23 Oct 2023 13:24:21 +0000 > > Eli Zaretskii writes: > > >> What we are getting in org.texi is > >> org.texi:15975: warning: @anchor should not appear on @item line > >> > >> May someone familiar with Texinfo explain what is the problem? > > > > What is unclear in the warning's text? I think it speaks for itself. > > According to Texinfo manual: > > An anchor is a position in your document, labelled so that > cross-references can refer to it, just as they can to nodes. You > create an anchor with the @anchor command, and give the label as a > normal brace-delimited argument. For example: > > This marks the @anchor{x-spot}spot. > ... > @xref{x-spot,,the spot}. > > ... > > It is best to put @anchor commands just before the position you wish > to refer to; that way, the reader’s eye is led on to the correct > text when they jump to the anchor. You can put the @anchor command > on a line by itself if that helps readability of the source. > Whitespace (including newlines) is ignored after @anchor. > > I do not see any clear reason why one may not put @anchor at the same > line with @item. I don't understand what you are saying here. Are you saying that the warning is bogus and should not be emitted in this case? Or that the Texinfo manual should explain better why @anchor should not appear on an @item line? If so, please take this up with the Texinfo maintainers, and ask them either to change the code or to fix the manual. Me, I would simply move the @anchor line before the @item, where it belongs. It will shut up the warning and also make the manual cleaner from the Texinfo POV. (Thet's what I did in other cases where this warning was emitted by makeinfo 7.1.) But that's me. > In Org mode, we add @anchor at the same place where the corresponding > Org markup (<<>>) is placed. That's a mistake, IMO. @anchor is basically the same as @node. > I guess we might try to put @anchor on a separate line just for the sake > of avoiding this warning, but I am not confident that it is always safe > and won't break Texinfo markup. It won't, since that's how @anchor is supposed to be used.