emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Marcin Borkowski <mbork@wmi.amu.edu.pl>
Cc: emacs-orgmode@gnu.org
Subject: Re: Error with \usepackage{amsmath} due to \iint already being defined
Date: Fri, 24 May 2013 21:39:08 +0200	[thread overview]
Message-ID: <87a9nk6ucj.fsf@gmail.com> (raw)
In-Reply-To: <20130524210106.29cc01b7@aga-netbook> (Marcin Borkowski's message of "Fri, 24 May 2013 21:01:06 +0200")

Hello,

Marcin Borkowski <mbork@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

  reply	other threads:[~2013-05-24 19:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-24 17:04 Error with \usepackage{amsmath} due to \iint already being defined John Hendy
2013-05-24 17:22 ` Vincent Beffara
2013-05-24 17:35   ` John Hendy
2013-05-24 18:26     ` Marcin Borkowski
2013-05-24 18:38     ` Nick Dokos
2013-05-24 19:01       ` Marcin Borkowski
2013-05-24 19:39         ` Nicolas Goaziou [this message]
2013-05-25 12:59       ` Suvayu Ali

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a9nk6ucj.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mbork@wmi.amu.edu.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).