From: "numbchild@gmail.com" <numbchild@gmail.com>
To: Grant Rettke <gcr@wisdomandwonder.com>
Cc: Org-mode <emacs-orgmode@gnu.org>
Subject: Re: babel header argument :var is not expanded when tangling
Date: Mon, 25 Dec 2017 20:45:58 +0800 [thread overview]
Message-ID: <CAL1eYuJmZvgeGzZsN3ijtfLaDXNzpSp_XA5yuaCp91rvCTautQ@mail.gmail.com> (raw)
In-Reply-To: <CAAjq1mdQ3DnThGrUDKexe3GvQ76pVnQBQS1jptT2oVFzYGBPXw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2265 bytes --]
I see. I will use noweb style for now.
But should tangle expand :var variables when tangling? I think this is the
correct behaviour.
[stardiviner] <Hack this world!> GPG key ID: 47C32433
IRC(freeenode): stardiviner Twitter: @numbchild
Key fingerprint = 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433
Blog: http://stardiviner.github.io/
On Sun, Dec 24, 2017 at 11:40 PM, Grant Rettke <gcr@wisdomandwonder.com>
wrote:
> > Here is a quick test:
> >
> > * Test tangle will auto expand and substitute :var
> >
> > #+begin_src js :tangle kk.js
> > console.log("hello, world!");
> > #+end_src
> >
> > #+begin_src js :var name="chris" :tangle require-kk.js
> > // require("kk.js");
> > console.log("Hi, ", name);
> > #+end_src
> >
> > #+RESULTS:
> > : Hi, chris
> >
> > #+NAME: check whether tangle expand and substitute :var
> > #+begin_src shell
> > cat require-kk.js
> > #+end_src
> >
> > #+RESULTS: check whether tangle expand and substitute :var
> > : var name="chris";
> > : console.log("Hi, ", name);
> >
> > The upper result should be: ~console.log("Hi, ", "chris");~.
>
> Here are your two source blocks. They each do literate programming,
> one with Variable style and the other with Noweb style. When you
> evaluate them you get an identical result. When you tangle them you
> get two different pieces of code, that generate the same result. You
> can peek at what the tangled code will look like by calling
> org-babel-expand-src-block inside the source block. That is how it
> will look in the tangled file. I think that want Noweb style.
>
> When I use the Variable approach like this
>
> #+begin_src js :var name="chris" :tangle kk.js
> console.log("Hi, ", name);
> #+end_src
>
> I get this in the tangled output file
>
> var name="chris";
> console.log("Hi, ", name);
>
> When I use the the Noweb approach like this
>
> #+NAME: name
> #+BEGIN_SRC emacs-lisp
> chris
> #+END_SRC
>
> #+NAME: org_gcr_2017-12-23_mara_3D887FDD-163D-4BE1-80E8-464BF29DABEA
> #+BEGIN_SRC js :tangle noweb-kk.js :comments no
> console.log("Hi, ", "«name»");
> #+END_SRC
>
> I get this in the tangled output file
>
> console.log("Hi, ", "chris");
>
> WDYT?
>
[-- Attachment #2: Type: text/html, Size: 3358 bytes --]
next prev parent reply other threads:[~2017-12-25 12:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-24 3:16 babel header argument :var is not expanded when tangling numbchild
2017-12-24 15:40 ` Grant Rettke
2017-12-25 12:45 ` numbchild [this message]
2017-12-28 1:20 ` Grant Rettke
2017-12-28 13:43 ` [SOLVED] " stardiviner
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=CAL1eYuJmZvgeGzZsN3ijtfLaDXNzpSp_XA5yuaCp91rvCTautQ@mail.gmail.com \
--to=numbchild@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=gcr@wisdomandwonder.com \
/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).