From: "Eckhart Guthöhrlein" <eckhart.guthoehrlein@uni-bielefeld.de>
Subject: Re: new ConTeXt versions
Date: Wed, 25 Aug 2004 13:16:31 +0200 [thread overview]
Message-ID: <20040825111631.GA28109@cebitec.uni-bielefeld.de> (raw)
In-Reply-To: <EAA68A82-F685-11D8-87EF-000A95B9ADE2@uni-bonn.de>
On Wed, Aug 25, 2004 at 01:00:03PM +0200, Thomas A.Schmitz wrote:
> I just used Taco's new script (which I find wonderful, thanks so
> much!), and this made me realize a problem: the latest version of
> ConTeXt should have updated texexec to version 4.4 -- and it did, sort
> of. When I checked, it still said "texexec : TeXExec 4.0 - ConTeXt /
> PRAGMA ADE 1997-2004." I then realized that the new versions of the
> scripts sit in texmf/scripts/context, while the old versions (that are
> still being called by the binary texexec) reside in
> texmf/context/perltk. For the time being, I just copied them over (one
> could also put softlinks in there, I suppose), but I wonder if this
> behavior can be modified -- I coulnd't find anything in texexec.rme. My
> system is tetex on Mac OS X. Anyone else have the same problems?
Here is what I do to be sure that always my own (up-to-date) context is
being used instead of any (almost certainly older) one from a tex
distribution, on all machines I have to use.
- I have context in my private texmf tree in $HOME. By default, this
should be the first texmf being searched.
- I have links to texmf/scripts/context/xxx.pl etc in $HOME/bin (without
suffix pl). $HOME/bin comes first in the search path for executables.
To be sure to notice changes like the new location of the scripts, I
usually remove an existing context before installing a newer one.
Regards,
Eckhart
next prev parent reply other threads:[~2004-08-25 11:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 7:28 Announcing a new script: TeXVersion Taco Hoekwater
2004-08-25 9:05 ` Maurice Diamantini
2004-08-25 10:03 ` Hans Hagen
2004-08-25 11:00 ` new ConTeXt versions Thomas A.Schmitz
2004-08-25 11:16 ` Eckhart Guthöhrlein [this message]
2004-08-25 11:25 ` Hans Hagen
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=20040825111631.GA28109@cebitec.uni-bielefeld.de \
--to=eckhart.guthoehrlein@uni-bielefeld.de \
--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).