From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
To: janerik.hagglof@bredband.net,
"mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: context minimals "path and directory structure" question
Date: Mon, 20 Oct 2008 13:16:20 +0200 [thread overview]
Message-ID: <6faad9f00810200416m5befac3eo3dbfa801ab42cd42@mail.gmail.com> (raw)
In-Reply-To: <1224490412.5955.21.camel@lundby>
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
___________________________________________________________________________________
next prev parent reply other threads:[~2008-10-20 11:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-20 8:13 Jan-Erik Hägglöf
2008-10-20 9:16 ` luigi scarso
2008-10-20 11:16 ` Mojca Miklavec [this message]
2008-10-20 13:18 ` Aditya Mahajan
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=6faad9f00810200416m5befac3eo3dbfa801ab42cd42@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.com \
--cc=janerik.hagglof@bredband.net \
--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).