Re: [O] Preventing noweb substitution during export

2017-12-28 Thread Nicolas Goaziou 
Hello,

"Thomas S. Dye"  writes:

> Good news. When will the switch from doc/org.texi to
> contrib/manual.org take place?

I don't know. I was only anticipating the ineluctable ;)

Regards,

-- 
Nicolas Goaziou

Re: [O] Preventing noweb substitution during export

2017-12-28 Thread Thomas S. Dye 


Patches welcome! Org manual is now an Org file, it should be 
much more

pleasant to edit. :)


Good news. When will the switch from doc/org.texi to 
contrib/manual.org take place?


All the best,
Tom

--
Thomas S. Dye
http://www.tsdye.com

Re: [O] Preventing noweb substitution during export

2017-12-28 Thread Nicolas Goaziou 
Hello,

swfl...@flintfam.org (Samuel W. Flint) writes:

> Nicolas, my apologies for sending this twice.
>> Nicolas Goaziou writes:
>
> NG> Hello, swfl...@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
>
>
>   <>
>
>   foo() #+end_src
>
> #+name: c
> #+begin_src python :tangle "test.py"
>
>   import bar
>   <>
> #+end_src
> #+END_EXAMPLE
>
> The file 'test.py' will contain:
>
> import bar
> <>
>
> foo()
>
> If noweb is set to no-export, the <> 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


  <>

  foo()
 #+end_src

#+name: c
#+begin_src python :tangle "test.py"

  import bar
  <>
#+end_src
--8<---cut here---end--->8---

becomes

--8<---cut here---start->8---
┌
│ def foo():
│ print "foo"
└

┌
│ 
│ 
│ <>
│ 
│ foo()
└

┌
│ 
│ import bar
│ <>
└
--8<---cut here---end--->8---

when exported to UTF-8.

Regards,

-- 
Nicolas Goaziou

Re: [O] Preventing noweb substitution during export

2017-12-27 Thread Samuel W. Flint 
Nicolas, my apologies for sending this twice.
> Nicolas Goaziou writes:

NG> Hello, swfl...@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

  <>

  foo()
#+end_src

#+name: c
#+begin_src python :tangle "test.py"

  import bar
  <>
#+end_src
#+END_EXAMPLE

The file 'test.py' will contain:

import bar
<>

foo()

If noweb is set to no-export, the <> 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)

Re: [O] Preventing noweb substitution during export

2017-12-27 Thread Nicolas Goaziou 
Hello,

swfl...@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

[O] Preventing noweb substitution during export

2017-12-27 Thread Samuel W. Flint 
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)