Many thanks—especially for the quick response.  Unfortunately, no go.

The headline was a copy and paste issue into the email — my org-lint only 
complains about the :classname (I didn’t even know about org-lint, thank you!)
Export to Ascii produces:

… 
1 Create
========

  ,----
  | <<testdemo2>>
  `----


1.1 Let's see what our code-weaving produces
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1.1.1 this is how we will assemble our code:
--------------------------------------------

  ,----
  | public class Yo {
  |   public static void main (Args[]) {
  `----


1.1.2 body
----------

  ,----
  | return "The test worked!";
  `----


1.1.3 foot
----------

  ,----
  | // <<test-foot>>
  | }}
  `----


1.1.4 weave together
--------------------

  - which will weave together the above blocks to produce this:

    ,----
    | cat TestDemo2.java
    `——

Ed

> On Apr 18, 2017, at 9:04 PM, Charles C. Berry <ccbe...@ucsd.edu> wrote:
> 
> On Tue, 18 Apr 2017, D Bro wrote:
> 
>> Both 26.0 and 25.1 on OS X 10.12 via homebrew, using the Spacemacs 
>> configuration.
>> 
> 
>> I recently tried the weaving technique from 
>> http://orgmode.org/manual/noweb_002dref.html#noweb_002dref 
>> <http://orgmode.org/manual/noweb_002dref.html#noweb_002dref> :
> 
> [snip]
> 
> Using M-x org-lint on your example gives
> 
>     3 high  Unknown header argument ":classname"
>    12 high  Incorrect location for PROPERTIES drawer
> 
> The latter is because the drawer is not immediately after a headline and is 
> disregarded:
> 
>> **Let's see what our code-weaving produces
>> :PROPERTIES:
>> :header-args: :noweb-ref testdemo2
>> :END:
> 
> If you put a space between `**' and `L[...]' the line becomes a valid 
> headline. Then the TestDemo2 src block produces
> 
> ,----
>  | public class Yo {
>  | public static void main (Args[]) {
>  | return "The test worked!";
>  | //
>  | }}
>  | cat TestDemo2.java
>  `----
> 
> on ASCII export.
> 
> You can ignore the message about :classname, which comes from ob-java not 
> defining it as a header-arg.
> 
> HTH,
> 
> Chuck

Reply via email to