From: Eli Zaretskii <eliz@gnu.org>
To: emacs-devel@gnu.org,
Jean-Christophe Helary
<jean.christophe.helary@traduction-libre.org>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: eintr.texi vs emacs-lisp-intro.texi
Date: Mon, 30 Dec 2019 15:10:53 +0200 [thread overview]
Message-ID: <A0B39EFF-EC0C-4733-B213-B24482D4787D@gnu.org> (raw)
In-Reply-To: <177F1758-4A95-4F86-BCBA-02208D807BA3@traduction-libre.org>
On December 30, 2019 2:42:36 PM GMT+02:00, Jean-Christophe Helary <jean.christophe.helary@traduction-libre.org> wrote:
> The gnu site has this link for the "An Introduction to Programming in
> Emacs Lisp" source download:
>
> https://www.gnu.org/software/emacs/manual/texi/eintr.texi.tar.gz
>
> from
>
> https://www.gnu.org/software/emacs/manual/eintr.html
>
> But the Savannah repository has the following file:
>
> http://git.savannah.gnu.org/cgit/emacs.git/tree/doc/lispintro/emacs-lisp-intro.texi
The tar.gz file offered for download is just the contents of the doc/lispintro directory of the Emacs repository. If you look inside the tarball, you will see the same emacs-lisp-intro.texi file there.
> emacs.texi and ack.texi also still refer to eintr.
The Info file produced from the Introduction is called eintr.info, and cross-references must use the actual name of the Info file. So this is expected and perfectly OK.
> The HTML version of the Emacs manual has a link to "eintr.html" when
> the HTML file created by the "make docs" is emacs-lisp-intro.html
>
>
> It seems to me that there is an issue here...
Which of the above issues did you allude to?
next prev parent reply other threads:[~2019-12-30 13:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-30 12:42 eintr.texi vs emacs-lisp-intro.texi Jean-Christophe Helary
2019-12-30 13:10 ` Eli Zaretskii [this message]
2019-12-30 13:22 ` Jean-Christophe Helary
2019-12-30 15:33 ` Eli Zaretskii
2019-12-30 16:05 ` Jean-Christophe Helary
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=A0B39EFF-EC0C-4733-B213-B24482D4787D@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jean.christophe.helary@traduction-libre.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).