ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Matt Gushee <mgushee@havenrock.com>
Subject: Re: Two texexec.ini files?
Date: Tue, 29 Jun 2004 15:35:04 -0600	[thread overview]
Message-ID: <20040629213504.GA30844@swordfish> (raw)
In-Reply-To: <275296B1-CA11-11D8-B8D0-0030659899AA@fiee.net>

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!

-- 
Matt Gushee                 When a nation follows the Way,
Englewood, Colorado, USA    Horses bear manure through
mgushee@havenrock.com           its fields;
http://www.havenrock.com/   When a nation ignores the Way,
                            Horses bear soldiers through
                                its streets.
                                
                            --Lao Tzu (Peter Merel, trans.)

  reply	other threads:[~2004-06-29 21:35 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 [this message]
2004-06-30  7:47     ` Hans Hagen
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=20040629213504.GA30844@swordfish \
    --to=mgushee@havenrock.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).