* Preventing noweb substitution during export
@ 2017-12-27 22:08 Samuel W. Flint
2017-12-27 22:29 ` Nicolas Goaziou
0 siblings, 1 reply; 6+ messages in thread
From: Samuel W. Flint @ 2017-12-27 22:08 UTC (permalink / raw)
To: Org-Mode
I used to be able to prevent noweb substitution during export by setting
noweb to tangle, now it's only a yes/no option. When was this feature
removed, and what can I do to get it back?
Thanks,
Sam
--
Samuel W. Flint
4096R/266596F4
(9477 D23E 389E 40C5 2F10 DE19 68E5 318E 2665 96F4)
λs.(s s) λs.(s s)
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Preventing noweb substitution during export
2017-12-27 22:08 Preventing noweb substitution during export Samuel W. Flint
@ 2017-12-27 22:29 ` Nicolas Goaziou
2017-12-27 22:50 ` Samuel W. Flint
0 siblings, 1 reply; 6+ messages in thread
From: Nicolas Goaziou @ 2017-12-27 22:29 UTC (permalink / raw)
To: Samuel W. Flint; +Cc: Org-Mode
Hello,
swflint@flintfam.org (Samuel W. Flint) writes:
> I used to be able to prevent noweb substitution during export by setting
> noweb to tangle, now it's only a yes/no option. When was this feature
> removed, and what can I do to get it back?
I don't think that was intended. Would you have an ECM demonstrating the
issue?
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Preventing noweb substitution during export
2017-12-27 22:29 ` Nicolas Goaziou
@ 2017-12-27 22:50 ` Samuel W. Flint
2017-12-28 11:42 ` Nicolas Goaziou
0 siblings, 1 reply; 6+ messages in thread
From: Samuel W. Flint @ 2017-12-27 22:50 UTC (permalink / raw)
To: Nicolas Goaziou; +Cc: Org-Mode
Nicolas, my apologies for sending this twice.
>>>>> Nicolas Goaziou writes:
NG> Hello, swflint@flintfam.org (Samuel W. Flint) writes:
>> I used to be able to prevent noweb substitution during export by
>> setting noweb to tangle, now it's only a yes/no option. When was
>> this feature removed, and what can I do to get it back?
NG> I don't think that was intended. Would you have an ECM
NG> demonstrating the issue?
It didn't get removed, though no-export is now the correct value.
Neither, however, are currently documented in the manual.
NG> Regards,
NG> -- Nicolas Goaziou
And the following should demonstrate how they currently behave:
#+BEGIN_EXAMPLE
#+PROPERTY: :noweb tangle
#+name: a
#+begin_src python
def foo():
print "foo"
#+end_src
#+name: b
#+begin_src python
<<a>>
foo()
#+end_src
#+name: c
#+begin_src python :tangle "test.py"
import bar
<<b>>
#+end_src
#+END_EXAMPLE
The file 'test.py' will contain:
import bar
<<a>>
foo()
If noweb is set to no-export, the <<a>> will be resolved. However, with
tangle, the block is included during export.
HTH,
Sam
--
Samuel W. Flint
4096R/266596F4
(9477 D23E 389E 40C5 2F10 DE19 68E5 318E 2665 96F4)
λs.(s s) λs.(s s)
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: Preventing noweb substitution during export
2017-12-27 22:50 ` Samuel W. Flint
@ 2017-12-28 11:42 ` Nicolas Goaziou
2017-12-28 18:30 ` Thomas S. Dye
0 siblings, 1 reply; 6+ messages in thread
From: Nicolas Goaziou @ 2017-12-28 11:42 UTC (permalink / raw)
To: Samuel W. Flint; +Cc: Org-Mode
Hello,
swflint@flintfam.org (Samuel W. Flint) writes:
> Nicolas, my apologies for sending this twice.
>>>>>> Nicolas Goaziou writes:
>
> NG> Hello, swflint@flintfam.org (Samuel W. Flint) writes:
>
> >> I used to be able to prevent noweb substitution during export by
> >> setting noweb to tangle, now it's only a yes/no option. When was
> >> this feature removed, and what can I do to get it back?
>
> NG> I don't think that was intended. Would you have an ECM
> NG> demonstrating the issue?
>
> It didn't get removed, though no-export is now the correct value.
> Neither, however, are currently documented in the manual.
Patches welcome! Org manual is now an Org file, it should be much more
pleasant to edit. :)
> And the following should demonstrate how they currently behave:
>
> #+BEGIN_EXAMPLE
> #+PROPERTY: :noweb tangle
This should be:
#+property: header-args :noweb tangle
> #+name: a
> #+begin_src python
> def foo():
> print "foo"
> #+end_src
>
> #+name: b
> #+begin_src python
>
>
> <<a>>
>
> foo() #+end_src
>
> #+name: c
> #+begin_src python :tangle "test.py"
>
> import bar
> <<b>>
> #+end_src
> #+END_EXAMPLE
>
> The file 'test.py' will contain:
>
> import bar
> <<a>>
>
> foo()
>
> If noweb is set to no-export, the <<a>> will be resolved. However, with
> tangle, the block is included during export.
I cannot reproduce it. The following document:
--8<---------------cut here---------------start------------->8---
#+PROPERTY: header-args :noweb tangle
#+name: a
#+begin_src python
def foo():
print "foo"
#+end_src
#+name: b
#+begin_src python
<<a>>
foo()
#+end_src
#+name: c
#+begin_src python :tangle "test.py"
import bar
<<b>>
#+end_src
--8<---------------cut here---------------end--------------->8---
becomes
--8<---------------cut here---------------start------------->8---
┌────
│ def foo():
│ print "foo"
└────
┌────
│
│
│ <<a>>
│
│ foo()
└────
┌────
│
│ import bar
│ <<b>>
└────
--8<---------------cut here---------------end--------------->8---
when exported to UTF-8.
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2017-12-28 21:50 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-12-27 22:08 Preventing noweb substitution during export Samuel W. Flint
2017-12-27 22:29 ` Nicolas Goaziou
2017-12-27 22:50 ` Samuel W. Flint
2017-12-28 11:42 ` Nicolas Goaziou
2017-12-28 18:30 ` Thomas S. Dye
2017-12-28 21:50 ` Nicolas Goaziou
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).