Agree.


---Original---
From: &quot;Eli Zaretskii&quot;<eliz@gnu.org&gt;
Date: Fri, Nov 29, 2019 22:14 PM
To: &quot;Stefan Kangas&quot;<stefan@marxist.se&gt;;
Cc: &quot;c4droid&quot;<c4droid@foxmail.com&gt;;&quot;emacs-devel&quot;<emacs-devel@gnu.org&gt;;
Subject: Re: Some ideas with Emacs


&gt; From: Stefan Kangas <stefan@marxist.se&gt;
&gt; Date: Fri, 29 Nov 2019 14:34:44 +0100
&gt; Cc: Anonymous <c4droid@foxmail.com&gt;, Emacs developers <emacs-devel@gnu.org&gt;
&gt; 
&gt; Eli Zaretskii <eliz@gnu.org&gt; writes:
&gt; 
&gt; &gt; I think if we want to have an ELisp tutorial, it should be a separate
&gt; &gt; manual.&nbsp; The current ELisp manual is a reference manual, and written
&gt; &gt; as such.
&gt; 
&gt; I fail to see why a reference manual can&#39;t also include examples.

I was talking about a tutorial, not about examples.

We already have examples in the ELisp manual, although it isn&#39;t
feasible to have an example for each possible use case.&nbsp; We could add
more examples where the description is not self-explanatory enough,
but adding too much of them would be infeasible, I think, due to size
considerations.&nbsp; We will have to consider that on a case by case
basis.

&gt; I&#39;ve had to search the web to understand how to use things before,
&gt; even after having carefully read the relevant parts of the elisp
&gt; manual and the doc string.

A better strategy is to search the Emacs tree, IME.

&gt; To be clear, I&#39;m not suggesting that we should mandate that we should
&gt; include examples.&nbsp; But I&#39;d suggest to optionally add them where it
&gt; makes sense, and possibly then only in the info version of the manual
&gt; (since we lack space in the print edition).

We already have examples where we think it&#39;s useful.