Hello, Charles Millar <mill...@verizon.net> 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 will export with the subheading :EXPORT_FILE_NAME: > /foo/baz, which does generate a short document named /foo/baz.pdf > > Should we be able to apply the new #+EXPORT_FILE_NAME: to a subheading > or does it work only for an entire buffer? As every keyword (i.e., #+KEYWORD syntax), it applies to the whole document. However export properties (i.e., :PROPERTY: syntax) override them. > Org mode version 9.0.2 (release_9.0.2-132-gc130b2 @ > /usr/local/share/emacs/site-lisp/org-mode/lisp/) > GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.5) of > 2015-03-07 on trouble, modified by Debian > > 2. An editorial suggestion for the realted ORGNEWS item which > currently reads: > > Simiralry to ~:EXPORT_FILE_NAME:~ property, this keyword allow to > specify the name of the output file upon exporting the document. This > has also an effect on publishing. > > be changed along the following lines? > > 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. Regards, -- Nicolas Goaziou
