emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: tsd@tsdye.com (Thomas S. Dye)
To: emacs-orgmode@gnu.org
Subject: Re: babel output as LaTeX code: help please!
Date: Tue, 10 Mar 2015 09:49:27 -1000	[thread overview]
Message-ID: <m2fv9ciqew.fsf@tsdye.com> (raw)
In-Reply-To: <87r3swll6a.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Tue, 10 Mar 2015 19:14:21 +0000")

Aloha Eric,

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> On Tuesday, 10 Mar 2015 at 08:42, Thomas S. Dye wrote:
>
> [...]
>
>> Have you tried
>>
>> #+call: drawlayout[:stdin solution]() :results raw
>>
>> or,
>>
>> #+call: drawlayout[:stdin solution]() :results latex
>>
>> which should make the print "#+begin_latex" etc. lines of drawlayout redundant?
>
> Both work perfectly.  Many thanks!
>
> The documentation confused me.  I see now that the end header arguments
> are not to be enclosed in [] whereas the inside ones are.  The
> documentation shows this in the example but the syntax seems to imply
> that the []s are required -- but in hindsight I guess the []s mean
> optional in this case.  However, they are not optional for the inside
> arguments...
>
> Ummm, the documentation is definitely confusing but I'm not sure how to
> improve it other than by adding a sentence making this explicit?

Perhaps the confusion comes from the fact that the syntax for #+call
lines differs from inline evaluation?  Inline evaluation requires [] for
the end header argument, but [] aren't used for the end header argument
of #+call lines.

I agree that this difference isn't easy to spot among all the ([<>]).
Perhaps a sentence pointing out the difference would be useful?

All the best,
Tom
-- 
Thomas S. Dye
http://www.tsdye.com

      reply	other threads:[~2015-03-10 19:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 17:25 babel output as LaTeX code: help please! Eric S Fraga
2015-03-10 18:42 ` Thomas S. Dye
2015-03-10 19:14   ` Eric S Fraga
2015-03-10 19:49     ` Thomas S. Dye [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=m2fv9ciqew.fsf@tsdye.com \
    --to=tsd@tsdye.com \
    --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).