Re: Help debugging a backtrace

[Jude DaShiell]

Thanks much, this is a huge help.  I didn't know exactly how to read 
back traces so ought to be able to fix things more effectively in 
future.

On Wed, 21 Sep 2016, Kaushal Modi wrote:

> Date: Wed, 21 Sep 2016 13:12:22
> From: Kaushal Modi <kaushal.modi@gmail.com>
> To: Jude DaShiell <jdashiel@panix.com>, rn3aoh.g@gmail.com,
>     help-gnu-emacs@gnu.org
> Subject: Re: Help debugging a backtrace
>
> On Tue, Sep 20, 2016 at 9:53 PM Jude DaShiell <jdashiel@panix.com> wrote:
>
> > Is it possible with a debug situation where a .emacs has to be debugged
> > to run emacs --debug then key in some command that has emacs tell you
> > what the first line is that has the error?
>
> I am not sure what you mean by that.
>
> When you run emacs --debug-init, it will show you an elisp backtrace of the
> first error in your emacs config. If your config has no error, you will see
> emacs start as usual. The backtrace will lead to the first line causing
> that error.
>
> Once your emacs session has started, and you want a backtrace on any error
> that occurs later on in the session, do M-x toggle-debug-on-error. Then you
> will get a backtrace on any error (even the harmless ones).

--