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>
Subject: Re: Using the standalone ConTeXt, how do I add access to my texmf-local tree
Date: Fri, 06 Mar 2015 10:59:57 +0100	[thread overview]
Message-ID: <54F97A9D.4090709@wxs.nl> (raw)
In-Reply-To: <54F978EF.9070309@wxs.nl>

On 3/6/2015 10:52 AM, Hans Hagen wrote:

> we have a runtime tree search with:
>
>    context --path=tree://e:/tmp/whatever/**/ --global somefile.tex
>
> which is quite ok for jobs that involve not that many files
>
> and a cached-across-jobs search with
>
>    context --path=dirfile://e:/tmp/whatever --global somefile.tex
>
> (in that case you need to delete dirlist.tuc in the given path when you
> add or remove files)
>
> the second one we use here in automated runs on servers where books are
> generated from thousands of small files sitting on an nfs share and this
> speeds up the search
>
> the --global bypasses the check for a valid file

btw, this is explained in the recent workflow manual

-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | voip: 087 875 68 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:[~2015-03-06  9:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-01 10:48 Gerben Wierda
2015-03-01 10:59 ` Hans Hagen
2015-03-01 21:56   ` Gerben Wierda
2015-03-01 22:04     ` Wolfgang Schuster
2015-03-01 22:16       ` Gerben Wierda
2015-03-01 23:15         ` Wolfgang Schuster
2015-03-02  6:42           ` Gerben Wierda
2015-03-02  8:36             ` Hans Hagen
2015-03-04 13:52               ` Ulrike Fischer
2015-03-04 16:58                 ` Hans Hagen
2015-03-04 18:06                   ` Ulrike Fischer
2015-03-05  0:40                     ` Hans Hagen
2015-03-05  9:34                       ` Ulrike Fischer
2015-03-06  8:22               ` Procházka Lukáš Ing. - Pontex s. r. o.
2015-03-06  9:52                 ` Hans Hagen
2015-03-06  9:59                   ` Hans Hagen [this message]
2015-03-06 12:08                   ` Procházka Lukáš Ing. - Pontex s. r. o.
2015-03-06 13:45                     ` Hans Hagen
2015-03-06 14:14                       ` Procházka Lukáš Ing. - Pontex s. r. o.

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=54F97A9D.4090709@wxs.nl \
    --to=pragma@wxs.nl \
    --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).