bug#65157: 30.0.50; Android port post-merge warnings?

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]

At 72e24ed0316542184f40c05eda2bf7c77808ec0c with all default
configuration I get after

   make -j8 bootstrap

the following warnings:

[...]
./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
[...]
In end of data:
touch-screen.el:163:16: Warning: the function 
‘pixel-scroll-precision-scroll-up-page’ is not known to be defined.
touch-screen.el:162:18: Warning: the function 
‘pixel-scroll-precision-scroll-down-page’ is not known to be defined.
[...]

Pls let me know if you need more information on that ...

bug#65157: 30.0.50; Android port post-merge warnings?

[Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Jens Schmidt <jschmidt4gnu@vodafonemail.de> writes:

> At 72e24ed0316542184f40c05eda2bf7c77808ec0c with all default
> configuration I get after
>
>   make -j8 bootstrap
>
> the following warnings:
>
> [...]
> ./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.  What version of Texinfo is that?

> In end of data:
> touch-screen.el:163:16: Warning: the function
> ‘pixel-scroll-precision-scroll-up-page’ is not known to be defined.
> touch-screen.el:162:18: Warning: the function
> ‘pixel-scroll-precision-scroll-down-page’ is not known to be defined.
> [...]

This should be fixed now.

bug#65157: 30.0.50; Android port post-merge warnings?

[Eli Zaretskii]

> 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.

bug#65157: 30.0.50; Android port post-merge warnings?

[Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors]

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.

bug#65157: 30.0.50; Android port post-merge warnings?

[Eli Zaretskii]

> From: Po Lu <luangruo@yahoo.com>
> Cc: jschmidt4gnu@vodafonemail.de,  65157@debbugs.gnu.org
> Date: Wed, 09 Aug 2023 21:28:44 +0800
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > 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.

Why do you need justification for adding @node's?  What is the
downside of having them.  The advantage is clear: easier navigation
with SPC and DEL.

If you don't need a @node, please ask yourself why you need a @section
of @subsection?

But if you are dead set on not adding @node's, please make those
@node-less @sections @unnumberedsec instead.

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]

On 2023-08-09  03:53, Po Lu wrote:

>> ./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.  What version of Texinfo is that?

Not sure whether still relevant after Eli's remarks on @nodes vs
@sections, but I use

   [emacs-master]$ makeinfo --version
   texi2any (GNU texinfo) 6.7

   Copyright (C) 2017 Free Software Foundation, Inc.
   License GPLv3+: GNU GPL version 3 or later 
<http://gnu.org/licenses/gpl.html>
   This is free software: you are free to change and redistribute it.
   There is NO WARRANTY, to the extent permitted by law.

bug#65157: 30.0.50; Android port post-merge warnings?

[Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Po Lu <luangruo@yahoo.com>
>> Cc: jschmidt4gnu@vodafonemail.de,  65157@debbugs.gnu.org
>> Date: Wed, 09 Aug 2023 21:28:44 +0800
>> 
>> Eli Zaretskii <eliz@gnu.org> writes:
>> 
>> > 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.
>
> Why do you need justification for adding @node's?  What is the
> downside of having them.  The advantage is clear: easier navigation
> with SPC and DEL.
>
> If you don't need a @node, please ask yourself why you need a @section
> of @subsection?
>
> But if you are dead set on not adding @node's, please make those
> @node-less @sections @unnumberedsec instead.

Thanks.

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]

On 2023-08-10  02:37, Po Lu wrote:

>> But if you are dead set on not adding @node's, please make those
>> @node-less @sections @unnumberedsec instead.
> 
> Thanks.

Seems to be resolved, thanks, closing this bug.