[babel] dot in pdf directly

[babel] dot in pdf directly

[andrea Crotti]

Still a couple of questions, I found something here
in the newsgroup but nothing helped me...

First, how many and where can I find all the possible

#+begin_...?

I mean why is
#+begin_dot and not

#+begin_src dot?

I would like to insert my dot info and on exporting getting a pdf with
embedded the generated eps, it would be great!

I don't have very clear the grammar I can use in the #+begin_.. line,
is there a clear explanation somewhere?

Thanks for the fantastic work!

Re: [babel] dot in pdf directly

[Sebastian Rose]

andrea Crotti <andrea.crotti.0@gmail.com> writes:
> Still a couple of questions, I found something here
> in the newsgroup but nothing helped me...
>
> First, how many and where can I find all the possible
>
> #+begin_...?
>
> I mean why is
> #+begin_dot and not
>
> #+begin_src dot?
>
> I would like to insert my dot info and on exporting getting a pdf with
> embedded the generated eps, it would be great!
>
> I don't have very clear the grammar I can use in the #+begin_.. line,
> is there a clear explanation somewhere?


The difference is, 

   #+begin_src mode-name

just tells the exporter that the following block is a `mode-name' block,
where mode-name == the name of the emacs mode you'd use to edit a file
in that language.

This handy if you want to edit the block's contents (C-c '). Eventually,
the source code inside the block will be highlighted on export to
XHTML. The mode is important then, too. Contents of blocks like this are
exported verbatim.




In contrast, blocks like

   #+begin_ditaa

will never export verbatim. Instead, the contents are treated specially
or even send to an external program, that will create an image (e.g. -
in most cases), that will in turn replace the block in the exported
result.


  Sebastian

Re: [babel] dot in pdf directly

[Eric Schulte]

Sebastian Rose <sebastian_rose@gmx.de> writes:

> andrea Crotti <andrea.crotti.0@gmail.com> writes:
>> Still a couple of questions, I found something here
>> in the newsgroup but nothing helped me...
>>
>> First, how many and where can I find all the possible
>>
>> #+begin_...?
>>
>> I mean why is
>> #+begin_dot and not
>>
>> #+begin_src dot?
>>
>> I would like to insert my dot info and on exporting getting a pdf with
>> embedded the generated eps, it would be great!
>>
>> I don't have very clear the grammar I can use in the #+begin_.. line,
>> is there a clear explanation somewhere?
>
>
> The difference is, 
>
>    #+begin_src mode-name
>
> just tells the exporter that the following block is a `mode-name' block,
> where mode-name == the name of the emacs mode you'd use to edit a file
> in that language.
>
> This handy if you want to edit the block's contents (C-c '). Eventually,
> the source code inside the block will be highlighted on export to
> XHTML. The mode is important then, too. Contents of blocks like this are
> exported verbatim.
>
>
>
>
> In contrast, blocks like
>
>    #+begin_ditaa
>
> will never export verbatim. Instead, the contents are treated specially
> or even send to an external program, that will create an image (e.g. -
> in most cases), that will in turn replace the block in the exported
> result.
>
>

The exception to the above is that *if* you have org-babel loaded, then
some begin_src blocks will become activated.  The source blocks
activated by org-babel are the contents of the variable
`org-babel-interpreters'.  They can be used to activate for example dot
blocks, and will then have the result of possibly evaluating dot blocks
on export in the same manner as org-exp-blocks.

The two separate mechanisms are confusion, but for now are necessary to
allow org-mode users to evaluate some simple block types (like dot) on
export without having to load up all of org-babel.

I hope the above isn't too confusing :) -- Eric

>
>   Sebastian
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [babel] dot in pdf directly

[andrea Crotti]

Eric Schulte <schulte.eric <at> gmail.com> writes:

> 
> The two separate mechanisms are confusion, but for now are necessary to
> allow org-mode users to evaluate some simple block types (like dot) on
> export without having to load up all of org-babel.
> 
> I hope the above isn't too confusing :) -- Eric
> 


No no thanks a lot not it's very clear.
Coming back to my original question, am I able to insert directly
the eps generated in my final generated pdf??

Maybe I have to
#+begin_dot -Tpdf -o file.pdf
...
#+end_dot

And then somewhere write some latex code to include it?
#+begin_latex
\includegraphics..
#+end_latex

or can it even be easier?

Re: Re: [babel] dot in pdf directly

[Sebastian Rose]

andrea Crotti <andrea.crotti.0@gmail.com> writes:
> Eric Schulte <schulte.eric <at> gmail.com> writes:
>
>> 
>> The two separate mechanisms are confusion, but for now are necessary to
>> allow org-mode users to evaluate some simple block types (like dot) on
>> export without having to load up all of org-babel.
>> 
>> I hope the above isn't too confusing :) -- Eric
>> 
>
>
> No no thanks a lot not it's very clear.
> Coming back to my original question, am I able to insert directly
> the eps generated in my final generated pdf??
>
> Maybe I have to
> #+begin_dot -Tpdf -o file.pdf
> ...
> #+end_dot
>
> And then somewhere write some latex code to include it?
> #+begin_latex
> \includegraphics..
> #+end_latex

Yes, you can include the eps image like this at any point - not sure if
you need to run the export twice, once the dot block changes.


But the dot block itself will always be executed and replaced by the
resulting image. This is absolutely fine in 99% of all cases.

Suppose you want to refer to the image several times, how about this
then: 

   1. Create a file your-org-directory/images/images.org
   2. Put all images into that file, that you need to reference more
      than once, or that you need to be out of sight to avoid clutter.
   3. Include your images using the relative path to
      ../your-org-directory/images/resulting-image.eps 




Sebastian

Re: Re: [babel] dot in pdf directly

[Eric Schulte]

Sebastian Rose <sebastian_rose@gmx.de> writes:

> andrea Crotti <andrea.crotti.0@gmail.com> writes:
>> Eric Schulte <schulte.eric <at> gmail.com> writes:
>>
>>> 
>>> The two separate mechanisms are confusion, but for now are necessary to
>>> allow org-mode users to evaluate some simple block types (like dot) on
>>> export without having to load up all of org-babel.
>>> 
>>> I hope the above isn't too confusing :) -- Eric
>>> 
>>
>>
>> No no thanks a lot not it's very clear.
>> Coming back to my original question, am I able to insert directly
>> the eps generated in my final generated pdf??
>>
>> Maybe I have to
>> #+begin_dot -Tpdf -o file.pdf
>> ...
>> #+end_dot
>>
>> And then somewhere write some latex code to include it?
>> #+begin_latex
>> \includegraphics..
>> #+end_latex
>
> Yes, you can include the eps image like this at any point - not sure if
> you need to run the export twice, once the dot block changes.
>
>
> But the dot block itself will always be executed and replaced by the
> resulting image. This is absolutely fine in 99% of all cases.
>
> Suppose you want to refer to the image several times, how about this
> then: 
>
>    1. Create a file your-org-directory/images/images.org
>    2. Put all images into that file, that you need to reference more
>       than once, or that you need to be out of sight to avoid clutter.
>    3. Include your images using the relative path to
>       ../your-org-directory/images/resulting-image.eps 
>

Note that the solution I'm about to propose relies on the use of
org-babel and #+begin_src dot blocks rather than #+begin_dot blocks.

When in these situations I will often set the block so that neither the
code or the resulting image is exported, and so that the results of
block evaluation are silent.

#+begin_src dot :file file.pdf :cmdline -Tpdf :exports none :results silent
...
#+end_src

Then I manually add file links to the image throughout my document.

[[file:file.pdf]]

Whenever I change the contents of the block I manually re-evaluate the
block with C-c C-c and the image to which all of the links point is
updated.

Best -- Eric

>
>
>
>
> Sebastian
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode

Re: [babel] dot in pdf directly

[andrea Crotti]

Eric Schulte <schulte.eric <at> gmail.com> writes:

> Note that the solution I'm about to propose relies on the use of
> org-babel and #+begin_src dot blocks rather than #+begin_dot blocks.
> 
> When in these situations I will often set the block so that neither the
> code or the resulting image is exported, and so that the results of
> block evaluation are silent.
> 
> #+begin_src dot :file file.pdf :cmdline -Tpdf :exports none :results silent
> ...
> #+end_src
> 
> Then I manually add file links to the image throughout my document.
> 
> [[file:file.pdf]]
> 
> Whenever I change the contents of the block I manually re-evaluate the
> block with C-c C-c and the image to which all of the links point is
> updated.
> 
> Best -- Eric
> 

Ok that's really perfect!
The only "problem" is that it keeps exporting the code even without
the :exports none, maybe I need some newlines?

**** s2
#+BEGIN_SRC dot :file s2.pdf :cmdline -Tpdf :exports none :results silent
    digraph s1 {
    t1;
    t2;
    }
#+END_SRC

    [[file:s2.pdf]]

Re: Re: [babel] dot in pdf directly

[Eric Schulte]

andrea Crotti <andrea.crotti.0@gmail.com> writes:

> Eric Schulte <schulte.eric <at> gmail.com> writes:
>
>> Note that the solution I'm about to propose relies on the use of
>> org-babel and #+begin_src dot blocks rather than #+begin_dot blocks.
>> 
>> When in these situations I will often set the block so that neither the
>> code or the resulting image is exported, and so that the results of
>> block evaluation are silent.
>> 
>> #+begin_src dot :file file.pdf :cmdline -Tpdf :exports none :results silent
>> ...
>> #+end_src
>> 
>> Then I manually add file links to the image throughout my document.
>> 
>> [[file:file.pdf]]
>> 
>> Whenever I change the contents of the block I manually re-evaluate the
>> block with C-c C-c and the image to which all of the links point is
>> updated.
>> 
>> Best -- Eric
>> 
>
> Ok that's really perfect!
> The only "problem" is that it keeps exporting the code even without
> the :exports none, maybe I need some newlines?
>
> **** s2
> #+BEGIN_SRC dot :file s2.pdf :cmdline -Tpdf :exports none :results silent
>     digraph s1 {
>     t1;
>     t2;
>     }
> #+END_SRC
>
>     [[file:s2.pdf]]
>

Hi Andrea,

there was a bug related to capitalization in org-exp-blocks, I've fixed
this bug in the head of the org-mode git repo.  Please grab the latest
org-mode and see if you problem persists.

Best -- Eric

Re: [babel] dot in pdf directly

[andrea Crotti]

A question about updating org...
I also have all my .emacs.d under git, so if I put
the whole org-mode in it (46M) I wast a lot of space.
But if I don't then every time I can't just "git pull" but I need more
operations, which can be annoying, how do you deal with it?

For the capitalization I could also always write not capitalized,
it's not a problem.
Given I've always seen the org directives capitalized I thought it 
would be better..
Andrea

Re: [babel] dot in pdf directly

[Julien Barnier]

Hi,

> A question about updating org...
> I also have all my .emacs.d under git, so if I put
> the whole org-mode in it (46M) I wast a lot of space.
> But if I don't then every time I can't just "git pull" but I need more
> operations, which can be annoying, how do you deal with it?

In my experience git deals very well with imbricated .git working
directory. If your .emacs.d is unde git version control, putting your
org-mode git folder in yout .emacs.d .gitignore file should be enough.

HTH,

-- 
Julien