From: edgar@openmail.cc
To: emacs-orgmode@gnu.org
Subject: library of babel ingest interferes with noweb
Date: Thu, 14 Sep 2017 18:58:10 +0000 [thread overview]
Message-ID: <8c60c4046b28d6da0f46e5cce2bf1149@openmail.cc> (raw)
[-- Attachment #1: Type: text/plain, Size: 467 bytes --]
Hello,
It seems that when I have two blocks of code with noweb, and then I do a
babel ingest, I don't get my original result (see attached file).
Is there a reason for this? Is this a bug?
Thanks.
-------------------------------------------------
ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!
[-- Attachment #2: t.org --]
[-- Type: text/plain, Size: 803 bytes --]
;; This buffer is for notes you don't want to save, and for Lisp evaluation.
;; If you want to create a file, visit that file with C-x C-f,
;; then enter the text in that file's own buffer.
* This works
#+NAME: test1
#+BEGIN_SRC bash
a=2
#+END_SRC
#+NAME: test2
#+BEGIN_SRC bash :noweb yes
<<test1>>
#+END_SRC
#+BEGIN_SRC bash :noweb yes
<<test2>>
#+END_SRC
shows in the org-edit-special window
#+BEGIN_EXAMPLE
a=2
#+END_EXAMPLE
* This does not work
After loading this block,
#+BEGIN_SRC emacs-lisp :exports none :results none
(org-babel-lob-ingest "t.org")
#+END_SRC
#+BEGIN_SRC bash :noweb yes
<<test2>>
#+END_SRC
shows in the org-edit-special window
#+BEGIN_EXAMPLE
<<test1>>
#+END_EXAMPLE
* What I expect
After ingesting the file, I should still get =a=2= in the org-edit-special
next reply other threads:[~2017-09-14 18:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 18:58 edgar [this message]
2017-09-14 21:26 ` library of babel ingest interferes with noweb Nicolas Goaziou
[not found] ` <c43e45990e37b8cc86c605c1a989173e@openmail.cc>
2017-09-16 4:29 ` edgar
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=8c60c4046b28d6da0f46e5cce2bf1149@openmail.cc \
--to=edgar@openmail.cc \
--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).