[ < ] | [ > ] | [ << ] | [Plus haut] | [ >> ] | [Top] | [Table des matières] | [Index] | [ ? ] |
There are three ways to investigate a problem in an Emacs Lisp program, depending on what you are doing with the program when the problem appears.
18.1 The Lisp Debugger | How the Emacs Lisp debugger is implemented. | |
18.2 Edebug | A source-level Emacs Lisp debugger. | |
18.3 Debugging Invalid Lisp Syntax | How to find syntax errors. | |
18.4 Test Coverage | Ensuring you have tested all branches in your code. | |
18.5 Debugging Problems in Compilation | How to find errors that show up in byte compilation. |
Another useful debugging tool is the dribble file. When a dribble file is open, Emacs copies all keyboard input characters to that file. Afterward, you can examine the file to find out what input was used. Voir la section Terminal Input.
For debugging problems in terminal descriptions, the open-termscript
function can be useful. Voir la section Terminal Output.
Ce document a été généré par Eric Reinbold le 13 Octobre 2007 en utilisant texi2html 1.78.