From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Theodor Thornhill <theo@thornhill.no>,
61155@debbugs.gnu.org, jpff@codemist.co.uk
Subject: bug#61155: 29.0.60; build failures tree sitter
Date: Mon, 30 Jan 2023 15:42:03 +0100 [thread overview]
Message-ID: <878rhkxex0.fsf@gmail.com> (raw)
In-Reply-To: <83wn543xzd.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 30 Jan 2023 16:20:38 +0200")
>>>>> On Mon, 30 Jan 2023 16:20:38 +0200, Eli Zaretskii <eliz@gnu.org> said:
Eli> OK, thanks.
Eli> Btw, it was a bitch finding which code caused the error message. It
Eli> is easy to forget that the :set functions of defcustom's are called
Eli> during startup, and the line number shown with the message didn't
Eli> identify the defcustom, just the file name. I eventually found this
Eli> was the culprit by running the byte-compilation command under GDB...
The line number pointed at
(require 'treesit)
so I just took a 'emacs -Q', did M-x toggle-debug-on-error, and C-x
C-e, and got dumped at the right location
Robert
--
next prev parent reply other threads:[~2023-01-30 14:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 21:00 bug#61155: 29.0.60; build failures tree sitter John
2023-01-30 9:36 ` Robert Pluim
2023-01-30 11:10 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-30 11:40 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-30 13:17 ` Eli Zaretskii
2023-01-30 13:22 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-30 14:20 ` Eli Zaretskii
2023-01-30 14:32 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-30 14:42 ` Robert Pluim [this message]
2023-01-30 15:00 ` Eli Zaretskii
2023-01-30 12:36 ` Eli Zaretskii
2023-01-30 13:24 ` Robert Pluim
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rhkxex0.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=61155@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jpff@codemist.co.uk \
--cc=theo@thornhill.no \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.