emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: bug processing non emacs-lisp blocks
Date: Thu, 29 Jul 2021 14:13:55 +1000	[thread overview]
Message-ID: <87r1fh3gb1.fsf@gmail.com> (raw)
In-Reply-To: <CAEBXXD_VNau1=TSLAoe4WkeJfuu7FJb7KghpuJafJLp=jEhzJg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1000 bytes --]

dmg <dmg@turingmachine.org> writes:

> org-babel-load-file will try to tangle any source block that contains
> the substring emacs-lisp or elisp in their language.
> For example, the following code block will be tangled:
> #+begin_src emacs-lispDONOT
> (use-package "org-sidebar")
> #+end_src
> the following patch fixes that problem. The Regular expression should
> be more stringent, so it does match exactly the string and not a
> substring.
> I think this is a regression. I used to comment out blocks from my
> .org init files by simply adding a XXX (as in emacs-lispXXXX). In
> current org these blocks are tangled :(

I think your right. The regexp should only match on complete string.

BTW an easy way to comment out code blocks from tangling is to just add :tangle no to the header. This will work better because the code block will still work for editing etc and have correct syntax highlighting etc. 



*Tim Cross*

/For gor sake stop laughing, this is serious!/

  reply	other threads:[~2021-07-29  4:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-29  3:37 bug processing non emacs-lisp blocks dmg
2021-07-29  4:13 ` Tim Cross [this message]
2021-07-29 14:54   ` Maxim Nikulin
2021-08-07 20:24 ` Nicolas Goaziou

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=87r1fh3gb1.fsf@gmail.com \
    --to=theophilusx@gmail.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).