all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Van L <van@scratch.space>
Cc: 31683@debbugs.gnu.org
Subject: bug#31683: emacs-lisp-intro.texi - opportunity to link eintr to elisp
Date: Sat, 02 Jun 2018 17:13:18 +0300	[thread overview]
Message-ID: <838t7xe0ox.fsf@gnu.org> (raw)
In-Reply-To: <BDEB9AB7-3073-47F8-B1A0-C12676C518EF@scratch.space> (message from Van L on Sat, 2 Jun 2018 23:30:35 +1000)

> From: Van L <van@scratch.space>
> Date: Sat, 2 Jun 2018 23:30:35 +1000
> Cc: 31683-done@debbugs.gnu.org
> 
> >> : 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.
> 
> #+BEGIN_EXAMPLE
> 8cda6f8f44b (Glenn Morris             2007-09-06  1151) The printed representation of both atoms and lists are called
> 8cda6f8f44b (Glenn Morris             2007-09-06  1152) @dfn{symbolic expressions} or, more concisely, @dfn{s-expressions}.

Which is actually related to the second location you mentioned, and
seems to explain enough of what an s-expression is to be
self-contained.

In general, this manual is not an introduction chapter for the ELisp
manual, and never wanted to be.  It only includes cross-references to
the ELisp manual where it just mentions some subtlety, but doesn't
describe it.  These two places don't seem like they fit.





  reply	other threads:[~2018-06-02 14:13 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
2018-06-02 13:30   ` Van L
2018-06-02 14:13     ` Eli Zaretskii [this message]
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=838t7xe0ox.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=31683@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.