emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nick Dokos <nicholas.dokos@hp.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: fullpage.sty replacement [WAS: Problem with LaTeX snippets preview]
Date: Tue, 29 Sep 2009 02:48:21 -0400	[thread overview]
Message-ID: <6137.1254206901@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Carsten Dominik <carsten.dominik@gmail.com> of "Mon, 28 Sep 2009 22:10:51 +0200." <AF2BC4C7-B7FD-4012-9A34-A70016EA14F0@gmail.com>

My $0.02: 

Let me point out that a dependency on soul.sty was introduced in order
to deal with strike-through emphasis in the LaTeX exporter. And guess
where soul.sty resides (on Debian/Ubuntu): in the texlive-latex-extra
package. So it seems to me that replacing the use of the fullpage
package by its contents is not the best solution: it would be better to
document the dependency (and other such dependencies). Keeping the
dependency on fullpage.sty would also insulate org-mode from missing
future changes to it - however unlikely that event happens to be.

Also, the main difference between these two is that if soul.sty is not
present, then when you try to process the exported latex file, you get
an explicit error message that fingers the problem exactly, whereas
without fullpage.sty, the preview failed silently. If the latter failure
could be made visible, then the problem would be solved (and this
solution would cover other similar failures as well).

Thoughts?

Thanks,
Nick

next prev parent reply	other threads:[~2009-09-29  7:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-26 11:36 fullpage.sty replacement [WAS: Problem with LaTeX snippets preview] Tim Burt
2009-09-28 20:10 ` Carsten Dominik
2009-09-28 23:46   ` Tim Burt
2009-09-29  6:48   ` Nick Dokos [this message]
2009-09-29  7:38     ` Carsten Dominik
2009-09-29 17:03       ` Nick Dokos
2009-09-30  8:27         ` Carsten Dominik

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=6137.1254206901@gamaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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

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).