h...@heagren.com writes: > Attached is a patch adding a new option > `org-latex-default-class-options'. The option can be set locally (file > locally, buffer locally, etc.) to effect the options which are > interpolated in LaTeX exports by default. > > This might not seem terribly useful: if you want to have > standard/common options set for a certain class (or even all classes) > just specify them in the header string in `org-latex-classes'. This is > usually sufficient, but not always. > > I have recently been using the LaTeX subfiles package a lot, with org > mode. The package lets your compile multi-file projects in convenient > ways, but (in order to do this) requires that: 1. each subfile uses > the `subfile' class, 2. with the path of the master file passed as an > argument
I have no specific objections to adding a defcustom, but I am wondering why not using #+INCLUDE directive and adding all the export settings that way? For the patch, please add ORG-NEWS entry. > +(defcustom org-latex-default-class-options "" > + "The defailt options passed to the document class." > + :group 'org-export-latex > + :type '(string :tag "LaTeX class") > + :safe #'stringp) Here, what does "LaTeX class" mean? Also, :package-version is missing. -- Ihor Radchenko // yantar92, Org mode maintainer, Learn more about Org mode at <https://orgmode.org/>. Support Org development at <https://liberapay.com/org-mode>, or support my work at <https://liberapay.com/yantar92>
