The problem is in changing [the behavior of] existing
code letters. Emacs allows customization of almost
everything down to redefining built-in core functions,
but disallows customization of default methods for reading
input arguments. This is an artificial restriction
co
But I still like to apply the patch for debug-on-entry as is. Besides
using function-called-at-point, it also filters out special forms
(which can't be set to break on entry). Is that Ok?
Yes.
___
Emacs-devel mailing list
Emacs-devel@gnu.
> There are other commands using `a' letter to read function names (like
> `elp-instrument-function', etc.) where getting the default function name
> from the current buffer would be useful too. So maybe it's better to
> implement this in `call-interactively' for all commands using
"Richard M. Stallman" <[EMAIL PROTECTED]> writes:
> There are other commands using `a' letter to read function names (like
> `elp-instrument-function', etc.) where getting the default function name
> from the current buffer would be useful too. So maybe it's better to
> implement
There are other commands using `a' letter to read function names (like
`elp-instrument-function', etc.) where getting the default function name
from the current buffer would be useful too. So maybe it's better to
implement this in `call-interactively' for all commands using `a'?
T
>> A better way to do this is to change the interactive specification of
>> `debug-on-entry' to call `function-called-at-point'.
>
> How about this?
There are other commands using `a' letter to read function names (like
`elp-instrument-function', etc.) where getting the default function name
from
> For example, a user could define his own version of `b' in `(interactive
> "b...")'. Instead of having to find all occurrences of `(interactive
> "b...")' and replacing each of them with his own `(interactive (list
> (my-read-buffer...)...)...)', he could just redefine what `(inte
Juri Linkov <[EMAIL PROTECTED]> writes:
> A better way to do this is to change the interactive specification of
> `debug-on-entry' to call `function-called-at-point'.
How about this?
Lute.
Index: lisp/emacs-lisp/debug.el
===
RCS f
> However, that would only help with uses of `call-interactively', not
> uses of `interactive' itself.
I don't understand what you mean. `interactive' is just a
specification.
`call-interactively' interprets it.
Sorry; I see that now. I didn't realize it when I wrote tha
> However, that would only help with uses of `call-interactively', not
> uses of `interactive' itself.
I don't understand what you mean. `interactive' is just a specification.
`call-interactively' interprets it.
> It's probably not feasible (and I foresee immediate dismissal of the idea,
> regar
For post-release: it would be good to rewrite the function
`call-interactively' in Lisp which will allow easy modification of
reading arguments according to code letters (e.g. in this particular
case adding a call to `function-called-at-point' for the code letter `a').
I think that
> change the interactive specification of
> `debug-on-entry' to call `function-called-at-point'.
>
> Yes. I've suggested this previously. When debugging, you are often
> in an Emacs-Lisp buffer, and this is useful.
_If_ you are in an Emacs-Lisp buffer and consequent
"Drew Adams" <[EMAIL PROTECTED]> writes:
> change the interactive specification of
> `debug-on-entry' to call `function-called-at-point'.
>
> Yes. I've suggested this previously. When debugging, you are often
> in an Emacs-Lisp buffer, and this is useful.
_If_ you are in an Emacs-Lisp buf
change the interactive specification of
`debug-on-entry' to call `function-called-at-point'.
Yes. I've suggested this previously. When debugging, you are often in an
Emacs-Lisp buffer, and this is useful.
For post-release: it would be good to rewrite the function
`call-interactive
> Is there an existing function which performs the following?
>
> (defun debug-on-entry-at-point ()
> "Perform \\[debug-on-entry] on the function at point."
> (let ((fn (function-called-at-point)))
> (if fn
> (debug-on-entry fn)
> (message "No function at point"
A better wa
Excellent, thank you.
--
"Cut your own wood and it will warm you twice"
Regards, Yoni Rabkin Katzenell
___
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel
Yoni Rabkin Katzenell <[EMAIL PROTECTED]> writes:
> Is there an existing function which performs the following?
>
> (defun debug-on-entry-at-point ()
> "Perform \\[debug-on-entry] on the function at point."
> (let ((fn (function-called-at-point)))
> (if fn
> (debug-on-entry fn)
>
17 matches
Mail list logo
