Re: bug in new exporter

[Nicolas Goaziou <n.goaziou@gmail.com>]

Hello,

Nick Dokos <ndokos@gmail.com> writes:

> Nicolas Goaziou <n.goaziou@gmail.com> 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!]" :width "")
>>>
>>> when it doesn't crash.
>>
>> This bug should be fixed in maint. Thanks to both of you for identifying
>> it.
>>
>
> And also in master, correct? I can never remember who goes first.

Correct.

Basically, if current version is "a.b.c", a change in maint will appear
in "a.b.c+1" whereas a change in master will appear in "a.b+1".

> 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 name). The tex file looks OK and I can process it from the
> command line. I'll try to pin this down more precisely,

Problem probably comes from `org-latex-compile'.

> but do I understand correctly that the processing of the tex file
> should take place with the current working directory set to the
> directory of the org file?

Yes.


Regards,

-- 
Nicolas Goaziou