On Mon, Oct 20, 2008 at 10:13 AM, Jan-Erik Hägglöf wrote:
> Hello!
>
> I'm using  context-minimal version: 2008.10.01 19:13 and have a
> generally question.
>
> I'm writing several documents with similar structure and design and have
> collected all common settings in "settings.tex" like following:
>
> \startenvironment settings
> ...
> ...
> ...
> \stopenvironment
>
> and just do the usual invoking by
>
> in
>
> anything.tex
>
> \environment settings
>
> \starttext
> ...
> ...
> ...
> \stoptext
>
> I've installed the "minimals" structure in /home/$USER/context/... on my
> ubuntu 8.04 machine.
>
> Now to the question:
>
> Where in this "structure" do I place "settings.tex" so it can be found
> by context from anywhere in my document-structure?

Like Luigi said, texmf-local/tex/context/whatever might be the best
place in the tree.

> I suppose I should do something like "context --make" after placing the
> file.

mktexlsr for kpathsea and luatools --generate for mkiv.
Though some folders are searched even without putting them to database.

> If I do the usual upgrade what happens then?

The script doesn't touch texmf-local.

> Is there a more efficient way doing similar tasks, like writing a
> module?

You can also have "settings.tex" on top of all the folders that use
it. Plain file and module do not make much difference in such cases.

(For safety reasons, I prefer to have a copy of such files locally (in
folder where I process files). I never know when I switch computer and
forget to copy some files from some "global" folders.)

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

Reply via email to