Hello, Marcin Borkowski <mb...@wmi.amu.edu.pl> writes:
> Also, taking into account the number of problems with wasysym's > conflicts, I'd suggest dropping it (and maybe several other packages) > from it. That would break, among other things, previewing of LaTeX snippets. On the other hand, it's probably safe to remove "longtable" package since we don't provide other table packages supported by the latex export back-end. Also, we may pass the "nointegrals" option by default to wasysym. > Further, this seems to be a bit of work - I can't promise > anything /now/ - but I'll try to look into it and check which package > is needed for which entity; loading a big package for a few commands > might be an overkill. IIRC it has been done already. The document is somewhere in Worg. > Would it be possible for the LaTeX exporter to include some packages > only if they are really needed, i.e., if some entity is actually used > in the document? This would both speed up compilation time and (maybe > more importantly) reduce the risk of such conflicts. (Not to mention > the inelegance of a large preamble consisting of loading unnecessary > packages - as a person responsible for converting LaTeX files sent to > a journal by people into something usable/compilable/good-looking, > I can say that one of the first things I usually do is to delete /all > \usepackage's/ from the preamble, and see if it compiles correctly. In > more than 50% cases, it does... It has been suggested on this list already. Aaron Ecay even provided a patch. I think this is calling for problems as it cannot be totally reliable (and the time necessary to do this would probably defeat the compilation gain). On the other hand, you can define your own optimized preamble with `org-latex-classes' while the default setup still provides a (somewhat) smooth experience for the casual LaTeX user. Regards, -- Nicolas Goaziou
