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: Sun, 03 Jun 2018 18:19:07 +0300 [thread overview]
Message-ID: <83o9grdhjo.fsf@gnu.org> (raw)
In-Reply-To: <55844132-EA2F-4D3B-835B-0870743E666D@scratch.space> (message from Van L on Sun, 3 Jun 2018 12:11:48 +1000)
> From: Van L <van@scratch.space>
> Date: Sun, 3 Jun 2018 12:11:48 +1000
> Cc: 31683@debbugs.gnu.org
>
>
> > Eli Zaretskii writes:
> >
> > Which is actually related to the second location you mentioned
>
> Which was the summary section.
Right.
> > In general, this manual is not an introduction chapter for the ELisp
> > manual
>
> The impression given in other discussion about this was the intention for eintr to be close and interwoven with elisp at a level of detail that bends over backwards for a ,non-programmer'.
>
> There are in general two kinds of people.
>
> One digests the elisp. Straight away.
>
> The other prefers eintr at first.
>
> Having tips of the elisp in the eintr is consciousness raising and invites the reader to go far one day.
I'm not saying there should be no cross-references to ELisp -- we
already have quite a few. I'm saying that having a cross-reference in
every place where we could possibly place one is not TRT for this
manual, because it is not a reference manual.
next prev parent reply other threads:[~2018-06-03 15:19 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
2018-06-03 2:11 ` Van L
2018-06-03 15:19 ` Eli Zaretskii [this message]
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=83o9grdhjo.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.