From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
Subject: Re: updating ConTeXt to latest on openbsd-current
Date: Mon, 6 Mar 2006 23:04:03 +0100 [thread overview]
Message-ID: <E60D218D-0892-4C6A-99D4-07B98D3DDEE5@uni-bonn.de> (raw)
In-Reply-To: <20060306211742.GN21773@obiit.org>
On Mar 6, 2006, at 10:17 PM, frantisek holop wrote:
> hi there,
>
> i am a (somewhat) long time pdflatex user and i am trying to
> convert to
> ConTeXt.
That's good, welcome to the ConTeXt community. I'm sure you'll like
it around here...
I'll try and answer some of your questions:
>
> shell_escape = t
>
> if it isn't already.
>
> --\stopquote----------------------------------------------------
>
> in the default openbsd package this line says:
>
> shell_escape = f
>
> what is the difference? and what is it for anyway?
> some external execution of the legends are true? :)
>
Among other things, ConTeXt has wonderful integration for an
implementation of Metapost called Metafun. If you set shell escape to
"t," ConTeXt will be able to compile Metafun code that is included in
your documents. this is a security issue when you're on a system with
many users; if you;re running it on your own personal computer, it is
safe to set this to true.
> kpathsea: Running mktexmf ec-lmr12
> ! I can't find file `ec-lmr12'.
> <*> ...ljfour; mag:=1; nonstopmode; input ec-lmr12
This is the old Latin-Modern bug that is a recurring event on this
list. Download the file cont-lmt.zip from the pragma website, unzip
it in your texmf-tree, run texhash, and this should solve your
problems on this front.
HTH, you'll certainly receive more answers.
Thomas
prev parent reply other threads:[~2006-03-06 22:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-06 21:17 frantisek holop
2006-03-06 22:01 ` Taco Hoekwater
2006-03-06 22:04 ` Thomas A. Schmitz [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E60D218D-0892-4C6A-99D4-07B98D3DDEE5@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).