From: ishamid <ishamid@lamar.colostate.edu>
Subject: RE: Upgrading...
Date: Tue, 15 Mar 2005 16:09:06 -0700 [thread overview]
Message-ID: <4248509B@webmail.colostate.edu> (raw)
> just download the windows zip file from our website and install that one
> in a separate tree, e.g. under
>
> c:\context
>
> then, you can initialize that tree with
>
> c:\context\setuptex c:\context
>
> and voila ...
Ok, I followed the above. Now I have two trees, c:\TeXLive and c:\ConTeXt
Issues:
1. I ``initialized'' the \ConTeXt tree and ran
texexec --make
but no aleph format, so a batch file is called:
cd C:\ConTeXt\texmf-mswin\web2c
aleph --ini *plain \dump
texexec --make en -tex=aleph
aleph --ini *cont-en
but...
C:\ConTeXt\texmf-mswin\web2c>aleph --ini *plain \dump
! aleph.pool doesn't match; otangle me again (or fix the path).
How do I get aleph working?
2. How do I get my OS to recognize/prioritize the C:\ConTeXt tree (when I call
texexec from my editor it still calls from c:\TeXLive)? Do I have to uninstall
ConTeXt from my c:\TeXLive path? What is the cleanest way to do that?
3. I presume that
\ConTeXt\texmf-local\web2c\texmf.cnf
is the one
texexec --make
uses. Have you already optimized/tested
\ConTeXt\texmf-local\web2c\texmf.cnf
for aleph (there were a few issues as you may recall...)?
Best
Idris
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523
next reply other threads:[~2005-03-15 23:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-15 23:09 ishamid [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-03-16 14:32 Upgrading ishamid
2005-03-16 1:10 Upgrading ishamid
2005-03-16 8:57 ` Upgrading Hans Hagen
2005-03-15 23:08 Upgrading ishamid
2005-03-16 9:02 ` Upgrading Hans Hagen
2005-03-05 17:33 Upgrading ishamid
2005-03-05 22:51 ` Upgrading h h extern
2005-03-15 18:38 ` Upgrading Idris Samawi Hamid
2005-03-16 21:14 ` Upgrading Hans Hagen
2005-03-17 10:48 ` Upgrading Patrick Gundlach
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=4248509B@webmail.colostate.edu \
--to=ishamid@lamar.colostate.edu \
--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).