From: Eli Zaretskii <eliz@gnu.org>
To: Van L <van@scratch.space>
Cc: 31655@debbugs.gnu.org
Subject: bug#31655: no obvious link to the Lisp Reference Manual
Date: Wed, 30 May 2018 20:08:38 +0300 [thread overview]
Message-ID: <83vab5gjft.fsf@gnu.org> (raw)
In-Reply-To: <A880954D-8A51-4B80-8D22-358BC88FACD6@scratch.space> (message from Van L on Wed, 30 May 2018 20:21:56 +1000)
> From: Van L <van@scratch.space>
> Date: Wed, 30 May 2018 20:21:56 +1000
>
>
> > John Darrington writes:
> >
> > You need to report this to the emacs maintainers.
>
> The page should not say to contact: maintainers@gnu.org
>
> > Van L writes:
> >> Hello.
> >>
> >> From the following locations I am unable to see the link to the Lisp Reference Manual, which is expected close to the Lisp Intro.
> >>
> >> https://www.gnu.org/software/emacs/
> >> https://www.gnu.org/manual/manual.html
I'm not sure I understand the problem. Starting from
https://www.gnu.org/software/emacs/
I can click "Documentation & Support", and I'm then presented with a
list which includes the Emacs Lisp Reference Manual. Clicking on the
"Read On-line" link allows me to read the ELisp manual.
Which one of the above didn't work for you?
next prev parent reply other threads:[~2018-05-30 17:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180528181944.GA32141@gnu.org>
2018-05-30 10:21 ` bug#31655: no obvious link to the Lisp Reference Manual Van L
2018-05-30 17:08 ` Eli Zaretskii [this message]
2018-05-31 2:50 ` Van L
2018-05-31 14:40 ` Eli Zaretskii
2018-06-01 4:29 ` Van L
2018-06-01 7:40 ` Eli Zaretskii
2018-06-01 7:56 ` Van L
2019-11-30 3:57 ` Stefan Kangas
2019-11-30 7:14 ` Eli Zaretskii
2019-11-30 8:48 ` VanL
2019-11-30 10:31 ` Eli Zaretskii
2019-12-01 2:21 ` VanL
2019-12-01 7:45 ` Stefan Kangas
2019-12-01 9:49 ` VanL
2020-01-15 1:43 ` Stefan Kangas
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=83vab5gjft.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31655@debbugs.gnu.org \
--cc=van@scratch.space \
/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).