bug-texinfo
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: @menu puts too many restrictions to produce the .info file


From: Christopher Dimech
Subject: Re: @menu puts too many restrictions to produce the .info file
Date: Tue, 27 Oct 2020 19:26:05 +0100

When I use the command line 'emacs file.info' I cannot see the file,
but I can open it in emacs I can see everything, including the menu
even though I put @ignore around the menu.


> Sent: Tuesday, October 27, 2020 at 5:00 PM
> From: "Gavin Smith" <gavinsmith0123@gmail.com>
> To: "Eli Zaretskii" <eliz@gnu.org>
> Cc: "Christopher Dimech" <dimech@gmx.com>, bug-texinfo@gnu.org
> Subject: Re: @menu puts too many restrictions to produce the .info file
>
> On Tue, Oct 27, 2020 at 05:21:05PM +0200, Eli Zaretskii wrote:
> > > From: Christopher Dimech <dimech@gmx.com>
> > > Date: Tue, 27 Oct 2020 10:07:04 +0100
> > > Sensitivity: Normal
> > > Cc: bug-texinfo@gnu.org
> > >
> > > What gets me most frustrated is that when I introduce @bye
> > > somewhere within the document, makeinfo goes nuts.  @bye
> > > is a great command to use when texi2pdf is unsuccessful
> > > so I may investigate. Makeinfo does not give me that possibility.
> > > If I remove the menu but there are references in the document,
> > > the info file is not generated.
> >
> > Instead of @bye use @ignore..@end ignore.
> >
>
> I think that would still lead to many errors about missing nodes and
> so on.
>
> If you used the --force option, it's possible the file would be
> generated anyway.  Also, some hard errors about menus were turned
> recently into warnings.
>
> Using the -c SHOW_MENU=0 option may get rid of some of the warnings,
> at the cost of not outputting the menus.
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]