From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Viewing Links for a info file
Date: Fri, 16 Oct 2020 13:58:46 +0300 [thread overview]
Message-ID: <83zh4mv3mh.fsf@gnu.org> (raw)
In-Reply-To: <trinity-a4f6843b-5cc3-498b-84ff-95fb52eee0cc-1602845541335@3c-app-mailcom-bs01> (message from Christopher Dimech on Fri, 16 Oct 2020 12:52:21 +0200)
> From: Christopher Dimech <dimech@gmx.com>
> Cc: help-gnu-emacs@gnu.org
> Date: Fri, 16 Oct 2020 12:52:21 +0200
>
> I have been getting these complaints.
>
> makeinfo 00-gungadin-elisp-abbrev.texi
> 00-gungadin-elisp-abbrev.texi:19: warning: @end ifclear should only appear at a line beginning
> 00-gungadin-elisp-abbrev.texi:52: warning: @end ifset should only appear at a line beginning
> 00-gungadin-elisp-abbrev.texi:103: @menu reference to nonexistent node `Introduction'
> 00-gungadin-elisp-abbrev.texi:110: @detailmenu reference to nonexistent node `Modifier-Keys'
> 00-gungadin-elisp-abbrev.texi:111: @detailmenu reference to nonexistent node `Key-Mnemonics'
> 00-gungadin-elisp-abbrev.texi:112: @detailmenu reference to nonexistent node `Composing-KeySeq'
> 00-gungadin-elisp-abbrev.texi:113: @detailmenu reference to nonexistent node `Complete-Kbd'
> 00-gungadin-elisp-abbrev.texi:114: @detailmenu reference to nonexistent node `Docu-KeySeq'
> 00-gungadin-elisp-abbrev.texi:115: @detailmenu reference to nonexistent node `Emacs-Tutorials-Eww'
> 00-gungadin-elisp-abbrev.texi:117: @detailmenu reference to nonexistent node `Docu-Function'
> 00-gungadin-elisp-abbrev.texi:118: @detailmenu reference to nonexistent node `Intactv-Function'
> 00-gungadin-elisp-abbrev.texi:119: @detailmenu reference to nonexistent node `UPrefix-Argument'
> 00-gungadin-elisp-abbrev.texi:120: @detailmenu reference to nonexistent node `Fnc-ArgSet-PrPfx'
I think this diagnostics is quite self-explanatory, no?
I suggest to consult the Texinfo manual if you are unsure how to
correctly write these constructs in Texinfo.
next prev parent reply other threads:[~2020-10-16 10:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 23:59 Viewing Links for a info file Christopher Dimech
2020-10-16 2:22 ` Brett Gilio
2020-10-16 2:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-16 2:58 ` Brett Gilio
2020-10-16 5:59 ` Eli Zaretskii
2020-10-16 9:42 ` Christopher Dimech
2020-10-16 10:33 ` Eli Zaretskii
2020-10-16 10:52 ` Christopher Dimech
2020-10-16 10:58 ` Eli Zaretskii [this message]
2020-10-16 11:17 ` Christopher Dimech
2020-10-16 11:23 ` 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=83zh4mv3mh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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.