From: Ihor Radchenko <yantar92@posteo.net>
To: "Fraga, Eric" <e.fraga@ucl.ac.uk>
Cc: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: error tangling: how to debug please?
Date: Thu, 14 Sep 2023 12:40:04 +0000 [thread overview]
Message-ID: <87sf7hapy3.fsf@localhost> (raw)
In-Reply-To: <87bke50wh2.fsf@ucl.ac.uk>
"Fraga, Eric" <e.fraga@ucl.ac.uk> writes:
> I have a rather large & complex file which has many src blocks, all of
> which tangle to a single file, defined by a header-args property.
>
> When I try to tangle, I get the following (not very informative
> unfortunately) backtrace:
>
> Debugger entered--Lisp error: (wrong-type-argument stringp nil)
> org-src-coderef-regexp(nil)
> org-babel-tangle-single-block(1)
> ...
> I haven't tried emacs -Q or similar as there are too many things to set
> up for this complex file. I am just looking for any hints or
> suggestions that could help me debug this.
Looks like `org-src-coderef-format' returns something weird for one of
the code blocks.
To debug, you can try to patch `org-babel-tangle-single-block', catching
when `org-src-coderef-regexp' is called with nil argument (it must be a
string). Then, examine which source block you are at when that happens.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2023-09-14 12:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 12:29 error tangling: how to debug please? Fraga, Eric
2023-09-14 12:40 ` Ihor Radchenko [this message]
2023-09-14 12:51 ` Fraga, Eric
2023-09-14 12:59 ` Ihor Radchenko
2023-09-14 13:00 ` Fraga, Eric
2023-09-14 14:12 ` Fraga, Eric
2023-09-15 9:16 ` Ihor Radchenko
2023-09-15 10:45 ` Fraga, Eric
2023-09-15 14:41 ` Max Nikulin
2023-09-15 15:42 ` Fraga, Eric
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sf7hapy3.fsf@localhost \
--to=yantar92@posteo.net \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
/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/org-mode.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).