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: Fri, 24 Nov 2023 13:38:17 +0000 [thread overview]
Message-ID: <DU2P193MB24228C1F84EA5CE58EE126F088B8A@DU2P193MB2422.EURP193.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87edhy3fcm.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 168 bytes --]
Sorry Ihor for the long delay.
I got the error again for the second source block in the attached file.
That is a sample of my configuration.
Hope this helps,
Andrea
[-- Attachment #2: example.org --]
[-- Type: application/vnd.lotus-organizer, Size: 864 bytes --]
[-- Attachment #3: Type: text/plain, Size: 633 bytes --]
On Fri 13 Oct 2023 at 11:56, Ihor Radchenko <yantar92@posteo.net> wrote:
> Andrea <andrea-dev@hotmail.com> writes:
>
>> 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).
>
> This should not happen. It would be nice if you can share a file with
> problematic encoding, so that I could check if we have an edge case
> with Org parser.
next prev parent reply other threads:[~2023-11-24 13:48 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
2023-10-13 11:56 ` Ihor Radchenko
2023-11-24 13:38 ` Andrea [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DU2P193MB24228C1F84EA5CE58EE126F088B8A@DU2P193MB2422.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 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.