From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [export] Should sidewaystable option automatically add rotating package? Date: Thu, 12 Sep 2013 21:00:00 +0200 Message-ID: <87ob7xq30v.fsf@gmail.com> References: <87ob7z4nzl.fsf@pinto.chemeng.ucl.ac.uk> <877gentvmv.fsf@gmx.us> <87wqmmos25.fsf@gmail.com> <878uz151r5.fsf@pank.sbde-40904.btopenzone.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:33472) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VKC7Q-0006aM-CT for emacs-orgmode@gnu.org; Thu, 12 Sep 2013 15:00:02 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VKC7J-00079Z-2j for emacs-orgmode@gnu.org; Thu, 12 Sep 2013 14:59:56 -0400 Received: from mail-we0-x22a.google.com ([2a00:1450:400c:c03::22a]:52385) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VKC7I-00079S-RV for emacs-orgmode@gnu.org; Thu, 12 Sep 2013 14:59:48 -0400 Received: by mail-we0-f170.google.com with SMTP id w62so217395wes.15 for ; Thu, 12 Sep 2013 11:59:47 -0700 (PDT) In-Reply-To: <878uz151r5.fsf@pank.sbde-40904.btopenzone.com> (rasmus@gmx.us's message of "Thu, 12 Sep 2013 20:33:02 +0200") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Rasmus Cc: emacs-orgmode@gnu.org Rasmus writes: > It's tough. I've /never/ used neither wrapfig nor longtable. From a > totally subjective point-of-view I'd certainly want to remove it! > However, I wonder if this is the 'nicest' thing to do. Not everyone > cares about LaTeX and not everyone cares to look into LaTeX details. > > Three possibilities are > > - Just Work=E1=B5=80=E1=B4=B9 :: Include a lot of stuff in > `org-latex-default-packages-alist'. Self-proclaimed 'power > users' can cut it down themselves in their config. It could > slow down compilation, especially if policy is too lenient. > (E.g. to support tikz files you need to load TiKZ; To > support #+LANGUAGE you need to load babel). Perhaps we could > add an optional variable org-latex-load-all-relevant-packages > that loads all known packages that Org might depend on (assuming > they are all compatible). People with i7 processors can then > turn it on and we could include only basic package in the > default package alist. > > - RTM :: Be better at documenting when a feature requires an > additional package. This is probably my preferred > solution. > > I think Org can mostly guess when a LaTeX export failed. > If so, perhaps we could be give informative hints when > something fails. E.g. if rotation is required and > something fails, tell the user that the rotation package is > needed. I have no idea how much work this would be. > > - Do nothing :: People who use the LaTeX exporter should be > proficient enough with LaTeX and Org to solve their > own problems. > > On Eric's original idea about auto-including packages: I don't like. > I want to like it, but it's just too fragile. Some things depend on > being loaded in the correct order (e.g. hyperref needs to be towards > the end). Since people can load arbitrary code using #+LATEX_HEADER: > \input{=C2=B7} it's bound to break! I'm not talking about auto-including packages, nor do I suggest to include lot of stuff in `org-latex-default-packages-alist'. My point is: if "wrapfig" is there, "rotating" should accompany it, or both should be removed from the variable. Also, there's no reason for "longtable" to be included. IOW, I'm discussing a very practical point, not the general status of packages in the LaTeX export back-end. Regards, --=20 Nicolas Goaziou