ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Alan Bowen <acbowen@princeton.edu>
Subject: Re: updating ConTeXt with ctxtools
Date: Wed, 09 Aug 2006 13:36:08 -0400	[thread overview]
Message-ID: <A8333C13-2A08-45F3-80BB-236DA419643F@princeton.edu> (raw)
In-Reply-To: <E1GAYYX-0005Pu-00@skye.ra.phy.cam.ac.uk>

On Aug 8, 2006, at 4:52 PM, Sanjoy Mahajan wrote:

>> In any case, I have probably misunderstood the thread. Has a summary
>> been posted somewhere that I might consult?
>
> I need to summarize all the Linux installation methods on the Wiki,
> once I get it all straight in my head.  Right now in reality and in my
> head it's a nightmare because of all the flavors (texlive, tetex 2 or
> 3, etc.) and the gazillion map files that could be anywhere.  ConTeXt
> tries to work everywhere so it has a hard life.
>
> I don't know much about what MacOS X does, but if you're not using a
> graphical installation method, it should be like BSD 4.[0123] Unix
> that I once used.  In which case it should work mostly like Linux.
>
> Here's what I do now and did just half hour ago to update to the
> 2006.08.08 version.  I use bash (a mostly sh-compatiable shell), which
> the MacOS terminal runs too I think.  The $ below is my bash prompt
> and everything after it is what I type:
>
>   $ TEXMFLOCAL=/home/sanjoy/texmf texmfstart ctxtools --updatecontext
>
> This fixes the problem that ctxtools uses (I think) Windows quoting in
> this source line:
>
>             tree = `kpsewhich --expand-path $TEXMFLOCAL`.chomp  
> rescue nil
>
> In Unix ruby (like in Perl) the $TEXMFLOCAL is expanded by the shell
> because of the $, and the result is run by the backticks.  Usually
> TEXMFLOCAL has no setting in the shell or environment so ruby runs the
> command with $TEXMFLOCAL replaced by an empty string, giving:
>
>    kpsewhich --expand-path
>
> So kpsewhich complains that it didn't get an argument for
> --expand-path (or --expand-var).  The long-term fix is to figure out
> how to quote that works in Windows and Unix, but I don't know how
> since I don't use Windows.
>
> The short-term hack is to set TEXMFLOCAL just while running ctxtools,
> which is done by the command above that I run.
>
> So maybe try that using the vanilla distribution (so with \012
> restored) and report back what happens and let's see if we can find a
> fix if something else doesn't work.  My computers run Linux but my
> partner has a MacOS 10.3 machine and I'll use it for ConTeXt
> experiments if needed.
>
> -Sanjoy

Sanjoy—

Since I use the teTeX distribution on my Mac, I ran
TEXMFLOCAL=/usr/local/teTeX/share/texmf.local sudo texmfstart  
ctxtools --updatecontext
in Terminal (bash) and the update went perfectly.

Many thanks!

Alan

      parent reply	other threads:[~2006-08-09 17:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-06 13:16 Alan Bowen
2006-08-06 13:39 ` Sanjoy Mahajan
2006-08-08 20:19   ` Alan Bowen
2006-08-08 20:52     ` Sanjoy Mahajan
2006-08-08 21:14       ` Hans Hagen
2006-08-09 17:36       ` Alan Bowen [this message]

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=A8333C13-2A08-45F3-80BB-236DA419643F@princeton.edu \
    --to=acbowen@princeton.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).