Re: Emacs development...

[Jean-Christophe Helary <lists@traduction-libre.org>]

Eli, apologies for the very general aspect of my question.

In the first version of this mail I was mentioning that my understanding of the development environment was not sufficient and made the study of the package.el code difficult.

Right now, I use C-h f to find the function definitions and move around the code.

But when I run package.el to test it, I'd like to have a way to examine the values of variables as they evolve. Right now I use message and check the *Messages* buffer... It is not ideal.

And there are probably a few other things that would make work easier but that I am not aware of because I am not a developer.

Jean-Christophe 

> On Aug 21, 2021, at 15:46, Eli Zaretskii <eliz@gnu.org> wrote:
> 
>> From: Jean-Christophe Helary <lists@traduction-libre.org>
>> Date: Sat, 21 Aug 2021 14:07:59 +0900
>> 
>> It just occurred to me that there was no section in the manual dedicated to developing for emacs proper.
> 
> The ELisp Intro and the ELisp Reference are supposed to be it.
> 
>> Something like what the elisp intro is, but for general development.
> 
> What is the difference between "general development" and the other
> kind (which presumably is covered in the Introduction)?
> 
>> For ex. is there a way to see the values of variables as I run the code, so that I don't need to modify the values of "message" here and there to have clues ?
> 
> See the chapter "Practicing Evaluation" in the ELisp Intro and
> "Evaluation" in the ELisp Reference.
> 
>> What are the things I need to know and the basic steps to have a proper working environment to develop for emacs?
> 
> There are too many of them to answer such a general question.  It also
> depends on your style of development.

-- 
Jean-Christophe Helary @brandelune
https://mac4translators.blogspot.com
https://sr.ht/~brandelune/omegat-as-a-book/