all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
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: Thu, 31 May 2018 12:50:54 +1000	[thread overview]
Message-ID: <BE0E6DC4-B1A6-4638-8219-1AA4133F2781@scratch.space> (raw)
In-Reply-To: <83vab5gjft.fsf@gnu.org>


> Eli Zaretskii writes:
> 
>>>> 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/
> 
> Which one of the above didn't work for you?

I found the two links, as above. 

There I located the lisp-intro on an index page but a keyword search for ``lisp reference'’ had nothing which was why I contacted the email mentioned which turned out to be inappropriate to contact. If you’ve located the lisp reference, having it on the same page as the index for lisp intro, in fact, on neighboring lines, will definitely be handy to have, and it would be consistent with how they are arranged on the infopage directory.






  reply	other threads:[~2018-05-31  2:50 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 [this message]
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

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

  git send-email \
    --in-reply-to=BE0E6DC4-B1A6-4638-8219-1AA4133F2781@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 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.