emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Juan Amiguet <jamiguet@gmail.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Export attributes for babel blocks
Date: Mon, 2 Oct 2017 09:10:49 +0200	[thread overview]
Message-ID: <CABmuXy92GV=H9Pc3oY1+GCJb4pTNWBoo3mt-czTb5RJ1+nTdhA@mail.gmail.com> (raw)
In-Reply-To: <m2infy6ndi.fsf@tsdye.com>

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

Thomas thank you for your answer,

I was thinking more of how to modify babel so that it would generate the
results block with the relevant exporter attribute parameters so that it
play nicely.
That is, the results block contains the directive it needs at the moment
the #+results block is bare and has no extra information for latex to pick
up and format correctly.

Kind regards.


--
Juan Amiguet Vercher
Practising theorist
All-round geek
Polyglot polymath

+41(0)774867913

On Mon, Oct 2, 2017 at 9:05 AM, Thomas S. Dye <tsd@tsdye.com> wrote:

> Aloha Juan Amiguet,
>
> Juan Amiguet writes:
>
> > Dear all,
> >
> > I have been having this issue for quite a while perhaps I am using the
> > feature wrong and someone can enlighten me or perhaps someone can point
> me
> > at the bit of code I can patch it myself.
> > Here is the issue:
> >
> > I have a babel block such as
> >
> > #+begin_src dot :file test.png
> > digraph test {
> > A -> B
> > }
> > #+end_src
> >
> > This will create after execution a
> >
> > #+RESULT:
> > [[file:./test.png]]
> >
> > Now if I would like have something like :width .5/.linewith as a
> attribute
> > to the image the only I have found is to do the following
> >
> > #+begin_src dot :file test.png :exports none
> > digraph test {
> > A -> B
> > }
> > #+end_src
> >
> > #+attr_latex: width=.5/linewidth
> > [[file:./test.png]]
> >
> > Is there a way of passing the export attributes to babel blocks in a way
> in
> > which from direct rendering of the document things work and I can adjust?
> > If now which part of the org mode codebase controls all of this?
> >
> > Thanking you all in advance.
>
> Dot doesn't know anything about the linewidth you might be using in
> LaTeX.  LaTeX will take any image and reproduce it at .5/linewidth,
> regardless of dot settings.
>
> The :cmdline header argument for dot is documented here:
> http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-dot.html
>
> You can find links to the dot command line arguments.  Babel gives you
> full access to the dot command line.
>
> hth,
> Tom
>
> --
> Thomas S. Dye
> http://www.tsdye.com
>

[-- Attachment #2: Type: text/html, Size: 3127 bytes --]

  reply	other threads:[~2017-10-02  7:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-02  6:46 Export attributes for babel blocks Juan Amiguet
2017-10-02  7:05 ` Thomas S. Dye
2017-10-02  7:10   ` Juan Amiguet [this message]
2017-10-02 10:26 ` Eric S Fraga
2017-10-02 12:23   ` Juan Amiguet

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='CABmuXy92GV=H9Pc3oY1+GCJb4pTNWBoo3mt-czTb5RJ1+nTdhA@mail.gmail.com' \
    --to=jamiguet@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=tsd@tsdye.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).