From: tsd@tsdye.com (Thomas S. Dye)
To: Grant Rettke <gcr@wisdomandwonder.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: LaTeX style command re-use but for within org-mode documents?
Date: Sun, 11 May 2014 09:51:18 -1000 [thread overview]
Message-ID: <m27g5shz61.fsf@tsdye.com> (raw)
In-Reply-To: <CAAjq1mcVYTvbqoX0K-3nO+XSRRRTW8Tr17nz_==EEC6XHkwDgg@mail.gmail.com> (Grant Rettke's message of "Sun, 11 May 2014 14:38:13 -0500")
Aloha Grant,
Perhaps a macro? Macro expansion takes place during export.
All the best,
Tom
Grant Rettke <gcr@wisdomandwonder.com> writes:
> Hi,
>
> Today we are working on an org-document that contains a quote that
> will re-appear multiple times within
> the same document. Coming from LaTeX, my initial reaction is to create
> a new command with \newcommand.
> Trying to find something like that within org-mode set me down two paths.
>
> The first was to consider utilize literate programming. This would be
> a fine approach if I were publishing the tangled document, but I am
> not. Additionally, it is not code, just human readable text (a quote).
>
> The second thought was to learn about export filters. Stuff like using
> \rarr works just fine no matter where you export, so I wondered if I
> should follow a similar approach. I didn't pursue this further though,
> I wanted to get some feedback first.
>
> What is the standard approach for doing stuff like this?
>
> Regards,
>
> Grant Rettke | AAAS, ACM, ASA, FSF, IEEE, SIAM, Sigma Xi
> grettke@acm.org | http://www.wisdomandwonder.com/
> “Wisdom begins in wonder.” --Socrates
> ((λ (x) (x x)) (λ (x) (x x)))
> “Life has become immeasurably better since I have been forced to stop
> taking it seriously.” --Thompson
>
>
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2014-05-11 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 19:38 LaTeX style command re-use but for within org-mode documents? Grant Rettke
2014-05-11 19:51 ` Thomas S. Dye [this message]
2014-05-11 20:06 ` Suvayu Ali
2014-05-12 0:08 ` Grant Rettke
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=m27g5shz61.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=gcr@wisdomandwonder.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).