Re: debugging.texi

[Lute Kamstra]

Luc Teirlinck <address@hidden> writes:

> Richard Stallman wrote:
>
>        @var{function-name} in the minibuffer.  If @var{function-name} is
>        ! omitted, @code{nil} or the empty string, it cancels break-on-entry 
> for all
>
>    You need a comment after @code{nil} to eliminate a misreading.  With
>    that change, please install.
>
> I assumed that you meant "comma" instead of "comment" and installed.
> However, at closer look I believe that further changes are needed.
>
> One reason is that the reference to the empty string in the above
> could give the wrong impression that one can specify the name of a
> function as a string.  The patch below reformulates things to make it
> clear that the empty string is a special case, used for internal purposes.

I think the empty string argument is a kludge.  Maybe we should just
not document it and tell people to use a symbol or nil from lisp and
the name of the function or no name (i.e., the empty string)
interactively.  Then we could fix the function in the future by not
letting it accept the empty string as an argument.

I like your patch for the docstring of debug-on-entry and I agree with
you that the docstring of cancel-debug-on-entry should be elaborated.

Lute.