From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
Subject: Re: does metafun require texexec --final?
Date: Sat, 23 Sep 2006 19:26:12 +0200 [thread overview]
Message-ID: <20060923192612.73c4f9c4.schuster.wolfgang@googlemail.com> (raw)
In-Reply-To: <E1GRAeW-0005W4-00@skye.ra.phy.cam.ac.uk>
On Sat, 23 Sep 2006 17:46:56 +0100
Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk> wrote:
> Wolfgang,
>
> Thanks for the pointer. I don't have a cont-sys.tex, but cont-sys.rme
> has these lines
>
> % \runMPgraphicstrue
> % \runMPTEXgraphicstrue
>
> The .rme extension meant I'd missed it when I ran grep on the .tex
> files. I'll uncomment them.
>
> Oh, that's not a good idea, because the next context update will
> overwrite cont-sys.rme. So I should copy cont-sys.rme to cont-sys.tex
> first, then uncomment the lines in cont-sys.tex. But then a context
> update will overwrite cont-sys.rme, and the new version will be
> ignored because I have a cont-sys.tex.
>
> So maybe the best approach is to edit cont-sys.rme directly, then
> merge changes (using a revision control system like mercurial or git)
> that arrive with the new context distributions.
>
> -Sanjoy
>
You could make a copy of cont-sys.rme and save it as cont-sys.tex
without problems.
The cont-sy.rme file is only loaded when ConTeXt can't find a
cont-sys.tex file on your system.
Don't bother about changes in the cont-sys.rme with a new ConTeXt
release, because the standalone Distribution for Windows comes with
both files and they have also differences. cont-sys.rme says
defaultencoding=ec and cont-sys.tex says defaultencoding=texnansi :-)
AFAIK this is somewhere mentioned in one of the manuals.
Wolfgang
next prev parent reply other threads:[~2006-09-23 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-23 4:48 Sanjoy Mahajan
2006-09-23 14:03 ` Sanjoy Mahajan
2006-09-23 16:16 ` Wolfgang Schuster
2006-09-23 16:46 ` Sanjoy Mahajan
2006-09-23 17:26 ` Wolfgang Schuster [this message]
2006-09-24 8:22 ` Mojca Miklavec
2006-09-24 8:37 ` Taco Hoekwater
2006-09-24 19:37 ` Hans Hagen
2006-09-25 19:32 ` Peter Münster
2006-09-26 10:05 ` Hans Hagen
2006-09-26 12:07 ` Sanjoy Mahajan
2006-09-27 10:10 ` Patrick Gundlach
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=20060923192612.73c4f9c4.schuster.wolfgang@googlemail.com \
--to=schuster.wolfgang@googlemail.com \
--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).