On Tue, Oct 20, 2020 at 05:30:15PM +0200, Christopher Dimech wrote:
> Understood. Had thought it exists but not documented, but reading your
> comment again, you are correct. Would one be able to call it inside the
> source code?
Currently customization variables can only be set on the command li
On Tue, Oct 20, 2020 at 03:02:58PM +0200, Christopher Dimech wrote:
> I have sent you a small test, it is not with anchors with with simple nodes
> and
> sections:
>
> I am getting the following output from makeinfo
>
For some reason now the 'unreferenced node' messages have disappeared,
but th
On Tue, Oct 20, 2020 at 05:59:56PM +0100, Gavin Smith wrote:
> On Tue, Oct 20, 2020 at 04:53:11PM +0100, Gavin Smith wrote:
> > If an author wants to have irregular menu or node structures for some
> > reason (I haven't made sense exactly of what Christopher is doing
> > with his documents) then th
On Tue, Oct 20, 2020 at 04:53:11PM +0100, Gavin Smith wrote:
>
> Possibly, @novalidate was supposed to do this, as well as checking
> cross-references:
>
> https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Pointer-Validation.html
>
> > Instead, makeinfo checks that the tree construct
On Tue, Oct 20, 2020 at 03:02:58PM +0200, Christopher Dimech wrote:
> ./gela-test.texi:9: node `Introduction' lacks menu item for
> `Specif-Intactv-Arg' despite being its Up target
I don't see why this should be a fatal error, when the others are
just warnings, so I've changed this to be just a w
I attach a file to see how I used floats to display images
where indenting makes sense as in standard languages.
Things are fine with sectioning, title, ... and can use whole
line.
But I see many instances when users want to include many
@if* statements, including within other constructs. I see
On Tue, Oct 20, 2020 at 04:53:11PM +0100, Gavin Smith wrote:
> If an author wants to have irregular menu or node structures for some
> reason (I haven't made sense exactly of what Christopher is doing
> with his documents) then they could use explicit node pointers,
> specifying Next/Prev/Up for ea
On Tue, Oct 20, 2020 at 05:30:15PM +0200, Christopher Dimech wrote:
> I also mention that Makeinfo states that @ifset and @ifclear
> should only appear at a line beginning. I suggest that it be made
> as other region commands that are allowed indentation.
This is not necessarily easy to implement
The simplest solution for Christopher's document is to delete
the menu altogether: delete the four lines
@menu
* Intactv-Function:: Interactive Functions.
* Tpsw-Cmd:: The Tpsw Interactive Command with Numeric Arguments.
@end menu
and the errors all go away.
On Tue, Oct 20, 2020 at 03:
Understood. Had thought it exists but not documented, but reading your
comment again, you are correct. Would one be able to call it inside the
source code?
Finding a variable like that becomes vital for those which plan deviates
from the popular way.
I also mention that Makeinfo states that @ifs
On Tue, Oct 20, 2020 at 04:33:53PM +0200, Christopher Dimech wrote:
> Sure, but ALLOW_NON_TREE_NODE_STRUCTURE is not there.
Of course, this is something to be added that I proposed in the mail
following your report. It is not implemented already! I would prefer
to have Gavin look at the proposal
Sure, but ALLOW_NON_TREE_NODE_STRUCTURE is not there.
> Sent: Tuesday, October 20, 2020 at 4:15 PM
> From: "Patrice Dumas"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: @menu puts too many restrictions to produce the .info file
>
> On Tue, Oct 20, 2020 at 04:10:41PM +0200
On Tue, Oct 20, 2020 at 04:10:41PM +0200, Christopher Dimech wrote:
> Where are the customization variables documented?
In the node 'Customization Variables' of the texinfo manual
https://www.gnu.org/software/texinfo/manual/texinfo/html_node/Customization-Variables.html
--
Pat
Where are the customization variables documented?
> Sent: Tuesday, October 20, 2020 at 3:03 PM
> From: "Patrice Dumas"
> To: "Christopher Dimech"
> Cc: "help-texinfo gnu"
> Subject: Re: @menu puts too many restrictions to produce the .info file
>
> On Tue, Oct 20, 2020 at 02:49:28PM +0200, Chr
On Tue, Oct 20, 2020 at 03:31:10PM +0200, Christopher Dimech wrote:
> It should not be assumed that the author made mistakes. At least
> not problems with how one structures the document. Because when
> using texi2pdf all of that is acceptable.
On the one hand I agree that it may be annoying for a
It should not be assumed that the author made mistakes. At least
not problems with how one structures the document. Because when
using texi2pdf all of that is acceptable.
Message is intended to start a discussion on improving some aspects
for those intending to do non-trivial work in texinfo.
And
On Tue, Oct 20, 2020 at 02:49:28PM +0200, Christopher Dimech wrote:
> I wish to point out that @menu puts a lot of restrictions on running
> makeinfo.
>
>
Do you have a use case in which this would not be an error:
> 1. Having an unreferenced node
> 2. lacking some item in the Menu
> 3. Not havi
I have sent you a small test, it is not with anchors with with simple nodes and
sections:
I am getting the following output from makeinfo
makeinfo 00-gungadin-elisp-abbrev.texi; emacs gungadin-elisp-abbrev.info
00-gungadin-elisp-abbrev.texi:22: warning: @end ifclear should only appear at a
line
I wish to point out that @menu puts a lot of restrictions on running
makeinfo.
1. Having an unreferenced node
2. lacking some item in the Menu
3. Not having same order in menu as in Sectioning
4. Menu complains about @anchor
5. Menu complains of @sebsectioning
I do get use cases where the menu i
On Tue, Oct 20, 2020 at 02:35:25PM +0200, Christopher Dimech wrote:
> When I use an anchor, the link does not work when I use @ref
> when I run makeinfo
You'll need to be much more specific. Which format? What does not
work? makeinfo by itself setup links but does not use them. Also
probably t
When I use an anchor, the link does not work when I use @ref
when I run makeinfo
21 matches
Mail list logo
