emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Perry Smith <pedz@easesoftware.com>
To: Max Nikulin <manikulin@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Where is Elisp evaluation documented in the Org Manual?
Date: Fri, 30 Sep 2022 11:25:02 -0500	[thread overview]
Message-ID: <1D5001B4-DA47-474C-AD45-BBF50F0DD7C7@easesoftware.com> (raw)
In-Reply-To: <9f1942ec-4bac-441e-99aa-8e6e9b232c0b@gmail.com>

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


> On Sep 30, 2022, at 11:07, Max Nikulin <manikulin@gmail.com> wrote:
> 
> On 30/09/2022 21:15, Perry Smith wrote:
> 
>> I discovered that it can be done like {{{kbd(M-TAB)}}}
>> Fascinating!!!  And I bet expr in the form of {{{ expr }}} could be any Elisp expression.  Cool!
>> But, where in the Org manual is this documented?
> 
> See info "(org) Macro Replacement" https://orgmode.org/manual/Macro-Replacement.html
> 
> If you are interested in particular in the implementation of kbd then have a look into doc/doc-setup.org and lisp/ox-texinfo.el files in the Org sources.
> 
> There are a pitfall with comma as macro argument separator. It is easy to forgot to escape it and to loose remaining arguments.

Thank you…

For others following along, the reference is doc/misc/org-setup.org and lisp/org/ox-texinfo.el in the source tree.

Also, I searched for {{{ in org.org but I failed to notice that some were escaped with =xxxx= such as:

    which can be referenced using ={{{name(arg1, arg2)}}}=

(making the text inside a verbatim).

Thank you again.


[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2022-09-30 16:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30 14:15 Where is Elisp evaluation documented in the Org Manual? Perry Smith
2022-09-30 16:07 ` Max Nikulin
2022-09-30 16:25   ` Perry Smith [this message]

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=1D5001B4-DA47-474C-AD45-BBF50F0DD7C7@easesoftware.com \
    --to=pedz@easesoftware.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=manikulin@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).