unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: goncholden via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: 54550@debbugs.gnu.org
Subject: bug#54550: Debugging elisp files
Date: Fri, 25 Mar 2022 08:38:31 +0000	[thread overview]
Message-ID: <CSihOzsLPO7hvlts2KUbIw-wFevEebUhjqLHYPWXJh_eqpVpjN2q2NsU1_EEeLs25AMO01B1qXkQKx6Yxi-XONkjcFVJ0nlrMsh14tL9SmA=@protonmail.com> (raw)
In-Reply-To: <877d8iwi1h.fsf@gmail.com>



Sent with ProtonMail secure email.

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

On Friday, March 25th, 2022 at 8:30 PM, Robert Pluim <rpluim@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@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.






  reply	other threads:[~2022-03-25  8:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-24 18:19 bug#54550: Debugging elisp files goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25  8:30 ` Robert Pluim
2022-03-25  8:38   ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-03-25  8:51     ` Robert Pluim
2022-03-25 11:47       ` goncholden via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-25 16:22 ` Lars Ingebrigtsen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CSihOzsLPO7hvlts2KUbIw-wFevEebUhjqLHYPWXJh_eqpVpjN2q2NsU1_EEeLs25AMO01B1qXkQKx6Yxi-XONkjcFVJ0nlrMsh14tL9SmA=@protonmail.com' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=54550@debbugs.gnu.org \
    --cc=goncholden@protonmail.com \
    --cc=rpluim@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).