From: Eli Zaretskii <eliz@gnu.org>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: arash@gnu.org, emacs-devel@gnu.org
Subject: Re: emacs-29 889a550ca08: ; Fix Texinfo warnings
Date: Mon, 23 Oct 2023 15:44:18 +0300 [thread overview]
Message-ID: <83lebto6e5.fsf@gnu.org> (raw)
In-Reply-To: <87fs218qk6.fsf@localhost> (message from Ihor Radchenko on Mon, 23 Oct 2023 12:35:21 +0000)
> From: Ihor Radchenko <yantar92@posteo.net>
> Cc: Arash Esbati <arash@gnu.org>, emacs-devel@gnu.org
> Date: Mon, 23 Oct 2023 12:35:21 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I fixed octave-mode.texi as well, just didn't mention it in the log
> > message. The rest are maintained outside Emacs, so the respective
> > maintainers will have to pick up the gauntlet (when they upgrade
> > Texinfo).
>
> 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.
next prev parent reply other threads:[~2023-10-23 12:44 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 [this message]
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 ` @anchor on @item line (was: emacs-29 889a550ca08: ; Fix Texinfo warnings) Ihor Radchenko
2023-11-06 19:29 ` 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=83lebto6e5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arash@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=yantar92@posteo.net \
/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.