I mean, include one or two examples for tell reader the describe function how to use, that's enough.
Call emacs with -Q -l option to load plugin development options file, it's also a solution. Suppose I have configured the development environment, but do not have to have the configuration to start, without code completion, have a little uncomfortable for me. :)


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


Anonymous <c4droid@foxmail.com&gt; writes:

&gt; First, suggest to add more examples of functions in the tutorial,
&gt; most for Emacs Lisp Reference Manual, which can lower the learning
&gt; threshold.

I think this is a fine idea that would make the manual more useful.
But the elisp manual is also printed on paper, and is from what I
understand already very long.&nbsp; Does it make sense to include examples
in the info manual only?

&gt; Second, in developing the Emacs plugins, create a virtual
&gt; environment, like Python virtualenv, so that we can test the plugin
&gt; in the virtual environment so that we do not need to affect the
&gt; configuration outside the virtual environment. That&#39;s can implement
&gt; plugin development environment and configuration isolation.

I think what you would do is something like &quot;emacs -Q -l myenv.el&quot; and
then set up the load-path, requires, and whatever else you need in
myenv.el.

&gt; Although my suggestion may be a little trivial and even useless. But
&gt; if my suggestions can help beginners like me go further, I think
&gt; it&#39;s worth it.

We very much need to get more people hacking on Emacs.&nbsp; So any
suggestion which could help us achieve that is welcome, I think.

Best regards,
Stefan Kangas