ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Matthew Huggett" <mhuggett@zam.att.ne.jp>
Subject: texexec
Date: Mon, 9 Dec 2002 23:56:20 +0900	[thread overview]
Message-ID: <004401c29f93$22cfd550$0200a8c0@home> (raw)

Hi:

I just re-installed TeX (fpTeX) and I have a question about running texexec.
I've followed the instructions in the texexec manual--i.e., customized and
copied texexec.rme to texexec.ini-- but I still get the following error when
I run texexec:
     locating ini file : not found by kpsewhich
     locating ini file : not found by searching
     locating ini file : no environment variable set
     locating ini file : not found in own path
             warning : texexec.ini not found, did you read 'texexec.rme'?

the context/perltk directory is in my path. Any ideas as to what I'm
missing?

thanks in advance

Matt

             reply	other threads:[~2002-12-09 14:56 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-09 14:56 Matthew Huggett [this message]
2002-12-09 19:25 ` texexec Henning Hraban Ramm
  -- strict thread matches above, loose matches on Subject: below --
2006-05-04 22:03 texexec Hans Hagen
2006-05-04 23:59 ` texexec Jilani Khaldi
2006-05-05  6:10 ` texexec luigi scarso
2006-05-05 13:26 ` texexec Steve Grathwohl
2006-05-05 13:36 ` texexec Renaud AUBIN
2006-05-05 15:16   ` texexec Hans Hagen
2006-05-05 14:09 ` texexec Steve Peter
2006-05-06 23:01 ` texexec Aditya Mahajan
2006-05-07 18:14   ` texexec Hans Hagen
2006-05-07 18:34     ` texexec Aditya Mahajan
2006-05-07 21:15       ` texexec Hans Hagen
2006-05-08  0:37         ` texexec Aditya Mahajan
2006-05-07 19:10   ` texexec Hans Hagen
2006-05-07 19:29     ` texexec Aditya Mahajan
2006-05-07 19:13   ` texexec Hans Hagen
2006-05-07 19:30     ` texexec Aditya Mahajan
2006-05-07 21:53     ` texexec Mojca Miklavec
2006-05-15 22:55 ` texexec frantisek holop
2006-05-15 23:06   ` texexec Hans Hagen
2006-06-19 21:46 ` texexec John R. Culleton
2006-06-19 21:13   ` texexec Hans Hagen
     [not found] <Pine.LNX.4.44.0307012300450.9436-100000@twain.marshallward .net>
2003-07-02 18:08 ` Texexec Hans Hagen
2003-07-04 23:39   ` Texexec Marshall Ward
     [not found] <"from Raimund.Kohl"@freenet.de>
2003-06-12 13:18 ` texexec Raimund Kohl
2003-06-12 15:01   ` texexec Ed L Cashin
2003-06-14  9:30     ` texexec Hans Hagen
2003-06-14 11:27       ` texexec Siep Kroonenberg
2003-06-13 15:57   ` texexec Raimund Kohl-Fuechsle
2003-06-13 16:00   ` texexec Raimund Kohl
2003-06-12 13:04 texexec Raimund Kohl-Fuechsle
2001-02-10 19:02 texexec Giuseppe Bilotta
2001-02-11  8:23 ` texexec Marc van Dongen
2001-02-11 21:14 ` texexec Hans Hagen
2001-02-12 16:35 ` texexec Ed L Cashin
2001-02-12 18:48   ` texexec Taco Hoekwater
2000-02-08  6:16 TeXexec Dan Seracu
2000-02-08  8:33 ` TeXexec Gilbert van den Dobbelsteen
2000-02-08  9:33   ` TeXexec Dan Seracu
     [not found] <375383E9.3A6BF93E@wxs.nl>
1999-06-01 19:34 ` texexec David Arnold
1999-06-02  7:26   ` texexec Hans Hagen
1999-04-22 12:31 texexec Thomas Esser
1999-04-23  7:09 ` texexec Hans Hagen
1999-04-22 12:13 texexec Thomas Esser
1999-04-22 14:28 ` texexec Taco Hoekwater
1999-04-22  9:05 texexec Erik Frambach
1999-04-22 11:31 ` texexec Erik Frambach
1999-04-22 12:12 ` texexec Taco Hoekwater

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='004401c29f93$22cfd550$0200a8c0@home' \
    --to=mhuggett@zam.att.ne.jp \
    --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).