From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Controlling image width and placement in Beamer export
Date: Tue, 26 Nov 2013 10:19:35 -0500 [thread overview]
Message-ID: <87iovf9omw.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: 87haazb79c.fsf@syk.fi
Jarmo Hurri <jarmo.hurri@syk.fi> writes:
> Greetings.
>
> I needed to create an Asymptote-generated centered image with a smaller
> width than the default .9\linewidth in a Beamer export. After trial and
> error I ended with the method shown below. In particular, to my surprise
> an
>
> #+ATTR_LATEX: :width 5cm
>
> _above_ the #+BEGIN_SRC did not work, so I had to place the line above
> #+RESULTS:
>
> Is the following the best way to do this, or is there a more concise
> method?
>
> # ---------------------------------------------------------------
> #+BEGIN_SRC asymptote :file triangle.pdf
> size (8cm, 0);
> pair A = (0, 0), B = (4, 1), C = (3, 2);
> draw (A -- B -- C -- cycle);
> #+END_SRC
> #+LATEX: \begin{center}
> #+ATTR_LATEX: :width 5cm
> #+RESULTS:
> [[file:triangle.pdf]]
> #+LATEX: \end{center}
> # ---------------------------------------------------------------
>
My recommendation is to always name code blocks: then the corresponding results
blocks are named as well, tying the two together; subsequent evaluations
will just refresh the appropriate results block without introducincg new
results blocks. This is not as much of a problem as it used to be, but
naming code blocks is still a good guideline, imo.
Other than that, I think that's the best that you can do.
Nick
prev parent reply other threads:[~2013-11-26 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-26 13:51 Controlling image width and placement in Beamer export Jarmo Hurri
2013-11-26 15:06 ` John Hendy
2013-11-27 6:28 ` Jarmo Hurri
2013-11-27 13:51 ` Nick Dokos
2013-11-26 15:08 ` John Hendy
2013-11-26 15:19 ` Nick Dokos [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=87iovf9omw.fsf@alphaville.bos.redhat.com \
--to=ndokos@gmail.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).