From: VanL <van@scratch.space>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Kangas <stefan@marxist.se>, 31655@debbugs.gnu.org
Subject: bug#31655: no obvious link to the Lisp Reference Manual
Date: Sat, 30 Nov 2019 19:48:17 +1100 [thread overview]
Message-ID: <m2a78doilq.fsf@vogel.localnet> (raw)
In-Reply-To: <83mucdomyp.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 30 Nov 2019 09:14:06 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> My point was that there is such a link already there. Search for
> "elisp", and you will find it. The OP searched for "lisp ref" for
> some reason, and that substring is not present on the page.
> Personally, I don't understand the motivation behind that search
> string, but that's me.
I don't recall the context when I spotted what I thought at the time
was a bug worth pursuing. Generally, when typing in a text box for a
search engine, I expect to see word and phrase completion. I
might've been after in full 'lisp reference manual' and expected that
to be the expansion from 'lisp ref'. Not being familiar with the
word 'elisp', at that time, there would've been zero chance of typing
that in. Yes, you want lots of search terms people use when what
they really want to find is elisp; and allow for missed spellings, etc.
--
LoL,
əə0@ 一 二 三 言 語 𝔖
'VLIW architecture?'
G4 White 78 Black 79
next prev parent reply other threads:[~2019-11-30 8:48 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
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 [this message]
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=m2a78doilq.fsf@vogel.localnet \
--to=van@scratch.space \
--cc=31655@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=stefan@marxist.se \
/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).