Re: [O] [PATCH] Let =`make'= be an option to =`org-latex-pdf-process'=.

[Suvayu Ali]

On Wed, Jul 03, 2013 at 02:22:40PM +0800, Feng Shu wrote:
> Suvayu Ali <address@hidden> writes:
> 
> > On Wed, Jul 03, 2013 at 07:09:35AM +0800, feng shu wrote:
> >> Customize  `org-latex-pdf-process isn't very convenient.
> >> Is it possible add a  feature like: #+LATEX_PDF_PROCESS:  latexmk
> >> or add  #OPTIONS:  ;latex_pdf_process  latexmk
> >
> > If you don't mind my chiming in, the standard way to customise Emacs
> > behaviour (across all modes, not just Org) is through
> > customize-variable.  Org cannot keep on introducing new keywords just
> > because of convenience.
> 
> I don't think so, Convenience is very important in most situation. we can
> introduce new keywords just for convenience!  #+LATEX_CLASS is a good example,
> If we don't want convencience.  we can just customize `org-latex-default-class

There is a big difference between the two variables.  Consider this:
org-latex-classes depends per document (most likely you wand different
documents for different things, hence maybe you also want different
classes), however you want to choose your LaTeX backend once (at most it
varies from project to project).  But again, if you use one build system
for a project you are most likely using the same build system in other
projects too.  The only difference I can see is when you have something
like make for projects, but simply LaTeX for a simple document/notes.
In that case, I would say Bastien's suggestion to use file local
variables is best suited.  At one point I used something like this
headline at the end of few Org files:

* COMMENT local setup                                               :ARCHIVE:

# Local Variables:
# org-latex-to-pdf-process: ("xelatex -interaction nonstopmode 
-output-directory %o %f" "xelatex -interaction nonstopmode -output-directory %o 
%f" "xelatex -interaction nonstopmode -output-directory %o %f")
# End:

Hope this helps,

-- 
Suvayu

Open source is the future. It sets us free.