From: "Gary Pajer" <pajer@iname.com>
Subject: Re: Update failure: I'm losing my mind
Date: Fri, 12 Dec 2003 08:40:31 -0500 [thread overview]
Message-ID: <001701c3c0b5$836e18b0$01fd5644@playroom> (raw)
In-Reply-To: <Pine.SGI.4.58.0312120738260.92465@montigo.bio.dfo.ca>
> > warning : texexec.ini not found, did you read
'texexec.rme'?
> >
> > It's really not finding it. The thing that surprises me is that no-one
else
> > has mentioned this. That's why I keep thinking that I've done something
> > wrong.
>
> Maybe trying to run ConTeXt with MikTeX instead of using TeX Live 2003,
> or trying to run ConTeXt in a Win32 configuration that puts spaces in
> the paths?
[longish comments deleted]
Thanks for your comments, George.
FWIW, I don't have any spaces in my MiKTeX directory tree, but I do use the
default XP system for organizing document files, and that system does have a
lot of spaces (e.g., "Documents and Settings")
I'm not married to MiKTeX, so I can switch to fpTeX. Any comments?
From what I can tell, fpTeX has better ConTeXt integration, while MiKTeX has
a better system for keeping up to date.
Anything else?
-gary
next prev parent reply other threads:[~2003-12-12 13:40 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
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 [this message]
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='001701c3c0b5$836e18b0$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).