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: "Stefan Kangas"<address@hidden>
Date: Fri, Nov 29, 2019 19:37 PM
To: "Anonymous"<address@hidden>;
Cc: "emacs-devel"<address@hidden>;
Subject: Re: Some ideas with Emacs
Anonymous <address@hidden> writes:
> First, suggest to add more examples of functions in the tutorial, > most for Emacs Lisp Reference Manual, which can lower the learning > 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. Does it make sense to include examples in the info manual only?
> Second, in developing the Emacs plugins, create a virtual > environment, like Python virtualenv, so that we can test the plugin > in the virtual environment so that we do not need to affect the > configuration outside the virtual environment. That's can implement > plugin development environment and configuration isolation.
I think what you would do is something like "emacs -Q -l myenv.el" and then set up the load-path, requires, and whatever else you need in myenv.el.
> Although my suggestion may be a little trivial and even useless. But > if my suggestions can help beginners like me go further, I think > it's worth it.
We very much need to get more people hacking on Emacs. So any suggestion which could help us achieve that is welcome, I think.