ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: first-setup for windows
Date: Wed, 26 Jan 2011 22:32:34 +0100	[thread overview]
Message-ID: <AANLkTimrV4H5fJN9oP6C29nsiUHSm0+0ZzCBM39xPfNe@mail.gmail.com> (raw)
In-Reply-To: <op.vpxn16ek8lgizc@lk-2008-nbk>

2011/1/26 Procházka Lukáš <lpr@pontex.cz>:
> Hello Mojca,
>
> I launched your modified first-setup.bat - it seems the latest Ctx version
> was updated successfully.

Thanks a lot for testing ...

> BTW: It normally happens to me that I have to run 'mtxrun --generate' after
> I updated Ctx.

(or that format generation breaks ...)

> So if you thought this would be useful (actually it may depend on whether an
> explicit 'mtxrun --generate' after update is necessary what I don't know -

It *is* necessary if some new files appear. The problem was that
usually the wrong mtxrun was called which had zero effect since it
possibly updated the cache in TeX Live or some other ConTeXt
distribution (under another path).

You can try the following:
- make sure that there is no tex in your path (set PATH ...)
- delete texmf-cache
- delete some files (for example context.mkiv and a few random other files)
- call first-setup.bat (the modified version that I sent you without
an explicit mtxrun --generate)
- call setuptex (or manually set PATH)
- try to compile some file

The mtxrun --generate at the end of script doesn't really help since
already the format generation is broken if some new files arrive.

Thanks,
    Mojca
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : http://www.pragma-ade.nl / http://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2011-01-26 21:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-26 19:31 Mojca Miklavec
2011-01-26 20:47 ` Procházka Lukáš
2011-01-26 21:32   ` Mojca Miklavec [this message]
2011-01-28  7:43     ` Procházka Lukáš Ing. - Pontex s. r. o.
2011-01-28 15:29       ` Mojca Miklavec
2011-01-28 15:57         ` Procházka Lukáš Ing. - Pontex s. r. o.
2011-01-28 16:06           ` Mojca Miklavec
2011-01-28 17:54           ` Hans Hagen
2011-01-27 10:23 ` Hans Hagen
2011-01-27 12:27   ` Mojca Miklavec

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=AANLkTimrV4H5fJN9oP6C29nsiUHSm0+0ZzCBM39xPfNe@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --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).