From: Eli Zaretskii <eliz@is.elta.co.il>
Cc: emacs-devel@gnu.org
Subject: Re: Error in emacs/emacs/lispintro/emacs-lisp-intro.texi
Date: Thu, 5 Sep 2002 17:13:39 +0200 (IST) [thread overview]
Message-ID: <Pine.SUN.3.91.1020905171046.18455E-100000@is> (raw)
In-Reply-To: <BADF3C947A1BD54FBA75C70C241B0B9E10AAC7@ex02.idirect.net>
On Thu, 5 Sep 2002, Harig, Mark A. wrote:
> (Would you prefer that this type of bug-report be sent
> to 'bug-gnu-emacs@gnu.org'?)
Since this is about the CVS version of Emacs, bug reports should be sent
to emacs-pretest-bug@gnu.org. ("M-x report-emacs-bug RET" will do that
automatically for you.)
> http://savannah.gnu.org/cgi-bin/viewcvs/emacs/emacs/lispintro/emacs-lisp
> -intro.texi
>
> emacs-lisp-intro.texi, revision 1.17 has the following at line 3:
>
> @setfilename ../info/eintr
>
> This causes the generated emacs-lisp-intro.info file to contain the
> lines:
>
> * Emacs Lisp Intro: (eintr).
> A simple introduction to Emacs Lisp programming.
>
> This appears to be an error. Because the .info file is named
> 'emacs-lisp-intro', it should not reference the file 'eintr'
> in the Info 'dir' file. Instead, the '@setfilename' line should
> refer to 'emacs-lisp-intro'.
No, this is not a bug. I'm guessing that you invoked makeinfo manually
to produce the Info output, and used the --output option to tell makeinfo
the name of the output file. In the Emacs sources, lispintro/Makefile.in
takes care of putting the output into info/eintr, so that the menu item
in the top-level DIR menu works.
next prev parent reply other threads:[~2002-09-05 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-05 14:50 Error in emacs/emacs/lispintro/emacs-lisp-intro.texi Harig, Mark A.
2002-09-05 15:13 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-05 15:41 Harig, Mark A.
2002-09-05 15:45 ` 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=Pine.SUN.3.91.1020905171046.18455E-100000@is \
--to=eliz@is.elta.co.il \
--cc=emacs-devel@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).