From: Eric Schulte <schulte.eric@gmail.com>
To: Oleh <ohwoeowho@gmail.com>
Cc: org mode <emacs-orgmode@gnu.org>
Subject: Re: Does org export have something like Lisp quasiquote and unquote?
Date: Thu, 20 Feb 2014 08:36:53 -0500 [thread overview]
Message-ID: <877g8p689i.fsf@gmail.com> (raw)
In-Reply-To: CAA01p3oGt36BVz2LbXkzbWhNreZd7nM_7K87wTq7bxm=NwVrGg@mail.gmail.com
Oleh <ohwoeowho@gmail.com> writes:
>> The following will do what you want.
>>
>> set the value
>> #+begin_src lisp :results silent
>> (defvar foo '(defun square (x) (* x x)))
>> #+end_src
>>
>> #+begin_src lisp :results output pp code
>> foo
>> #+end_src
>>
>> #+RESULTS:
>> #+BEGIN_SRC lisp
>>
>> (DEFUN SQUARE (X) (* X X))
>> #+END_SRC
>>
>> Best,
>>
>> --
>> Eric Schulte
>> https://cs.unm.edu/~eschulte
>> PGP: 0x614CA05D
>
> Thanks, Eric,
>
> but this isn't what I had in mind. I want the org-mode file to remain
> unchanged while behaving as if it was changed, something like C
> macros: C compiler is not aware of macros and I'm not aware of the
> expanded code, but we get along nicely anyway.
>
Think of code blocks as macros with optional interactive expansion. If
you don't execute the code block you need not ever see the results,
however with an additional ":exports results" header argument the code
block will be executed and replaced with it's results on export.
Take a look at the (info "(org) Working With Source Code") portion of
the Org-mode manual.
Hope this helps,
>
> First use-case is that I'm writing documentation for a library of
> functions, so some of them are mentioned a few times. I'd like to
> refer to them not by name, which can be subjected to change but by a
> file local variable. For instance, I've got a link in a table
> referring to a heading. They both have the same name and I'd like to
> keep them consistent, but I don't want to do it manually.
>
> Second use-case is that I'm generating a HTML block with
> `htmlize-buffer' that I want to include in the document. I'd prefer
> not to have hundreds of lines of HTML that correspond to 3 lines of
> code that they're supposed to represent. I'd rather generate this HTML
> via this macro mechanism that I hope exists in some form, maybe in
> conjunction with a makefile-like mechanism.
>
> Here's the org file that I'm working on:
> https://raw.github.com/abo-abo/lispy/gh-pages/index.org.
> As you see a lot of redundancy there and also several huge ugly HTML blocks.
> Btw, is there a way to #include HTML blocks?
> Here's the export result: http://abo-abo.github.io/lispy/.
>
> regards,
> Oleh
--
Eric Schulte
https://cs.unm.edu/~eschulte
PGP: 0x614CA05D
next prev parent reply other threads:[~2014-02-20 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 15:07 Does org export have something like Lisp quasiquote and unquote? Oleh
2014-02-19 17:27 ` Eric Schulte
2014-02-19 18:45 ` Oleh
2014-02-20 13:36 ` Eric Schulte [this message]
2014-02-20 16:56 ` Oleh
2014-02-20 18:13 ` Eric Schulte
2014-02-20 21:48 ` Alan Schmitt
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=877g8p689i.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ohwoeowho@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).