ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "Idris Samawi Hamid" <ishamid@colostate.edu>
Subject: Re: Context 2006.01.09 released
Date: Tue, 10 Jan 2006 13:18:55 -0700	[thread overview]
Message-ID: <op.s26ipty0nx1yh1@walayah1.wildblue.com> (raw)
In-Reply-To: <43C2B60A.10302@virgilio.it>

Hi,

On Mon, 09 Jan 2006 12:14:18 -0700, Jilani Khaldi  
<jilani.khaldi1@virgilio.it> wrote:

> Is there a particular procedure (read sinple) to update MikteX (for  
> Windows) without breaking the already installed distribution? Or to wait  
> for a while until a MikTeX Update is ready?
> Thanks!

The best thing to do is install MiKTeX without ConTeXt support, and then  
extract cont-tmf.zip into
\texmf-local, then refresh the fndb. I don't know how often Christian  
updates ConTeXt so I can't speak to that-)

But in my experience, if you want to painlessly keep ConTeXt up to date,  
install your distro of choice without ConTeXt and just add it on yourself  
locally.

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/

  reply	other threads:[~2006-01-10 20:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-09 16:55 Taco Hoekwater
2006-01-09 19:14 ` Jilani Khaldi
2006-01-10 20:18   ` Idris Samawi Hamid [this message]
2006-01-10 23:38     ` Updating to Context 2006.01.09 Jilani Khaldi
2006-01-11  1:56       ` Idris Samawi Hamid
2006-01-11 11:26         ` Jilani Khaldi
2006-01-09 19:35 ` Context 2006.01.09 released VnPenguin
2006-01-09 22:52   ` Hans Hagen
2006-01-09 23:42     ` VnPenguin
2006-01-10  8:23       ` Taco Hoekwater
2006-01-10  9:05       ` Hans Hagen
2006-01-10  9:13         ` Taco Hoekwater
2006-01-10 17:50         ` VnPenguin
2006-01-10 22:05           ` 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.s26ipty0nx1yh1@walayah1.wildblue.com \
    --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).