From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: TIL about use of eval in user Org macros.. Documentation?
Date: Thu, 21 Dec 2017 10:45:38 +0100 [thread overview]
Message-ID: <87tvwkh0sd.fsf@gmx.us> (raw)
In-Reply-To: CAFyQvY1htTzxL1OxVN-7zdaf-Ta4WV_Ja-1k3mp2vUunBbNNYg@mail.gmail.com
Kaushal Modi <kaushal.modi@gmail.com> writes:
> Hello,
>
> The commit message in this commit is golden:
> http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=3ac619c8ac9934a2a1368f3de8ffad951f900067
>
> Using that info, I came up with a "classified" version of n macro for markdown/HTML:
>
> #+MACRO: sec (eval (concat "<span class=\"section-num\">" (number-to-string (org-macro--counter-increment $1 $2)) "</span>"))
>
> Based on that I have two questions:
> 1. Can you please document the use of eval form in Org macro definitions
> in the Org manual(.org)? Its awesome wasn't evident to me until I read
> that commit message.
I guess it isn’t documented in the manual...
I agree, there could be a second example and the mention of using lisp or
at least a mention of the ‘org-export-global-macros’ docstring.
> 2. (Another question on canonical approach) What would be the recommended approach for an exporter backend to add new
> macros or override existing macros (like "n" macro to wrap the string with HTML class as an example)? Should it update
> org-macro-templates in org-export-before-processing-hook? or something similar?
Do you really need to overwrite an old macro? Couldn’t you define a new
macro? org-export-before-processing-hook is definitely the right hook,
cf. ‘org-export-as’.
(defun fooreplace (backend)
(when (eq backend 'mybackend)
(goto-char (point-min))
(while (search-forward-regexp "{{{foo\\((?\\)" nil t)
(replace-match "{{{myfoo\\1"))
(goto-char (point-max))
(insert "\n#+macro: myfoo mybar\n"))))
Rasmus
--
May contains speling mistake
next prev parent reply other threads:[~2017-12-21 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-20 22:30 TIL about use of eval in user Org macros.. Documentation? Kaushal Modi
2017-12-21 9:45 ` Rasmus [this message]
2017-12-22 20:10 ` Samuel Wales
2017-12-25 10:26 ` Nicolas Goaziou
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=87tvwkh0sd.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).