Nicolas Goaziou writes:
>
>> Similar to ~:EPORT_FILE_NAME:~ property, this keyword allows the user
>> to specify the name of the output file upon exporting the document.
>> This also has an effect on publishing (or "This also effects
>> publishing."
>
> Of course. Thank you.
IMO, the alternative
Hello,
Charles Millar writes:
> Hi again,
>
>
> On 12/21/2016 04:32 AM, Nicolas Goaziou wrote:
>> Hello,
>>
>> Charles Millar writes:
>>
>>
>>> However, I tried to export a subheading with, e.g.
>>> #+EXPORT_FILE_NAME: /foo/baz,
>>> and
>>> the result is /foo/bar.pdf, not /foo/baz.pdf
>> Wh
Hi again,
On 12/21/2016 04:32 AM, Nicolas Goaziou wrote:
Hello,
Charles Millar writes:
However, I tried to export a subheading with, e.g.
#+EXPORT_FILE_NAME: /foo/baz,
and
the result is /foo/bar.pdf, not /foo/baz.pdf
Where does "bar" come from?
I was not clear. I should have shown
Hello,
Charles Millar writes:
> However, I tried to export a subheading with, e.g.
> #+EXPORT_FILE_NAME: /foo/baz,
> and
> the result is /foo/bar.pdf, not /foo/baz.pdf
Where does "bar" come from?
> This is not the same result that using the PROPERTIES construct in
> a subheading, which wi
Hi Nicolas
On 12/20/2016 11:17 AM, Nicolas Goaziou wrote:
Hello,
I just introduced #+EXPORT_FILE_NAME keyword, which allows to change the
output file name upon exporting a document.
Thank you and a couple of questions/observations
1. Exporting to pdf latex -
I used #+EXPORT_FILE_NAME: /foo
Hello,
I just introduced #+EXPORT_FILE_NAME keyword, which allows to change the
output file name upon exporting a document.
Regards,
--
Nicolas Goaziou0x80A93738