From: Van L <van@scratch.space>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 31655@debbugs.gnu.org
Subject: bug#31655: no obvious link to the Lisp Reference Manual
Date: Fri, 1 Jun 2018 14:29:06 +1000 [thread overview]
Message-ID: <42350A8B-7E9E-4993-BA4F-A8AD008453AB@scratch.space> (raw)
In-Reply-To: <83lgbzhoqy.fsf@gnu.org>
> Eli Zaretskii writes:
>
> Sorry, I'm afraid I'm still not following. What is the "index page"
> which you mention? And what is "keyword search" in this case, and how
> did you perform it?
The index page has a list of all the published manuals except the lisp reference. (I bug reported two links, one of them is it.)
The keyword search is the function in the web browser for finding a sequence of characters on the presented webpage. (Command-F does it on the web browser in front of me.)
On the following page,
https://www.gnu.org/manual/manual.html
Command-F followed by ,lisp ref, results in
Phrase not found
next prev parent reply other threads:[~2018-06-01 4:29 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
2018-05-31 2:50 ` Van L
2018-05-31 14:40 ` Eli Zaretskii
2018-06-01 4:29 ` Van L [this message]
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=42350A8B-7E9E-4993-BA4F-A8AD008453AB@scratch.space \
--to=van@scratch.space \
--cc=31655@debbugs.gnu.org \
--cc=eliz@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).