emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: [export] Should sidewaystable option automatically add rotating package?
Date: Thu, 12 Sep 2013 21:00:00 +0200	[thread overview]
Message-ID: <87ob7xq30v.fsf@gmail.com> (raw)
In-Reply-To: <878uz151r5.fsf@pank.sbde-40904.btopenzone.com> (rasmus@gmx.us's message of "Thu, 12 Sep 2013 20:33:02 +0200")

Rasmus <rasmus@gmx.us> 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ᵀᴹ ::  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{·} 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,

-- 
Nicolas Goaziou

  reply	other threads:[~2013-09-12 19:00 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-11 11:05 [export] Should sidewaystable option automatically add rotating package? Eric S Fraga
2013-09-11 12:01 ` Rasmus
2013-09-11 12:08   ` Eric S Fraga
2013-09-11 12:14     ` Carsten Dominik
2013-09-11 12:25       ` Rasmus
2013-09-11 15:24         ` Eric S Fraga
2013-09-11 12:30       ` Rainer M Krug
2013-09-12 17:42   ` Nicolas Goaziou
2013-09-12 18:33     ` Rasmus
2013-09-12 19:00       ` Nicolas Goaziou [this message]
2013-09-13  8:49         ` Sebastien Vauban
2013-09-12 19:22     ` Carsten Dominik
2013-09-13  8:01     ` Detlef Steuer
2013-09-15  4:49       ` Carsten Dominik
2013-09-15 14:02         ` Nicolas Girard
2013-09-16  8:08           ` Carsten Dominik
2013-09-16 10:47         ` Rasmus
2013-09-16 11:26           ` Rainer M Krug
2013-09-16 13:27           ` Carsten Dominik
2013-09-16 13:38             ` Carsten Dominik
2013-09-16 19:26             ` Rasmus
2013-09-16 20:21               ` Andreas Leha
2013-09-17  1:45               ` Eric Abrahamsen
2013-09-17  4:48                 ` Carsten Dominik
2013-09-17 13:24                   ` Rasmus
2013-09-18 13:18                     ` Carsten Dominik
2013-09-18 22:21                       ` Rasmus
2013-09-19  2:04                         ` Carsten Dominik
2013-09-19  9:11                           ` Rasmus
2013-09-19  9:28                             ` Carsten Dominik
2013-09-19  9:38                           ` Nicolas Girard
2013-09-19 11:05                             ` Carsten Dominik
2013-09-25  7:04                             ` Carsten Dominik
2013-09-25  7:45                               ` Nicolas Girard
2013-09-25  7:50                                 ` Carsten Dominik
2013-09-25  9:09                                 ` Rasmus
2013-09-26  8:51                                   ` Marcin Borkowski
2013-09-17 13:30                 ` Rasmus
2013-09-17  5:11 ` Carsten Dominik
2013-09-17  8:05   ` Eric S Fraga

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=87ob7xq30v.fsf@gmail.com \
    --to=n.goaziou@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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).