Path: utzoo!attcan!utgpu!utstat!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!husc6!yale!Ram-Ashwin From: Ram-Ashwin@cs.yale.edu (Ashwin Ram) Newsgroups: comp.emacs Subject: Re: Better error handling for .emacs Message-ID: <61618@yale-celray.yale.UUCP> Date: 24 May 89 18:47:26 GMT References: <8458@chinet.chi.il.us> <6930010@hpdtl.HP.COM> <40186@bbn.COM> <61162@yale-celray.yale.UUCP> Sender: root@yale.UUCP Reply-To: Ram-Ashwin@cs.yale.edu (Ashwin Ram) Organization: Computer Science, Yale University, New Haven, CT 06520-2158 Lines: 19 In-reply-to: jcgs@wundt.harlqn.uucp (John Sturdy) In article , jcgs@wundt.harlqn.uucp (John Sturdy) writes: > Ashwin writes: > >> It would be nice if you could always ask for a backtrace after an error > >> occurred. The purpose of "debug-on-error" would then be to have this happen > >> automatically if desired. > Try (setq stack-trace-on-error t) -- but, like debug-on-entry, it does > not work while doing your .emacs! stack-trace-on-error is like debug-on-error in that it automatically gives you a backtrace whenever there is an error, if you've setq'd it to t beforehand. But this (a) can get annoying and (b) does not allow you to debug unanticipated errors. 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. -- Ashwin.