ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: Norbert Preining <preining@logic.at>
Cc: dev-context@ntg.nl, ntg-context@ntg.nl
Subject: Re: [dev-context] integrating context mkiv, luatex, and fmtutil, mktexlsr, etc
Date: Wed, 03 Oct 2007 15:28:23 +0200	[thread overview]
Message-ID: <470398F7.6090900@wxs.nl> (raw)
In-Reply-To: <20071003131856.GE3597@gamma.logic.tuwien.ac.at>

Norbert Preining wrote:

> Are these megabytes kept and are they useful for later runs? If yes,
> then it is ok to put them in a separate cache (I assume the stuff is
> useful, it is the font stuff).

not sure yet, maybe later; but there is a cache cleaner (i may even 
thrash by date and usage)

> Hmm, but if the caches would be in TEXMFTREE/lcache/ then the only thing
> necessary would be a change of
> 	TEXMFCNF
> referencing other trees.
> 
> (Sorry, only trying to understand the details ...)

sure, all depends on what the cache var is set too (too many variants so 
i play safe and hash (but i can make that piece configurable if needed)

the beta is on the website and on the ftp

Hans

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2007-10-03 13:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20071003110634.GA29863@gamma.logic.tuwien.ac.at>
     [not found] ` <47037E8C.7080907@wxs.nl>
2007-10-02 13:55   ` Call for test documents Norbert Preining
2007-10-02 14:48     ` [dev-context] " Hans Hagen
2007-10-03 11:15       ` Norbert Preining
2007-10-03 11:21         ` [dev-context] " Hans Hagen
     [not found]           ` <20071003074824.GW9324@gamma.logic.tuwien.ac.at>
     [not found]             ` <47037739.208@wxs.nl>
     [not found]               ` <20071003111038.GB29863@gamma.logic.tuwien.ac.at>
     [not found]                 ` <47037AF1.4020104@wxs.nl>
2007-10-03 12:21                   ` integrating context mkiv, luatex, and fmtutil, mktexlsr, etc Norbert Preining
2007-10-03 13:06                     ` Hans Hagen
2007-10-03 13:18                       ` [dev-context] " Norbert Preining
2007-10-03 13:28                         ` Hans Hagen [this message]
2007-10-03 11:31         ` [NTG-context] Call for test documents Taco Hoekwater

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=470398F7.6090900@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=dev-context@ntg.nl \
    --cc=ntg-context@ntg.nl \
    --cc=preining@logic.at \
    /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).