ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Idris Samawi Hamid" <ishamid@colostate.edu>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: tex live and context
Date: Thu, 22 Feb 2007 10:22:33 -0700	[thread overview]
Message-ID: <op.tn5ujvzcnx1yh1@ihamid.libarts.colostate.edu> (raw)
In-Reply-To: <4CB783E5-4708-4B1B-9D12-FFD738C53DFC@uni-bonn.de>

Hi Thomas,

On Thu, 22 Feb 2007 09:57:26 -0700, Thomas A. Schmitz  
<thomas.schmitz@uni-bonn.de> wrote:

> On Feb 22, 2007, at 5:40 PM, Idris Samawi Hamid wrote:
>
>>> after some testing taco and i found out that tl has recent map
>>> files but
>>> that there's a problem with rsync and time outs on large trees,
>>> which is
>>> why my local texlive copy is incomplete; so, it mostly depends on
>>> what
>>> snapshot one uses
>>
>> This is exactly why I stick with mswincontext.zip, to avoid
>> headaches like
>> this ;-)

> I sympathize, but I think you're a bit unfair here. If I understand
> Hans's mail right, he was not installing from the image, but rsyncing
> his trees with TeXLive, and that's where the error was. I've been
> running the development version for at least three months now (even
> when it still was called 2006...) and haven't had any troubles,
> especially wrt to fonts and packages.

Point taken, although for the record I finally abandoned TeXLive a couple  
of years ago or so because of headaches with getting ever-newer versions  
of ConTeXt working right, then there was aleph and...

> On a linux or OS X box, I would
> even recommend installing it alongside the minimal and switch between
> them to test things, but I have no idea if/how this is possible on
> winblows.

Well, there's setuptex.bat which allows this and I do have a XemTeX tree  
 from Fabrice. Maybe I'll update XemTeX and see what happens.

Best
Idris

-- 
Professor Idris Samawi Hamid
Department of Philosophy
Colorado State University
Fort Collins, CO 80523

Using Opera's revolutionary e-mail client: http://www.opera.com/mail/

  parent reply	other threads:[~2007-02-22 17:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-21 20:44 On tikz Idris Samawi Hamid
2007-02-21 20:49 ` Thomas A. Schmitz
2007-02-21 21:04   ` Idris Samawi Hamid
2007-02-21 21:16     ` Thomas A. Schmitz
2007-02-22 16:40       ` tex live and context Idris Samawi Hamid
2007-02-22 16:57         ` Thomas A. Schmitz
2007-02-22 17:17           ` luigi scarso
2007-02-22 18:09             ` Thomas A. Schmitz
2007-02-22 18:32               ` luigi scarso
2007-02-23  8:31             ` Hans Hagen
2007-02-23  8:32             ` Hans Hagen
2007-02-22 17:22           ` Idris Samawi Hamid [this message]
2007-02-22 20:38             ` Peter Münster
2007-02-22 21:01               ` Sanjoy Mahajan
2007-02-23  7:02                 ` Peter Münster
2007-02-23  8:34             ` Hans Hagen
2007-02-23  8:29           ` Hans Hagen
2007-02-21 21:06   ` PS Idris Samawi Hamid
2007-02-21 21:21     ` PS Idris Samawi Hamid
2007-02-21 21:49 ` On tikz Willi Egger
2007-02-21 22:01   ` Idris Samawi Hamid
2007-02-21 23:07     ` Aditya Mahajan
2007-02-22  8:59       ` luigi scarso
2007-02-22  9:00 tex live and context Hans Hagen
2007-02-22  9:58 ` 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=op.tn5ujvzcnx1yh1@ihamid.libarts.colostate.edu \
    --to=ishamid@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).