From: Kyle Meyer <kyle@kyleam.com>
To: Tassilo Neubauer <tassilo.neubauer@gmail.com>
Cc: 50218@debbugs.gnu.org
Subject: bug#50218: 28.0.50; org-babel-tangle-file tangles code blocks starting with #+begin_src :tangle no
Date: Sat, 18 Dec 2021 17:16:50 -0500 [thread overview]
Message-ID: <875yrla78t.fsf@kyleam.com> (raw)
In-Reply-To: <9d143449-d2db-179b-24da-b4e4d6a33319@gmail.com>
Tassilo Neubauer writes:
> Hello,
>
> Here are the steps that led to code blocks being tangled I did not
> expect to:
>
> emacs -Q
> C-x C-h: ~/org-roam/example.org
> content of example.org (excluding "):
> "
> #+begin_src emacs-lisp
> (setq some-emacs-lisp-variable t)
> #+end_src
>
> #+begin_src :tangle no
> ;;This line should not be in the elisp code
> #+end_src
> "
(Sorry for the delayed reply. This message, unlike the initial post,
will be redirected to the Org list, where you're more likely to get a
response.)
Org sees the last block above as a source block of language ":tangle".
Here's what org-element-at-point reports:
(src-block (:language ":tangle" :switches nil :parameters "yes"...)
org-lint will complain about this block:
2 nil Missing colon in header argument "yes"
And, were you to use a bare source block (i.e. drop ":tangle no"), it
would complain about a missing language:
2 nil Missing language in source block
So, I think the source block is mis-specified, and I'm not sure there's
much that Org should do here, but perhaps others will chime in with
their thoughts.
next parent reply other threads:[~2021-12-18 22:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9d143449-d2db-179b-24da-b4e4d6a33319@gmail.com>
2021-12-18 22:16 ` Kyle Meyer [this message]
2022-10-17 12:24 ` bug#50218: 28.0.50; org-babel-tangle-file tangles code blocks starting with #+begin_src :tangle no Ihor Radchenko
2024-01-29 15:16 ` 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=875yrla78t.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=50218@debbugs.gnu.org \
--cc=tassilo.neubauer@gmail.com \
/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).