unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: van@scratch.space, 31655-done@debbugs.gnu.org
Subject: bug#31655: no obvious link to the Lisp Reference Manual
Date: Wed, 15 Jan 2020 02:43:33 +0100	[thread overview]
Message-ID: <87h80xh4u2.fsf@marxist.se> (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:

>> >>   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.
>
> 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 had another look at this with fresh eyes, and I think I agree that
there is no need for further links on this page:

    https://www.gnu.org/manual/manual.html

That page seems to be about enumerating different pieces of GNU
software and linking their manuals.  It makes no sense to have two
entries for Emacs in that particular list.

I'm therefore closing this bug report.  If anyone disagrees with that,
feel free to reopen (or just reply to this email) and suggest a
different course of action.

Best regards,
Stefan Kangas





      parent reply	other threads:[~2020-01-15  1:43 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
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 [this message]

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=87h80xh4u2.fsf@marxist.se \
    --to=stefan@marxist.se \
    --cc=31655-done@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 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).