all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Van L <van@scratch.space>, 31655@debbugs.gnu.org
Subject: bug#31655: no obvious link to the Lisp Reference Manual
Date: Sat, 30 Nov 2019 04:57:31 +0100	[thread overview]
Message-ID: <87tv6mhv84.fsf@marxist.se> (raw)
In-Reply-To: <831sdrgdj1.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 01 Jun 2018 10:40:50 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Van L <van@scratch.space>
>> Date: Fri, 1 Jun 2018 14:29:06 +1000
>> Cc: 31655@debbugs.gnu.org
>> 
>> On the following page,
>> 
>>   https://www.gnu.org/manual/manual.html
>> 
>> Command-F followed by ,lisp ref, results in 
>> 
>>   Phrase not found
>
> Try "elisp" instead, and Bob's your uncle.

The request here is to have a separate link to the Emacs Lisp
Reference Manual from that page.  I think that request makes sense; in
any case it definitely can't hurt.

Does anyone else have an opinion here?  Otherwise, I'll go ahead and
contact webmasters@gnu.org to see if they can help add that.

Best regards,
Stefan Kangas





  parent reply	other threads:[~2019-11-30  3:57 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87tv6mhv84.fsf@marxist.se \
    --to=stefan@marxist.se \
    --cc=31655@debbugs.gnu.org \
    --cc=eliz@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 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.