From: Carsten Dominik <carsten.dominik@gmail.com>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: fullpage.sty replacement [WAS: Problem with LaTeX snippets preview]
Date: Tue, 29 Sep 2009 09:38:14 +0200 [thread overview]
Message-ID: <553421F5-3BC3-4D27-A215-0CE745CF522A@gmail.com> (raw)
In-Reply-To: <6137.1254206901@gamaville.dokosmarshall.org>
Hi Nick,
On Sep 29, 2009, at 8:48 AM, Nick Dokos wrote:
> 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).
These are valid points!
However:
- Fullpage is a trivial ad very small package that only
changes margins. Even if it changes at some point, there is no
reason
for Org to follow this change.
- I'd like to have few dependencies if possible.
- People who use strike-through faces should know better :-)
Well, I know there are exceptions where this does make sense.
The bad thing about packages that are in some TeX distros, but not
in others, is that you have to start documenting these dependencies
on a system-by-system basis, and I'd rather not go there, if possible.
If soul.sty is a non-guaranteed dependency, we should document it.
Where?
Maybe I should make the use of soul.sty dependend on the use of strike-
through
stuff in the file....
- Carsten
next prev parent reply other threads:[~2009-09-29 7:38 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
2009-09-29 7:38 ` Carsten Dominik [this message]
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=553421F5-3BC3-4D27-A215-0CE745CF522A@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
/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).