A problem is that `debugger-old-buffer' is not necessarily the same
buffer that was current when `eval-buffer' was called.
Strange, somehow I thought about that issue and concluded that it
would be the current buffer. Now it's clear I was not thinking
straight at the time.
I fixed it ano
Richard M. Stallman wrote:
I have debug-on-error set to t. When I do an eval-buffer and there is an
undefined function:
(this-is-no-fun)
I get the error "Wrong type argument: stringp, nul
Does this fix it? (I installed a more elaborate patch.)
Yes, thanks, I think so. I t
"Richard M. Stallman" <[EMAIL PROTECTED]> writes:
> Does this fix it? (I installed a more elaborate patch.)
Well, it does make the error go away.
A problem is that `debugger-old-buffer' is not necessarily the same
buffer that was current when `eval-buffer' was called.
Example (with the patch)
I have debug-on-error set to t. When I do an eval-buffer and there is an
undefined function:
(this-is-no-fun)
I get the error "Wrong type argument: stringp, nul
Does this fix it? (I installed a more elaborate patch.)
*** debug.el05 Jul 2005 00:45:47 -0400 1.90
---
I have debug-on-error set to t. When I do an eval-buffer and there is an
undefined function:
(this-is-no-fun)
I get the error "Wrong type argument: stringp, nul
If I instead let the region be the whole buffer and to eval-region I get
a traceback with "Symbol's function definition is void: t
