Hello,
Nick Dokos writes:
> Please find an org file and the corresponding tex file attached. The
> directory structure is as follows:
>
> ~/src/org--images--foo.png
> |
> |--latex--example.{org,tex}
> |
> |--example.t2d/pdf/build
>
> Just execu
Nicolas Goaziou writes:
> Nick Dokos writes:
>
>> Nick Dokos writes:
>>
>>> Just a heads-up: As part of testing this, I stumbled on an unrelated
>>> current-working-directory problem, where on exporting to pdf, the
>>> pdflatex of the produced tex file fails to find an image file specified
>>>
Nick Dokos writes:
> Nick Dokos writes:
>
>> Just a heads-up: As part of testing this, I stumbled on an unrelated
>> current-working-directory problem, where on exporting to pdf, the
>> pdflatex of the produced tex file fails to find an image file specified
>> with a relative pathname (it works
Hello,
Nick Dokos writes:
> Nicolas Goaziou writes:
>
>>> With
>>>
>>>#+ATTR_LATEX: :options scale=1.5:width "" :placement [htb!]
>>> it fails here
>>>(attr (org-export-read-attribute :attr_latex parent))
>>>
>>> which evalues to something like
>>>
>>> Result: (:
Nick Dokos writes:
> Just a heads-up: As part of testing this, I stumbled on an unrelated
> current-working-directory problem, where on exporting to pdf, the
> pdflatex of the produced tex file fails to find an image file specified
> with a relative pathname (it works fine with an absolute path n
Nicolas Goaziou writes:
>> With
>>
>>#+ATTR_LATEX: :options scale=1.5:width "" :placement [htb!]
>> it fails here
>>(attr (org-export-read-attribute :attr_latex parent))
>>
>> which evalues to something like
>>
>> Result: (:options "scale=1.5" :placement "[htb!]" :
Hello,
Rasmus writes:
> Nick Dokos writes:
>> if I rearrange the line to
>>
>> #+ATTR_LATEX: :width "" :placement [htb!] :options scale=1.5
>>
>> I get the "Wrong argument type" error in the current version as
>> well.
>
> I can reproduce this here.
>
>> I guess :width has to be after the
Nick Dokos writes:
>>> One thing that I couldn't figure out is how to get rid of the width
>>> specification altogether.
>>
>> It's a feature. We had a lengthy discussion about it a while ago
>> (myself, Nicholas and Aaron, I believe)
>>
>
> Count me confused again: what's the feature? I'll go
Rasmus writes:
>> One thing that I couldn't figure out is how to get rid of the width
>> specification altogether.
>
> It's a feature. We had a lengthy discussion about it a while ago
> (myself, Nicholas and Aaron, I believe)
>
Count me confused again: what's the feature? I'll go looking for
>>> When I include the following in my org file
>>>
>>> #+attr_latex: scale=1.5, placement =[htb!]
>>> [[file:img/figure2.eps]]
>>
>> The syntax changes. Something like this might give you what you want.
>>
>> #+ATTR_LATEX: :placement [htb!] :options scale=1.5
>> #+CAPTION: a float needs a capti
Rasmus writes:
> Hi Marvin,
>
> Marvin Doyley writes:
>
>> Hi there,
>>
>> When I include the following in my org file
>>
>> #+attr_latex: scale=1.5, placement =[htb!]
>> [[file:img/figure2.eps]]
>
> The syntax changes. Something like this might give you what you want.
>
> #+ATTR_LATEX: :place
Hi Rasmus,
It is still not behaving properly
#+ATTR_LATEX: :options scale=2
[[file:fig.pdf]]
yields
\begin{figure}[htb]
\centering
\includegraphics[scale=2,width=.9\linewidth]{fig.pdf}
\end{figure}
which is still not quite right, including option, this still doesn't remove the
extra width =
Hi Marvin,
Marvin Doyley writes:
> Hi there,
>
> When I include the following in my org file
>
> #+attr_latex: scale=1.5, placement =[htb!]
> [[file:img/figure2.eps]]
The syntax changes. Something like this might give you what you want.
#+ATTR_LATEX: :placement [htb!] :options scale=1.5
#+
Hi there,
When I include the following in my org file
#+attr_latex: scale=1.5, placement =[htb!]
[[file:img/figure2.eps]]
This was exported as
\begin{figure}[htb]
\centering
\includegraphcis[width=0.9\linewidth]{img/figure2.eps}
\end{figure}
rather than
\begin{figure}[htb!]
\centering
\inc
Hello,
Aaron Ecay writes:
> 2013ko urtarrilak 23an, Nicolas Goaziou-ek idatzi zuen:
>> You needn't. org-exp-blocks functionalities are supported by the new
>> exporter out of the box.
>
> Can you say more about this? I looked for but did not find a
> replacement to the org-export-blocks variabl
Nicolas,
Thank you for your explanations, which were very helpful.
2013ko urtarrilak 23an, Nicolas Goaziou-ek idatzi zuen:
> You needn't. org-exp-blocks functionalities are supported by the new
> exporter out of the box.
Can you say more about this? I looked for but did not find a
replacement t
Hello,
Aaron Ecay writes:
> I’m dealing with a puzzling bug in the new exporter. As background,
> I’ve written a custom function to process special-blocks, to replicate
> in the new exporter the functionality of the org-exp-blocks package
> (http://orgmode.org/worg/org-contrib/org-exp-blocks.h
Hello,
I’m dealing with a puzzling bug in the new exporter. As background,
I’ve written a custom function to process special-blocks, to replicate
in the new exporter the functionality of the org-exp-blocks package
(http://orgmode.org/worg/org-contrib/org-exp-blocks.html). Because I
need the un-p
Rick Frankel writes:
> So, it seems that as long as there is a body (or blank) line after the
> parent heading and you position the cursor on that line, it works
> (point at X):
>
> #+begin_src org
> * Title
> X
> ** heading 1
>text
> ** heading 2
>...
> #+end_src
>
> But if there is no
On Wed, Jan 16, 2013 at 07:36:10PM +0100, Nicolas Goaziou wrote:
> Rick Frankel writes:
>
> > In the new exporter, when the option to export only the subtree is
> > specified, the first heading in the subtree is used as the title of
> > the document. This seems wrong, as it becomes the title, the
Hello,
Rick Frankel writes:
> In the new exporter, when the option to export only the subtree is
> specified, the first heading in the subtree is used as the title of
> the document. This seems wrong, as it becomes the title, the first
> element in the table of contents and the first (not necess
In the new exporter, when the option to export only the subtree is
specified, the first heading in the subtree is used as the title of
the document. This seems wrong, as it becomes the title, the first
element in the table of contents and the first (not necessarily
the top level) section in the doc
Please ignore this, the problem does not occur using the latest git source.
--
Best,
Hsiu-Khuern.
Hi all,
Under the new exporter, if I export this to ascii:
--
#+TITLE:
#+AUTHOR:
#+OPTIONS: toc:nil
* A
1. this
1. something
#+begin_src r
a <- 1
#+end_src
2. other
--
I get
-
Achim Gratz writes:
> Thorsten Jolitz writes:
>> when I try to use the new exporter outside of an Org buffer, e.g. from a
>> function or with M-:, it seems that there is a problem with the current
>> buffer that is used for exporting - it is not the buffer of the Org file
>> given as argument.
>
Thorsten Jolitz writes:
> when I try to use the new exporter outside of an Org buffer, e.g. from a
> function or with M-:, it seems that there is a problem with the current
> buffer that is used for exporting - it is not the buffer of the Org file
> given as argument.
You should read the docstrin
Hi list,
when I try to use the new exporter outside of an Org buffer, e.g. from a
function or with M-:, it seems that there is a problem with the current
buffer that is used for exporting - it is not the buffer of the Org file
given as argument.
I think the problem is here (line 2319 of org-exp
27 matches
Mail list logo
