Mercurial > hg > xemacs-beta

comparison man/lispref/edebug.texi @ 444:576fb035e263 r21-2-37

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r21-2-37
author cvs
date Mon, 13 Aug 2007 11:36:19 +0200
parents 3ecd8885ac67
children
comparison
equal deleted inserted replaced
443:a8296e22da4e 444:576fb035e263
147 sometimes. 147 sometimes.
148 148
149 There is a bug in window updating when there is both a trace buffer 149 There is a bug in window updating when there is both a trace buffer
150 and an evaluation list - the source buffer doesn't get displayed. 150 and an evaluation list - the source buffer doesn't get displayed.
151 151
152 @item 152 @item
153 Killing and reinserting an instrumented definition or parts of 153 Killing and reinserting an instrumented definition or parts of
154 it leaves marks in the buffer which may confuse Edebug later. 154 it leaves marks in the buffer which may confuse Edebug later.
155 155
156 @item 156 @item
157 Design problem: The position of definitions with complex names (e.g. 157 Design problem: The position of definitions with complex names (e.g.
168 168
169 @item 169 @item
170 There are no other known bugs, so if you find any, please let me know. 170 There are no other known bugs, so if you find any, please let me know.
171 There is nothing worse than a buggy debugger! 171 There is nothing worse than a buggy debugger!
172 172
173 @item 173 @item
174 I need to rethink locally binding @code{debug-on-error}, 174 I need to rethink locally binding @code{debug-on-error},
175 @code{debug-on-quit}, and keyboard macro state variables. Should we 175 @code{debug-on-quit}, and keyboard macro state variables. Should we
176 allow the global values to be changed by the user? 176 allow the global values to be changed by the user?
177 177
178 @item 178 @item
206 206
207 @item 207 @item
208 Better integration with standard debug. 208 Better integration with standard debug.
209 209
210 @item 210 @item
211 Use @code{inhibit-quit} while edebugging? 211 Use @code{inhibit-quit} while edebugging?
212 212
213 @item 213 @item
214 Crawl mode would @code{sit-for} 0 or 1 in the outside window configuration 214 Crawl mode would @code{sit-for} 0 or 1 in the outside window configuration
215 between each edebug step. 215 between each edebug step.
216 Maybe it should be a separate option that applies to trace as well. 216 Maybe it should be a separate option that applies to trace as well.