From: Sebastian Miele <sebastian.miele@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Bug: org-babel-expand-noweb-references: FIXEDCASE=nil
Date: Mon, 09 Mar 2020 16:34:00 +0100 [thread overview]
Message-ID: <87o8t5h79z.fsf@gmail.com> (raw)
org-babel-expand-noweb-references in the current master branch ends with:
(replace-regexp-in-string noweb-re (lambda...) body nil t 2)
I.e., the FIXEDCASE argument to replace-regexp-in-string is nil. This
has the effect that in
#+BEGIN_SRC elisp :noweb-ref AA
(ignore)
#+END_SRC
#+BEGIN_SRC elisp :noweb yes
<<AA>>
#+END_SRC
the second block is expanded as "(IGNORE)". That probably is a bug.
FIXEDCASE should be t.
next reply other threads:[~2020-03-09 15:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 15:34 Sebastian Miele [this message]
2020-03-09 22:11 ` Bug: org-babel-expand-noweb-references: FIXEDCASE=nil 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:
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=87o8t5h79z.fsf@gmail.com \
--to=sebastian.miele@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).