From: Grant Rettke <gcr@wisdomandwonder.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: Paul Rudin <public-paul-sqPYmOVXOov10XsdtD+oqA@plane.gmane.org>,
public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org
Subject: Re: inline constant substitution
Date: Sun, 12 Oct 2014 20:00:29 -0500 [thread overview]
Message-ID: <CAAjq1mdmwaaJdyMGR8yUapsRHP=BfkJPdY=JpmATgH+no+mGdA@mail.gmail.com> (raw)
In-Reply-To: <8738atpbuk.fsf@nicolasgoaziou.fr>
Should a noweb-ref be expanded as imagined inside of a table for this case?
Eg pseudo code:
,----
| #+NAME: foo
| #+begin_src emacs-lisp
| 42
| #+end_src
|
|
| #+NAME: ns
| | n |
| |-------|
| | 1 |
| | 2 |
| | <<foo>> |
| | |
`----
On Sun, Oct 12, 2014 at 10:05 AM, Nicolas Goaziou
<mail@nicolasgoaziou.fr> wrote:
>
>
> Hello,
>
> Paul Rudin <paul-sqPYmOVXOov10XsdtD+oqA@public.gmane.org> writes:
>
>> Suppose I have:
>>
>> #+CONSTANTS: foo=42
>>
>> How can I make inline references to a constant on export in regular
>> text, rather than in a table?
>>
>> I want to be able to write something like:
>>
>> The value of foo is $foo
>>
>> in my org file, and then end up with:
>>
>> The value of foo is 42
>>
>> when I export to LaTeX.
>
> Constants are for tables only. You can use a macro instead:
>
> #+MACRO: foo 42
>
> The value of foo is {{{foo}}}.
>
>
> Regards,
>
> --
> Nicolas Goaziou
>
>
--
Grant Rettke
gcr@wisdomandwonder.com | 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
prev parent reply other threads:[~2014-10-13 1:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-12 14:41 inline constant substitution Paul Rudin
2014-10-12 15:05 ` Nicolas Goaziou
2014-10-12 17:13 ` Paul Rudin
2014-10-13 11:51 ` Eric S Fraga
2014-10-13 19:38 ` Paul Rudin
2014-10-13 1:00 ` Grant Rettke [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='CAAjq1mdmwaaJdyMGR8yUapsRHP=BfkJPdY=JpmATgH+no+mGdA@mail.gmail.com' \
--to=gcr@wisdomandwonder.com \
--cc=mail@nicolasgoaziou.fr \
--cc=public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org \
--cc=public-paul-sqPYmOVXOov10XsdtD+oqA@plane.gmane.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).