From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, "rms@gnu.org" <rms@gnu.org>
Cc: "larsi@gnus.org" <larsi@gnus.org>,
"46084@debbugs.gnu.org" <46084@debbugs.gnu.org>
Subject: bug#46084: [External] : Re: bug#46084: 26.3; Elisp manual: provide a link to (eintro) up front
Date: Thu, 28 Jan 2021 15:16:09 +0000 [thread overview]
Message-ID: <SA2PR10MB4474EC6D727CEBB568F87052F3BA9@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <834kj1ywqq.fsf@gnu.org>
> > I agree, let's make the link. It costs almost nothing on any
> > dimension, and you're right that it will help some people.
>
> Did anyone look in the ELisp manual before writing about this issue?
Yes, I did.
> Because there is already a link.
Not that I see. At least not in Emacs 26.3
(or 27.1, or the latest 28 MS Windows
snapshot I have).
> The ELisp manual says in its first chapter, "Introduction":
>
> This manual attempts to be a full description of Emacs Lisp. For
> a
> beginner’s introduction to Emacs Lisp, see ‘An Introduction to Emacs
> Lisp Programming’, by Bob Chassell, also published by the Free
> Software
> Foundation. This manual presumes considerable familiarity with the
> use
> of Emacs for editing; see ‘The GNU Emacs Manual’ for this basic
> information.
>
> What else is missing?
A link (as the enhancement request says). Not just
a textual mention of the manual's title, but an Info
link.
___
And while we're at it, please consider adding a link
(a link) to the Emacs manual, as well.
Textual references are great. Linked textual refs
are even better.
___
BTW, "This manual" can be misunderstood in the last
sentence you quoted. We presumably want it to mean,
like the first "This manual" of the paragraph, the
Elisp manual. But immediately following mention of
Eintr, it becomes a bit ambiguous. Better to make
explicit which manual is meant.
next prev parent reply other threads:[~2021-01-28 15:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-24 18:55 bug#46084: 26.3; Elisp manual: provide a link to (eintro) up front Drew Adams
2021-01-27 2:49 ` Lars Ingebrigtsen
2021-01-27 2:58 ` bug#46084: [External] : " Drew Adams
2021-01-28 6:31 ` Richard Stallman
2021-01-28 14:14 ` Eli Zaretskii
2021-01-28 15:16 ` Drew Adams [this message]
2021-01-28 15:28 ` Eli Zaretskii
2021-01-28 15:46 ` Drew Adams
2021-01-29 6:35 ` Richard Stallman
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=SA2PR10MB4474EC6D727CEBB568F87052F3BA9@SA2PR10MB4474.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=46084@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=rms@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.