all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>, help-texinfo@gnu.org
Cc: arash@gnu.org, emacs-devel@gnu.org
Subject: @anchor on @item line (was: emacs-29 889a550ca08: ; Fix Texinfo warnings)
Date: Sun, 05 Nov 2023 11:30:42 +0000	[thread overview]
Message-ID: <87msvs5tel.fsf@localhost> (raw)
In-Reply-To: <834jigmeb3.fsf@gnu.org>

Hi,

This is a question regarding a recent change in Texinfo.

AFAIU, @anchor in Texinfo can be used to refer to arbitrary place in the
document: https://www.gnu.org/software/texinfo/manual/texinfo/texinfo.html#g_t_0040anchor
In some scenarios, this "arbitrary place" can be located _inside_ an
item.

However, there is a warning being produced when @anchor is found on the
same line with an item:

org.texi:15975: warning: @anchor should not appear on @item line

The problematic .texi source is

    @table @asis
    @item @samp{OrgOdtStyles.xml} @anchor{x-orgodtstyles-xml}
    This file contributes to the @samp{styles.xml} file of the final ODT
    document.  This file gets modified for the following purposes:

Here, the @anchor is referring to OrgOdtStyles.xml file and is not
necessarily linked to the @item itself.

May someone please explain the correct usage of @anchor in the above
example and why the warning is being thrown?

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>



  reply	other threads:[~2023-11-05 11:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <169796650463.2984.6470791064475342706@vcs2.savannah.gnu.org>
     [not found] ` <20231022092145.0486AC09BDB@vcs2.savannah.gnu.org>
2023-10-22 10:30   ` emacs-29 889a550ca08: ; Fix Texinfo warnings Arash Esbati
2023-10-22 11:03     ` Eli Zaretskii
2023-10-23 10:36       ` Arash Esbati
2023-10-23 12:35       ` Ihor Radchenko
2023-10-23 12:44         ` Eli Zaretskii
2023-10-23 13:24           ` Ihor Radchenko
2023-10-23 14:27             ` Eli Zaretskii
2023-10-24  9:11               ` Ihor Radchenko
2023-10-24 11:48                 ` Eli Zaretskii
2023-11-05 11:30                   ` Ihor Radchenko [this message]
2023-11-06 19:29                     ` @anchor on @item line (was: emacs-29 889a550ca08: ; Fix Texinfo warnings) Gavin Smith
2023-11-07 10:29                       ` Patrice Dumas
2023-11-12 19:23                         ` @anchor on @item line Gavin Smith
2023-11-14 21:58                           ` Gavin Smith
2023-11-15  3:30                             ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87msvs5tel.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=arash@gnu.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=help-texinfo@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.