From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 65157@debbugs.gnu.org, jschmidt4gnu@vodafonemail.de
Subject: bug#65157: 30.0.50; Android port post-merge warnings?
Date: Wed, 09 Aug 2023 21:28:44 +0800 [thread overview]
Message-ID: <87r0ocuyyb.fsf@yahoo.com> (raw)
In-Reply-To: <83sf8sl5yk.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 09 Aug 2023 16:07:31 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: 65157@debbugs.gnu.org
>> Date: Wed, 09 Aug 2023 09:53:13 +0800
>> From: Po Lu via "Bug reports for GNU Emacs,
>> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
>>
>> Jens Schmidt <jschmidt4gnu@vodafonemail.de> writes:
>>
>> > ./android.texi:320: warning: node `Android Windowing' is next for
>> > `Android Environment' in menu but not in sectioning
>> > ./android.texi:528: warning: node `Android Environment' is prev for
>> > `Android Windowing' in menu but not in sectioning
>>
>> I don't receive this warning here, nor can I locate any inconsistencies
>> between the menu and sectioning.
>
> I see you used @section's without a @node. Why did you do that? It
> is in general not recommended, as it makes it harder for the readers
> to find those node-less sections.
>
> I suggest to add @node's there.
Thanks. How about @subsection's? The relative importance of the
contents of those node-less sections doesn't justify placement in
their own nodes, IMHO.
next prev parent reply other threads:[~2023-08-09 13:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 19:36 bug#65157: 30.0.50; Android port post-merge warnings? Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-09 1:53 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-09 13:07 ` Eli Zaretskii
2023-08-09 13:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-08-09 13:45 ` Eli Zaretskii
2023-08-10 0:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-11 19:23 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-09 18:58 ` Jens Schmidt via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r0ocuyyb.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=65157@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jschmidt4gnu@vodafonemail.de \
--cc=luangruo@yahoo.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).