emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tommy Kelly <tommy.kelly@verilab.com>
To: emacs-orgmode@gnu.org
Subject: BUG? Null character prevents org-babel-tangle from tangling a block
Date: Fri, 11 Nov 2022 18:13:20 -0800	[thread overview]
Message-ID: <CAMg28Ov+fn3uLBb1XTYDnxeNkL1M14edpVnsj6A-cGoPDP=9gg@mail.gmail.com> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 824 bytes --]

I'm starting to figure out tangle by wrapping chunks of my emacs init.el in
#+begin_src/#end_src and then hitting C-c C-v t. It has been working fine,
but one block simply refused to participate. I eventually tracked the
problem down to a stray NULL character that had found its way into some of
the lisp comments in that particular chunk of my init.el. It had the effect
of completely disabling tangling of the entire block. Blocks before and
after that one, however, all tangle nicely.

The attached .org file describes a simple test to demonstrate the problem.
I've also attached a .zip version, in case the NULL character in the test
doesn't survive the gmailing process. (The null is In BLOCK 2, two
characters after the '3' in ';; line3' If it's there, you should see the
usual ^@ (as a single character) placeholder.

[-- Attachment #1.2: Type: text/html, Size: 990 bytes --]

[-- Attachment #2: test-effect-of-null.org --]
[-- Type: application/octet-stream, Size: 947 bytes --]

[-- Attachment #3: test-effect-of-null.org.zip --]
[-- Type: application/zip, Size: 999 bytes --]

             reply	other threads:[~2022-11-12  2:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-12  2:13 Tommy Kelly [this message]
2022-11-12 12:59 ` [BUG] Null character in block/drawer regexps (but not in org-element parser) (was: BUG? Null character prevents org-babel-tangle from tangling a block) Ihor Radchenko
2022-11-12 15:22   ` [BUG] Null character in block/drawer regexps (but not in org-element parser) Bastien Guerry
2023-04-25 19:12     ` 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:

  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='CAMg28Ov+fn3uLBb1XTYDnxeNkL1M14edpVnsj6A-cGoPDP=9gg@mail.gmail.com' \
    --to=tommy.kelly@verilab.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).