From: Eli Zaretskii <eliz@gnu.org>
To: Van L <van@scratch.space>
Cc: 31683-done@debbugs.gnu.org
Subject: bug#31683: emacs-lisp-intro.texi - opportunity to link eintr to elisp
Date: Sat, 02 Jun 2018 14:36:12 +0300 [thread overview]
Message-ID: <83bmcte7yr.fsf@gnu.org> (raw)
In-Reply-To: <C3639BB5-4767-4873-B990-FA75ED8D65C2@scratch.space> (message from Van L on Sat, 2 Jun 2018 20:39:49 +1000)
> From: Van L <van@scratch.space>
> Date: Sat, 2 Jun 2018 20:39:49 +1000
>
> The footnote at line 2150 *indirectly* links to (elisp) Printed Representation, which details what an expression is.
>
> : 8cda6f8f44b (Glenn Morris 2007-09-06 2150) learn how to read it.@footnote{@code{(quote hello)} is an expansion of
I don't think I agree: the relation to expressions is too far-fetched
here.
> At line 2508 in the summary is an opportunity to *directly* link the mention of expressions to (elisp) Printed Representation.
>
> : 8cda6f8f44b (Glenn Morris 2007-09-06 2508) Lisp programs are made up of expressions, which are lists or single atoms.
Expressions were explained in the previous sub-sections, so I don't
think we need to add a cross-reference here. (In any case, having
cross-references in a Summary is IME bad style, since it means we
failed to describe something in the parts being summarized. A summary
should never say anything that wasn't already said before.)
> (I will re-open this bug number for future opportunities to link eintr, elisp after it is closed.)
Please don't, as each issue should be a separate bug report.
next prev parent reply other threads:[~2018-06-02 11:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-02 10:39 bug#31683: emacs-lisp-intro.texi - opportunity to link eintr to elisp Van L
2018-06-02 11:36 ` Eli Zaretskii [this message]
2018-06-02 13:30 ` Van L
2018-06-02 14:13 ` Eli Zaretskii
2018-06-03 2:11 ` Van L
2018-06-03 15:19 ` Eli Zaretskii
2018-06-04 1:26 ` Van L
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=83bmcte7yr.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=31683-done@debbugs.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.