Hi Nicolas,
Thank you for your comments on this patch. I appreciate your concerns
about the ordering of packages – this was something I had not considered
fully. I have reworked the implementation; I think it is now simpler
and more robust. Instead of a new customization variable, I’ve added a
Hello Aaron,
On Wed, Feb 20, 2013 at 11:02:21PM -0500, Aaron Ecay wrote:
Hello,
The current way that org handles LaTeX packages for export isn’t
optimal. The org-latex-(default-)packages-alist variables define a set
of packages that are loaded always. If a user wants to use advanced
Hello,
Aaron Ecay aarone...@gmail.com writes:
The current way that org handles LaTeX packages for export isn’t
optimal. The org-latex-(default-)packages-alist variables define a set
of packages that are loaded always. If a user wants to use advanced
functionality (booktabs for nicer table
2013ko otsailak 21an, Nicolas Goaziou-ek idatzi zuen:
Obviously, if you need a package in every document you write, it
should go into `org-latex-packages-alist'.
I agree with this.
If you need occasional packages, they should go into
`org-latex-classes'. Adding a new class is cheap. For
Aaron Ecay aarone...@gmail.com writes:
2013ko otsailak 21an, Nicolas Goaziou-ek idatzi zuen:
If you need occasional packages, they should go into
`org-latex-classes'. Adding a new class is cheap. For example you can
create a class article-with-tikz. It also allows to include
arbitrary code
Hello,
The current way that org handles LaTeX packages for export isn’t
optimal. The org-latex-(default-)packages-alist variables define a set
of packages that are loaded always. If a user wants to use advanced
functionality (booktabs for nicer table export, listings or minted for
nicer source
