From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ihor Radchenko Newsgroups: gmane.emacs.devel Subject: Re: emacs-29 889a550ca08: ; Fix Texinfo warnings Date: Mon, 23 Oct 2023 13:24:21 +0000 Message-ID: <87bkcp8oai.fsf@localhost> 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> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29379"; mail-complaints-to="usenet@ciao.gmane.io" Cc: arash@gnu.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Oct 23 15:23:59 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 1quuuV-0007Ms-LW for ged-emacs-devel@m.gmane-mx.org; Mon, 23 Oct 2023 15:23:59 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1quutZ-0007uw-TV; Mon, 23 Oct 2023 09:23:01 -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 1quutS-0007rE-7v for emacs-devel@gnu.org; Mon, 23 Oct 2023 09:22:54 -0400 Original-Received: from mout01.posteo.de ([185.67.36.65]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1quutO-0003Kx-LL for emacs-devel@gnu.org; Mon, 23 Oct 2023 09:22:53 -0400 Original-Received: from submission (posteo.de [185.67.36.169]) by mout01.posteo.de (Postfix) with ESMTPS id 877A7240028 for ; Mon, 23 Oct 2023 15:22:48 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1698067368; bh=1BB/TCLoepVJKjhodFgZhXFcg2BSJ8CDDIXDz/sUhUo=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version: Content-Transfer-Encoding:From; b=dJ1JiPA/87BqYdrakhdJqqBznB12N3CjESpr1hvhEzL9s/y5UjOfAcB4EuikBcm3x 22Rrwxpuu1n+1+h4bgGIK6uzND9u2nswIrl2PIp1UNEreoqOT6Op5IgjiJDL34yt3h I4SYiKLgnsCf1I92P9Y7GUiO3VYSqik4PeGfmwVyMyGZwts5mwWE8Mj6XFbkbxeTq3 pFF8or+kirOf1uAOWkIuB8dJcAWQVahNHwHPh3G66bDIqaA/smH69taTGJZJHaKVcw /QGYOuuxnmbIjIeWaKYHeSSZS2x+hRvlkpY9GK3BImzVSP5g6zUKI0d8xW1J8wrZzx vhzWs0/WSixcQ== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4SDbTg67ZRz9rxW; Mon, 23 Oct 2023 15:22:47 +0200 (CEST) In-Reply-To: <83lebto6e5.fsf@gnu.org> Received-SPF: pass client-ip=185.67.36.65; envelope-from=yantar92@posteo.net; helo=mout01.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H5=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=unavailable 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:311712 Archived-At: Eli Zaretskii writes: >> What we are getting in org.texi is >> org.texi:15975: warning: @anchor should not appear on @item line >>=20 >> 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: =20=20=20=20 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=E2=80=99s 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. In Org mode, we add @anchor at the same place where the corresponding Org markup (<<>>) is placed. 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. --=20 Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at