Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!mailrus!csd4.milw.wisc.edu!lll-winken!uunet!mcvax!ukc!icdoc!qmc-cs!harlqn!jcgs From: jcgs@wundt.harlqn.uucp (John Sturdy) Newsgroups: comp.emacs Subject: Re: Better error handling for .emacs Message-ID: Date: 26 May 89 10:31:10 GMT References: <8458@chinet.chi.il.us> <6930010@hpdtl.HP.COM> <40186@bbn.COM> <61162@yale-celray.yale.UUCP> <61618@yale-celray.yale.UUCP> Sender: news@harlqn.UUCP Organization: Harlequin Ltd, Cambridge, England Lines: 15 In-reply-to: Ram-Ashwin@cs.yale.edu's message of 24 May 89 18:47:26 GMT In <61618@yale-celray.yale.UUCP>, Ashwin writes: >> What you want is a way to ask for a backtrace AFTER an error has >> occurred so that you can choose which errors you want to debug >> (rather than have every error put you into the debugger), and so >> that you can debug errors even if you didn't turn on debug-on-error >> or stack-trace-on-error earlier. I agree. How about a flag to control whether the *Backtrace* buffer is popped up on screen? Then you could look at the backtrace if you wanted to, but it wouldn't pester you if you didn't. A combination of that, and of making \C-G not produce a backtrace, would suit me fine. __John (jcgs@uk.co.harlqn) -- __John The Lord bless you and watch over you, The Lord make his face shine upon you and be gracious to you, The Lord look kindly on you and give you peace; My brothers, my sisters, God bless you. Amen. (St. Francis)