ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Martin 'golodhrim' Scholz <scholz.m82@googlemail.com>
Subject: Re: context mkiv metafun
Date: Sat, 06 Feb 2010 01:11:49 +0100	[thread overview]
Message-ID: <4B6CB3C5.6010404@wxs.nl> (raw)
In-Reply-To: <hkibn0$497$1@ger.gmane.org>

On 6-2-2010 1:04, Martin 'golodhrim' Scholz wrote:
> On Sat, 06 Feb 2010 00:50:43 +0100, Hans Hagen wrote:
>
>> On 5-2-2010 21:40, Martin 'golodhrim' Scholz wrote:
>>
>>> Ok problem solved... missing rights to write to
>>> /opt/context-minimals/tex/ texmf-cache/, just chmoded it 777 so it will
>>> be usable for graphic generation. Would be nice to include the
>>> possibilty to add in a standard way a personal texmf-cache, or is there
>>> a way to do so and I don't know about it?
>>
>> grep for texmfcnf.lua
>>
>> this is a prelude to a replacement for texmf.cnf in mkiv
>>
> Ok got this file Hans, and what would be a good replacement in there?
>
> would it be ok to something like
>
> return {
> 	TEXMFCACHE = '~/.context-minimals/texmf-cache',
> }
> ok or is it possible to use multiple paths in that syntax like:

sure. you probably need to run "luatools --generate" after a change

> return {
> 	TEXMFCACHE = 'Path1', 'Path2'
> }
> unfortunately on this point there is no documention I can find.
> Thanks for your fast help Hans

no, for the moment just one cache path (maybe in the future more but it 
is sort of tricky as quite some version testing has to be done then so 
it's not a good idea to implement that while mkiv is in flux

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  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________


  reply	other threads:[~2010-02-06  0:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05  9:33 Martin 'golodhrim' Scholz
2010-02-05 17:43 ` Hans Hagen
2010-02-05 20:10   ` Martin 'golodhrim' Scholz
2010-02-05 20:23   ` Martin 'golodhrim' Scholz
2010-02-05 20:40     ` Martin 'golodhrim' Scholz
2010-02-05 23:50       ` Hans Hagen
2010-02-06  0:04         ` Martin 'golodhrim' Scholz
2010-02-06  0:11           ` Hans Hagen [this message]
2010-02-06  0:42             ` Martin 'golodhrim' Scholz
2010-02-05 23:48     ` 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=4B6CB3C5.6010404@wxs.nl \
    --to=pragma@wxs.nl \
    --cc=ntg-context@ntg.nl \
    --cc=scholz.m82@googlemail.com \
    /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).