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 13:03:21 -0400 [thread overview]
Message-ID: <8072.1254243801@alphaville.usa.hp.com> (raw)
In-Reply-To: Message from Carsten Dominik <carsten.dominik@gmail.com> of "Tue, 29 Sep 2009 09:38:14 +0200." <553421F5-3BC3-4D27-A215-0CE745CF522A@gmail.com>
Carsten Dominik <carsten.dominik@gmail.com> wrote:
> 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.
Agreed - it was more "the principle of the thing" rather than this
particular change.
>
> - I'd like to have few dependencies if possible.
>
Agreed - but there are going to be dependencies anyway.
> - People who use strike-through faces should know better :-)
> Well, I know there are exceptions where this does make sense.
>
Agreed with this too - but soul.sty is included unconditionally
so you get the dependency even if you are on the side of the angels.
> 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.
>
That's why I think we should document it at the level of latex packages:
we can then point people to CTAN as the last resort. A blurb like this
perhaps:
"Your distro may provide a package for this (e.g. on Debian/Ubuntu,
soul.sty is in the package texlive-latex-extra), but that varies greatly
from distro to distro, so you are on your own. Alternatively, you can
look for it on ctan.org: most LaTeX packages can be found there, but the
installation is more complicated; a description can be found at <here
comes a link>, but you will have to resolve problems on your own."
> If soul.sty is a non-guaranteed dependency, we should document it.
> Where?
Perhaps a new Dependencies section in the manual that gathers up
dependencies of the various exporters, as well as the preview stuff and
anything else that fits. Maybe keep it online, so people can update it,
and have the manual point to it. Give me a week or so to work on the
latex part and see whether it seems helpful.
> Maybe I should make the use of soul.sty dependend on the use of
> strike- through stuff in the file....
The trade-off is of course added complexity, but if you are willing
to suffer the pain, who am I to dissuade you? :-)
Thanks,
Nick
next prev parent reply other threads:[~2009-09-29 17:04 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
2009-09-29 17:03 ` Nick Dokos [this message]
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=8072.1254243801@alphaville.usa.hp.com \
--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
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).