emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: kevinbanjo <kevinbanjo@gmail.com>
To: "Berry, Charles" <ccberry@health.ucsd.edu>
Cc: Ihor Radchenko <yantar92@gmail.com>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: substitutions in html export?
Date: Sun, 17 Jul 2022 12:19:26 -0700	[thread overview]
Message-ID: <CAOHcZqOmVo3q7LGJ55smOoPKoYbXL0gszFndmxKGjUaPsFB_gA@mail.gmail.com> (raw)
In-Reply-To: <E1596106-D803-47F7-B6E3-6B6370566615@health.ucsd.edu>

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

On Sun, Jul 17, 2022 at 11:54 AM Berry, Charles <ccberry@health.ucsd.edu>
wrote:

> Kevin,
>
> > On Jul 17, 2022, at 10:18 AM, kevinbanjo <kevinbanjo@gmail.com> wrote:
> >
> >
> >
> > On Sun, Jul 17, 2022 at 7:24 AM Ihor Radchenko <yantar92@gmail.com>
> wrote:
> > See inline calls in
> https://orgmode.org/manual/Evaluating-Code-Blocks.html#Evaluating-Code-Blocks
> >
> > I did this and it didn't work (but the one outside the export block did):
> >
> > #+title:test
> >
> > #+name: numbers
> > #+begin_src emacs-lisp :exports none
> > 40
> > #+end_src
> >
> > #+begin_export html
> >
> > the result is call_numbers()
> >
> > #+end_export
>
>
> The export block provides text that is to be used "as is" by the html
> backend. So, "call_numbers()" is treated as html.
>
> You need to construct the export block programmatically. Maybe something
> like
>
> #+begin_src emacs-lisp :results html :exports results :var num=numbers()
>    (format "the result is %d" num )
> #+end_src
>
>
> HTH,
>
> Chuck
>
>
>
Thanks for that Chuck.   It would seem a lot cleaner if there was a hook or
something one could run that would just expand macros in export blocks
before exporting them.

-Kevin

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

  reply	other threads:[~2022-07-17 19:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-17 14:16 substitutions in html export? kevinbanjo
2022-07-17 14:25 ` Ihor Radchenko
2022-07-17 17:18   ` kevinbanjo
2022-07-17 18:54     ` Berry, Charles
2022-07-17 19:19       ` kevinbanjo [this message]
2022-07-17 23:18         ` Ihor Radchenko
2022-07-18  1:16       ` kevinbanjo
2022-07-18  4:35         ` Ihor Radchenko
2022-07-17 20:54   ` kevinbanjo
2022-07-17 23:21     ` Ihor Radchenko
2022-07-18 19:00     ` Berry, Charles

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=CAOHcZqOmVo3q7LGJ55smOoPKoYbXL0gszFndmxKGjUaPsFB_gA@mail.gmail.com \
    --to=kevinbanjo@gmail.com \
    --cc=ccberry@health.ucsd.edu \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@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).