From: David Rogoff <david@therogoffs.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: macro replacement in code block?
Date: Wed, 1 Nov 2017 10:32:14 -0700 [thread overview]
Message-ID: <95C792B0-79AC-4F65-B07B-F7787D25352D@therogoffs.com> (raw)
In-Reply-To: <CAFyQvY1Lx2wFjbz4K_ASpru07=R4ZGfLzUyFkv8T20ONizEdEg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2125 bytes --]
Thanks so much. It sort of works but with a bit of work-around:
1) tangle works fine
2) for export, I had to move the
> ,#+MACRO: SEC_FOO
lines out of the code block. If I didn’t and tried to eval that block, I got the error
No org-babel-execute function for org!
But I think this will do what I need. Of course emacs / org couldn’t have a simple preproccessor-like macro :)
David
Sent from my iPhone
> On Nov 1, 2017, at 9:17 AM, Kaushal Modi <kaushal.modi@gmail.com> wrote:
>
>> On Wed, Nov 1, 2017 at 11:51 AM Kaushal Modi <kaushal.modi@gmail.com> wrote:
>> I still don't have a fully working solution (see below). Hopefully someone can help figure out the reason for "Invalid read syntax: #" error.
>
> OK, I found a workaround. Below solution works:
>
> 1. Eval the =org-macros= block once (=C-c C-c=)
> - Always use that =org-macros= block to define the Org macros for this file.
> - Hitting =C-c C-c= will insert those macros in this file.
> - This block is reused as a noweb-ref in other blocks.. so keeping just this
> block as a source for all Org macros will be convenient.
> 2. Then export that file (=C-c C-e h o=)
>
> =====
> #+BEGIN_SRC org :noweb-ref org-macros :results output replace :exports none
> ,#+MACRO: SEC_FOO Foo Topic
> ,#+MACRO: SEC_BAR Bar Topic
> #+END_SRC
>
> #+NAME: ehdr
> #+BEGIN_SRC emacs-lisp :var macro="n" :noweb yes :results raw :exports none
> (with-temp-buffer
> (insert "
> <<org-macros>>
> \n")
> (let ((start (point)))
> (insert "// ---------------------------\n")
> (insert (concat "// {{{" macro "}}}"))
> (org-mode)
> (org-macro-replace-all
> (append org-macro-templates org-export-global-macros))
> (buffer-substring-no-properties start (point-max))))
> #+END_SRC
>
> * Section 1: {{{SEC_FOO}}}
> #+BEGIN_SRC verilog :noweb yes
> <<ehdr(macro="SEC_FOO")>>
> parameter A = 1;
> #+END_SRC
>
> * Section 2: {{{SEC_BAR}}}
> #+BEGIN_SRC verilog :noweb yes
> <<ehdr(macro="SEC_BAR")>>
> parameter A = 1;
> #+END_SRC
> =====
> --
> Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 3642 bytes --]
next prev parent reply other threads:[~2017-11-01 17:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 23:13 macro replacement in code block? David Rogoff
2017-11-01 0:32 ` Kaushal Modi
2017-11-01 3:21 ` David Rogoff
2017-11-01 15:51 ` Kaushal Modi
2017-11-01 16:04 ` Multi-line noweb expansion in elisp insert form (Was Re: macro replacement in code block?) Kaushal Modi
2017-11-01 16:17 ` macro replacement in code block? Kaushal Modi
2017-11-01 17:32 ` David Rogoff [this message]
2017-11-01 18:48 ` Kaushal Modi
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=95C792B0-79AC-4F65-B07B-F7787D25352D@therogoffs.com \
--to=david@therogoffs.com \
--cc=emacs-orgmode@gnu.org \
--cc=kaushal.modi@gmail.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).