GNU bug report logs - #54550
Debugging elisp files

Previous Next

Full log

Message #11 received at 54550 <at> debbugs.gnu.org (full text, mbox):

From: goncholden <goncholden <at> protonmail.com>
To: Robert Pluim <rpluim <at> gmail.com>
Cc: 54550 <at> debbugs.gnu.org
Subject: Re: bug#54550: Debugging elisp files
Date: Fri, 25 Mar 2022 08:38:31 +0000

Sent with ProtonMail secure email.

------- Original Message -------

On Friday, March 25th, 2022 at 8:30 PM, Robert Pluim <rpluim <at> gmail.com> wrote:

> > > > > > On Thu, 24 Mar 2022 18:19:13 +0000, goncholden via "Bug reports for GNU Emacs, the Swiss army knife of text editors" bug-gnu-emacs <at> gnu.org said:
>
> >> I am debugging a large file because of the following error,
>
> >> Warning (initialization): An error occurred while loading ‘/home/goncho/.emacs’:
> >> Invalid read syntax: )
>
> One way to work with this is to put point at the beginning of .emacs
> and eval
>
> (while t (forward-sexp))
>
> That will error and tell you at what character position itʼs failing.

> >> In texinfo, there exists the "@ignore" and "@end ignore" tags that
> >> comment out sections of texinfo code. This makes it much easier to
> >> debug texinfo files, because one does not have to constantly comment
> >> every line, and with the advantage that one can leave the file almost
> >> intact.

> You can wrap blocks of code in (when nil) to achieve the same.
> Robert

I cannot say that the "(when nil)" can include a chunk of defuns though,
only sections within a function.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.