From: Christopher Dimech <dimech@gmx.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Viewing Links for a info file
Date: Fri, 16 Oct 2020 12:52:21 +0200 [thread overview]
Message-ID: <trinity-a4f6843b-5cc3-498b-84ff-95fb52eee0cc-1602845541335@3c-app-mailcom-bs01> (raw)
In-Reply-To: <837drqwjdm.fsf@gnu.org>
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'
My code goes something like this
\input texinfo
@c %**start of header
@setfilename gungadin-elisp-abbrev.info
@set Volume-1
@set Gela-Version 1.0
@set Emacs-Version 27.0
@set Date October 21, 2020.
@c %**end of header
@menu
* Introduction:: Introduction to Emacs Lisp.
@detailmenu
Subnodes so you can get to them easily in one step:
Introduction
* Modifier-Keys:: Modifier Keys on Lisp Machine Keyboards.
* Key-Mnemonics:: Mnemonics that identify specific keys.
* Composing-KeySeq:: Composing Key Sequences.
* Complete-Kbd:: Complete Key Bindings.
* Docu-KeySeq:: Documentationm of Key Sequences.
* Emacs-Tutorials-Eww:: Emacs Tutorials and View Web Pages with Eww.
* Docu-Function:: Documentation of Functions.
* Intactv-Function:: Interactive Functions.
* UPrefix-Argument:: The Universal Prefix Argument.
* Fnc-ArgSet-PrPfx:: Setting Function Arguments by Prompt or Prefix.
@end detailmenu
@end menu
@ifclear Volume-1
@include 01-gela-intro.texi
@end ifclear
@bye
cat 01-gela-intro.texi
@node Introduction
@chapter Introduction
Looks at what Emacs is.
@node Modifier-Keys
@section Modifier Keys on Lisp Machine Keyboards
Looks at Modifier Keys on Lisp Machine Keyboards.
etc
@node Fnc-ArgSet-PrPfx
@section Setting Function Argument by Prompt and Prefix
Passing arguments to interactive functions
@c end-of-file
Sent: Friday, October 16, 2020 at 12:33 PM
From: "Eli Zaretskii" <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Viewing Links for a info file
> From: Christopher Dimech <dimech@gmx.com>
> Cc: help-gnu-emacs@gnu.org
> Date: Fri, 16 Oct 2020 11:42:15 +0200
>
>
> That's right. It is makeinfo. I have then done
>
> C-u C-h i file
>
> and it works
>
> Is tht how you view the resulting file.info?
Yes.
You should also consider running "install-info file" (from the shell's
prompt) to add its entry to the DIR file.
next prev parent reply other threads:[~2020-10-16 10:52 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 [this message]
2020-10-16 10:58 ` Eli Zaretskii
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
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=trinity-a4f6843b-5cc3-498b-84ff-95fb52eee0cc-1602845541335@3c-app-mailcom-bs01 \
--to=dimech@gmx.com \
--cc=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.
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).