From: Andrea <andrea-dev@hotmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Andrea <andrea-dev@hotmail.com>, emacs-orgmode@gnu.org
Subject: Re: [BUG] org-babel-tangle may fail due to (org-babel-tangle-collect-blocks lang-re tangle-file) [9.6.9 ( @ /home/andrea/.emacs.d/elpa/org-9.6.9/)]
Date: Thu, 12 Oct 2023 16:46:04 +0100 [thread overview]
Message-ID: <AS8P193MB2413C9D7808AADA9D69BC77488D3A@AS8P193MB2413.EURP193.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <878r87dfkv.fsf@localhost>
On Thu 12 Oct 2023 at 15:29, Ihor Radchenko <yantar92@posteo.net> wrote:
>
> I recommend trying to shrink the problematic file to the smallest possible.
> Then, try with emacs -Q. If cannot reproduce, you can use
> https://github.com/Malabarba/elisp-bug-hunter to bisect the config
> quickly.
Thanks Ihor! I found out that there was (likely) an encoding issue on
one of the source block. I had something like:
:PROPERTIES:
:ID: some-id
:END:
#+being_src emacs-lisp
And trying to evaluate (org-babel-get-src-block-info 'no-eval) at the
beginning of the source block was returning nil (as if I were outside of it).
Just adding a newline manually removed the issue, so I guessed there was
some special character there (which is weird, but I cannot be sure of my
copy pasting).
Sorry for the noise and thanks for your suggestions, they were useful in
debugging my issue.
Best,
Andrea
next prev parent reply other threads:[~2023-10-12 15:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 10:33 [BUG] org-babel-tangle may fail due to (org-babel-tangle-collect-blocks lang-re tangle-file) [9.6.9 ( @ /home/andrea/.emacs.d/elpa/org-9.6.9/)] Andrea
2023-10-12 13:04 ` Ihor Radchenko
2023-10-12 14:16 ` Andrea
2023-10-12 14:40 ` Ihor Radchenko
2023-10-12 14:50 ` Andrea
2023-10-12 15:29 ` Ihor Radchenko
2023-10-12 15:46 ` Andrea [this message]
2023-10-13 11:56 ` Ihor Radchenko
2023-11-24 13:38 ` Andrea
2023-12-05 11:28 ` Ihor Radchenko
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=AS8P193MB2413C9D7808AADA9D69BC77488D3A@AS8P193MB2413.EURP193.PROD.OUTLOOK.COM \
--to=andrea-dev@hotmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).