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.comp.tex.texinfo.general,gmane.emacs.devel Subject: Re: @anchor on @item line Date: Wed, 15 Nov 2023 05:30:43 +0200 Message-ID: <83jzqjsnfg.fsf@gnu.org> References: <87fs218qk6.fsf@localhost> <83lebto6e5.fsf@gnu.org> <87bkcp8oai.fsf@localhost> <838r7to1mu.fsf@gnu.org> <87v8aw75cj.fsf@localhost> <834jigmeb3.fsf@gnu.org> <87msvs5tel.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29756"; mail-complaints-to="usenet@ciao.gmane.io" Cc: pertusus@free.fr, yantar92@posteo.net, help-texinfo@gnu.org, arash@gnu.org, emacs-devel@gnu.org To: Gavin Smith Original-X-From: help-texinfo-bounces+gnu-help-texinfo2=m.gmane-mx.org@gnu.org Wed Nov 15 04:31:33 2023 Return-path: Envelope-to: gnu-help-texinfo2@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 1r36cm-0007aX-LT for gnu-help-texinfo2@m.gmane-mx.org; Wed, 15 Nov 2023 04:31:33 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1r36cI-000294-RJ; Tue, 14 Nov 2023 22:31:02 -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 1r36cD-00028B-TM; Tue, 14 Nov 2023 22:30:59 -0500 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 1r36cC-0001nD-L1; Tue, 14 Nov 2023 22:30:56 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=QsYfoxPzAW8DuOUUiMMuByn2RqwTznqPybFIMjJCeTw=; b=qJpr6/Oldjcn T1ED3MoWb6Np/nvYJlevY9auM1nXEYskBoeFTzWK4G431hT8AOSJnck5a1gQ2DqlKr2+8zOku39GA J4cJ6lx5eAnlC28lyWqHyy4TqifcMlFPFrr0AfNTZD4faNVJbscGe/ufZn1FPsWjX2gVx1OWevyUG 1eWZOtJS0sjgixqdkJbgj0Lnf3aQe38BIE3YniAf6+GTw/dCSTBgAt2xGPr5pzOH5zaFGm9kYbeS5 Et9wSisVsYCQH1c3kIEleQ6nAmK5r8DHoLDuDs2gPHBBwXkL0GIot21CSKws0P7410EFth7aCePk3 o3uRFNk7b24oBXPTZ6MIfw==; In-Reply-To: (message from Gavin Smith on Tue, 14 Nov 2023 21:58:01 +0000) X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-texinfo-bounces+gnu-help-texinfo2=m.gmane-mx.org@gnu.org Original-Sender: help-texinfo-bounces+gnu-help-texinfo2=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.comp.tex.texinfo.general:3350 gmane.emacs.devel:312751 Archived-At: > From: Gavin Smith > Date: Tue, 14 Nov 2023 21:58:01 +0000 > > @anchor should not appear in any context where it does not > correspond to a single position in the output file. Good luck with documenting this restriction in a way that Texinfo users can use in practice without a very deep understanding how the converters work. MO is that @anchor should always be on a line of its own. I suggest to say that in the Texinfo manual, and that using it inline is discouraged. There are no good reasons for such inline use in Texinfo documents, IME.