controling width of graphviz source block result

controling width of graphviz source block result

[regcl]

When I try to control the width of the image produced by 
included graphviz (DOT) code like so ...

#+ATTR_HTML: :width 300
#+INCLUDE: gnus.dot SRC dot :file gnus.png :exports results

... width is not controlled. 

This works ...

#+INCLUDE: "gnus.dot" SRC dot :file gnus.png :exports none
#+ATTR_HTML: :width 300
file:gnus.png

So it makes me wonder... Is this a bug or operator error?

Thanks,
regcl

GNU Emacs 24.3.1 (x86_64-unknown-linux-gnu, X toolkit, Xaw scroll bars)
of 2014-02-20 on e3

Org-mode version 8.2.5c (release_8.2.5c @
/home/regcl/.emacs.d/lisp/org-mode/lisp/)

Re: controling width of graphviz source block result

[Nicolas Goaziou]

Hello,

regcl <regcl@channing.harvard.edu> writes:

> When I try to control the width of the image produced by 
> included graphviz (DOT) code like so ...
>
> #+ATTR_HTML: :width 300
> #+INCLUDE: gnus.dot SRC dot :file gnus.png :exports results
>
> ... width is not controlled.

Here the HTML attribute applies to the INCLUDE keyword below.

> #+INCLUDE: "gnus.dot" SRC dot :file gnus.png :exports none
> #+ATTR_HTML: :width 300
> file:gnus.png

Here, the HTML attribute applies to the link below.

Therefore, the behaviour is to be expected.


Regards,

-- 
Nicolas Goaziou

Re: controling width of graphviz source block result

[regcl]

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
>
> regcl <regcl@channing.harvard.edu> writes:
>
>> When I try to control the width of the image produced by 
>> included graphviz (DOT) code like so ...
>>
>> #+ATTR_HTML: :width 300
>> #+INCLUDE: gnus.dot SRC dot :file gnus.png :exports results
>>
>> ... width is not controlled.
>
> Here the HTML attribute applies to the INCLUDE keyword below.
>
>> #+INCLUDE: "gnus.dot" SRC dot :file gnus.png :exports none
>> #+ATTR_HTML: :width 300
>> file:gnus.png
>
> Here, the HTML attribute applies to the link below.
>
> Therefore, the behaviour is to be expected.
>
>
> Regards,

So I am understanding from your answer that attribues only "modify" the
next immediate "thing" in the .org document, and do not persist, so to
speak.

But I have discovered that it works to stack them up like this ...

#+ATTR_HTML: :width 1000
#+ATTR_ODT: :width 15 :height 15
[[file:gnus.png]]

... so I am a little confused. 

Could you please clarify?

Thanks,
regcl

Re: controling width of graphviz source block result

[Nicolas Goaziou]

Hello,

regcl <regcl@channing.harvard.edu> writes:

> So I am understanding from your answer that attribues only "modify" the
> next immediate "thing" in the .org document, and do not persist, so to
> speak.

"things" are called "elements" in Org lingo and "attributes" are called
"affiliated keywords". So, yes, affiliated keywords apply to the element
right after them.

> But I have discovered that it works to stack them up like this ...
>
> #+ATTR_HTML: :width 1000
> #+ATTR_ODT: :width 15 :height 15
> [[file:gnus.png]]
>
> ... so I am a little confused. 
>
> Could you please clarify?

Both keywords are affiliated keywords. There is only one element in this
example (a paragraph containing a single link). Affiliated keywords
apply to the next element, not the next affiliated keyword.

For more information, see:

  http://orgmode.org/worg/dev/org-syntax.html

or the comments at the beginning of "org-element.el".


Regards,

-- 
Nicolas Goaziou

Re: controling width of graphviz source block result

[regcl]

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
>
> regcl <regcl@channing.harvard.edu> writes:
>
>> So I am understanding from your answer that attribues only "modify" the
>> next immediate "thing" in the .org document, and do not persist, so to
>> speak.
>
> "things" are called "elements" in Org lingo and "attributes" are called
> "affiliated keywords". So, yes, affiliated keywords apply to the element
> right after them.
>
>> But I have discovered that it works to stack them up like this ...
>>
>> #+ATTR_HTML: :width 1000
>> #+ATTR_ODT: :width 15 :height 15
>> [[file:gnus.png]]
>>
>> ... so I am a little confused. 
>>
>> Could you please clarify?
>
> Both keywords are affiliated keywords. There is only one element in this
> example (a paragraph containing a single link). Affiliated keywords
> apply to the next element, not the next affiliated keyword.
>
> For more information, see:
>
>   http://orgmode.org/worg/dev/org-syntax.html
>
> or the comments at the beginning of "org-element.el".
>
>
> Regards,

Thank you, this is helpful. May require a little study ;)

best,
regcl

Re: controling width of graphviz source block result

[regcl]

Hi Nicolas, 

Thank you for your earlier comments.  In order to adjust the scaling of
a graphic generated by a R source block I am doing this ...

** adjusting scaling of a figure generated from source
#+begin_src R :results graphics silent :file foo2.pdf :exports results 
  plot(c(1:10), c(10:1))
  #+end_src
#+attr_latex: :width .35\textwidth
file:foo2.pdf 

While this does work, it is a wee bit unsatisfying to type "foo2.pdf""
twice.

Is there a better way to apply the latex keyword to the results?

Many thanks,
regcl

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
>
> regcl <regcl@channing.harvard.edu> writes:
>
>> So I am understanding from your answer that attribues only "modify" the
>> next immediate "thing" in the .org document, and do not persist, so to
>> speak.
>
> "things" are called "elements" in Org lingo and "attributes" are called
> "affiliated keywords". So, yes, affiliated keywords apply to the element
> right after them.
>
>> But I have discovered that it works to stack them up like this ...
>>
>> #+ATTR_HTML: :width 1000
>> #+ATTR_ODT: :width 15 :height 15
>> [[file:gnus.png]]
>>
>> ... so I am a little confused. 
>>
>> Could you please clarify?
>
> Both keywords are affiliated keywords. There is only one element in this
> example (a paragraph containing a single link). Affiliated keywords
> apply to the next element, not the next affiliated keyword.
>
> For more information, see:
>
>   http://orgmode.org/worg/dev/org-syntax.html
>
> or the comments at the beginning of "org-element.el".
>
>
> Regards,

Re: controling width of graphviz source block result

[Nicolas Goaziou]

Hello,

regcl <regcl@channing.harvard.edu> writes:

> Thank you for your earlier comments.  In order to adjust the scaling of
> a graphic generated by a R source block I am doing this ...
>
> ** adjusting scaling of a figure generated from source
> #+begin_src R :results graphics silent :file foo2.pdf :exports results 
>   plot(c(1:10), c(10:1))
>   #+end_src
> #+attr_latex: :width .35\textwidth
> file:foo2.pdf 
>
> While this does work, it is a wee bit unsatisfying to type "foo2.pdf""
> twice.
>
> Is there a better way to apply the latex keyword to the results?

I don't know what the current state of the art is, but I usually add
a name to the block, generate the result link, and add attributes above.


Regards,

-- 
Nicolas Goaziou

Re: controling width of graphviz source block result

[Sebastien Vauban]

regcl wrote:
> Thank you for your earlier comments.  In order to adjust the scaling of
> a graphic generated by a R source block I am doing this ...
>
> ** adjusting scaling of a figure generated from source
>
> #+begin_src R :results graphics silent :file foo2.pdf :exports results 
>   plot(c(1:10), c(10:1))
>   #+end_src
>
> #+attr_latex: :width .35\textwidth
> file:foo2.pdf 
>
> While this does work, it is a wee bit unsatisfying to type "foo2.pdf""
> twice.
>
> Is there a better way to apply the latex keyword to the results?

What I do is that I simply execute it a first time, so that the link is
created (that is, the name is copied) by Org.

Best regards,
  Seb

-- 
Sebastien Vauban