[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: blink-cursor-end sometimes fails and disrupts pre-command-hook

From: David Kastrup
Subject: Re: blink-cursor-end sometimes fails and disrupts pre-command-hook
Date: Mon, 21 Aug 2006 09:15:23 +0200
User-agent: Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux)

"Ken Manheimer" <address@hidden> writes:

> On 8/20/06, Richard Stallman <address@hidden> wrote:
>>     i would really, really, *really* have liked to backtraces to help
>>     track this down, but emacs backtraces are useless for that by design.
>>     you have to know where to put them to get the backtrace from an error
>>     at that point.
>> I do not understand that sentence.  What do you mean, "put them"?
>> What do you mean by "where"--what is a "place"?
> "put them" == put the `(backtrace)' call
> "where" == at the point in the code for which you want the backtrace.
> what i want, instead, is the ability to get a stack trace for an error
> when i am handling that error, in a condition-case or in the
> interactive interpreter.

(setq debug-on-signal t)

It's not actually a fun setting, since it catches quite a lot, but it
is useful.

David Kastrup, Kriemhildstr. 15, 44793 Bochum

reply via email to

[Prev in Thread] Current Thread [Next in Thread]