emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: D Bro <dabroyoh@gmail.com>
To: "Charles C. Berry" <ccberry@ucsd.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: :noweb-ref property inheritance failure?
Date: Tue, 18 Apr 2017 21:47:00 -0500	[thread overview]
Message-ID: <36A52436-D544-4991-BB73-496879AABBED@gmail.com> (raw)
In-Reply-To: <alpine.OSX.2.20.1704181850540.1221@charlessmacbook.attlocal.net>

[-- Attachment #1: Type: text/plain, Size: 2157 bytes --]

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 <ccberry@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


[-- Attachment #2: Type: text/html, Size: 4728 bytes --]

  reply	other threads:[~2017-04-19  2:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 23:44 :noweb-ref property inheritance failure? D Bro
2017-04-19  2:04 ` Charles C. Berry
2017-04-19  2:47   ` D Bro [this message]
2017-04-19  2:53     ` D Bro

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=36A52436-D544-4991-BB73-496879AABBED@gmail.com \
    --to=dabroyoh@gmail.com \
    --cc=ccberry@ucsd.edu \
    --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).