From: "Gary Pajer" <pajer@iname.com>
Subject: Re: Update failure: I'm losing my mind
Date: Thu, 11 Dec 2003 09:08:40 -0500 [thread overview]
Message-ID: <000901c3bff0$47ece6b0$01fd5644@playroom> (raw)
In-Reply-To: <332181496.20031211104725@iol.it>
> Thursday, December 11, 2003 Gary Pajer wrote:
>
> > MiKTeX.
>
> > I've done this half a dozen times. This time it doesn't work. I feel
> > stupid. What have I forgotten?
>
> > Things were working perfectly. I decide to update, so I download
> > cont-tmf.zip to \localtexmf. Then I unzip, overwritting all the old
files.
> > Then I update the database either using mktexlsr or the MiKTeX options
> > wizard.
>
> > But now texexec can't find texexec.ini. But it's there, in
> > \localtexmf\context\config (as well as \texmf\context\config)
>
> > BTW, if I execute kpsewhich texexec.ini it returns without an error,
but
> > also with no information. Is that right?
>
> Yes, and that's the problem. Recent ConTeXts are too strongly
> tied to fpTeX :\
>
> One thing you can do: move your texexec.ini in the same folder
> as texexec.pl
Thanks, but that didn't work. I still have a nagging feeling that I'm
forgetting something simple.
MiKTeX comes with a texexec.exe. Putting texexec.ini in the same directory
doesn't do it either.
Is there an environment variable that I can set to help texexec find its
way?
Or a command line switch? (I have not found mention of either in the docs)
(Putting texexec.ini in the directory containing the ConTeXt .tex script
works.)
-gary
next prev parent reply other threads:[~2003-12-11 14:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20031209110008.9614.2387.Mailman@ref.ntg.nl>
2003-12-09 15:43 ` quiz olivier Turlier
2003-12-11 5:51 ` Update failure: I'm losing my mind Gary Pajer
2003-12-11 9:47 ` Giuseppe Bilotta
2003-12-11 14:08 ` Gary Pajer [this message]
2003-12-11 15:02 ` Re[2]: " Giuseppe Bilotta
2003-12-13 2:58 ` Gary Pajer
2003-12-13 11:48 ` Re[4]: " Giuseppe Bilotta
2003-12-11 17:27 ` Henning Hraban Ramm
2003-12-11 20:50 ` Gary Pajer
2003-12-12 12:05 ` George N. White III
2003-12-12 13:40 ` Gary Pajer
2003-12-12 14:11 ` Peter Rolf
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='000901c3bff0$47ece6b0$01fd5644@playroom' \
--to=pajer@iname.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).