From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "larsi@gnus.org" <larsi@gnus.org>, "rms@gnu.org" <rms@gnu.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:46:17 +0000 [thread overview]
Message-ID: <SA2PR10MB4474BA018FA2949587644039F3BA9@SA2PR10MB4474.namprd10.prod.outlook.com> (raw)
In-Reply-To: <831re5ytb4.fsf@gnu.org>
> > > 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).
>
> Maybe your Info manuals are (severely) outdated.
> This text is there as far back as Emacs 23.
I confirmed that the text is there. And I
reiterated that the enhancement request is
about a missing link, not missing text.
> Nothing is ever good enough, sigh.
Please don't take it personally. There's
always room for improvement, yes.
I'm a writer, and every writer knows that
it's very easy to write something that can
be misunderstood, and that nearly everything
is ripe for a possible rewrite.
That added suggestion about "This manual"
is a nit - not important. It's not what
this enhancement request is about. I wrote
"BTW," and separated that minor suggestion
from the other text.
The enhancement request is just to add a
link to the Eintr manual from the Elisp
manual, preferably up front somewhere, e.g.
in the Introduction.
next prev parent reply other threads:[~2021-01-28 15:46 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
2021-01-28 15:28 ` Eli Zaretskii
2021-01-28 15:46 ` Drew Adams [this message]
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
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=SA2PR10MB4474BA018FA2949587644039F3BA9@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 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).