From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Two texexec.ini files?
Date: Wed, 30 Jun 2004 09:47:04 +0200 [thread overview]
Message-ID: <40E26FF8.4040907@wxs.nl> (raw)
In-Reply-To: <20040629213504.GA30844@swordfish>
Matt Gushee wrote:
>On Tue, Jun 29, 2004 at 11:13:23PM +0200, Henning Hraban Ramm wrote:
>
>
>>>I have noticed that the ConTeXt distribution contains both
>>> $TEXMF/context/config/texexec.rme
>>>and
>>> $TEXMF/scripts/context/perl/texexec.rme
>>>Are they both supposed to be used? What happens if they're not the
>>>same?
>>>
>>>
>>This is a FAQ.
>>
>>
>
>Oops, sorry. Except ... is there a list of FAQs somewhere? I've never
>seen it.
>
>
>
>>They're both unused. You must rename or copy one to texexec.ini (I
>>prefer it in config).
>>
>>
>
>Yes, I knew they had to be copied. I take it, then, that texexec.ini can
>be in either of the above locations ... maybe anywhere accessible to
>kpathsea?
>
>Anyway, it's a bit confusing to have two texexec.rme files. I would
>suggest removing one of them from the distribution.
>
>Thanks for your reply!
>
>
The reason why there are two files is that in the new tds the scripts are now in a separate branch of the tree (scripts); in order to keep some downward compatibility (also with respect to expectations) i put two copies in the tree; the one in scripts will go away next year
(btw, you can use textools to move files to the new locations)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
next prev parent reply other threads:[~2004-06-30 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-29 19:55 Matt Gushee
2004-06-29 21:13 ` Henning Hraban Ramm
2004-06-29 21:35 ` Matt Gushee
2004-06-30 7:47 ` Hans Hagen [this message]
2004-06-30 16:41 ` Henning Hraban Ramm
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=40E26FF8.4040907@wxs.nl \
--to=pragma@wxs.nl \
--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).