From: Aditya Mahajan <adityam@umich.edu>
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 09:18:23 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.1.00.0810200905580.1178@nqv-yncgbc> (raw)
In-Reply-To: <1224490412.5955.21.camel@lundby>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1745 bytes --]
On Mon, 20 Oct 2008, Jan-Erik Hägglöf wrote:
> Where in this "structure" do I place "settings.tex" so it can be found
> by context from anywhere in my document-structure?
For files which are specific to one or two projects, I usually place them
in the directory:
main-dir/
|
+---- settings.tex
|
+---- project-1/
| |
| +--- component-1-1.tex
|
+---- project-2/
and then in component-1-1.tex, put
\environment settings
There is no need to tell the relative path to context. When context cannot
find a file in the current dir, it looks up two (or three?) levels to find
the file.
As Mojca said, this has the added advantage of making the structure
self-sufficient. You can just copy the main-dir on a different computer
and everything works.
For files that are used in many different projects, I usually make it a
module (if you are not using any advanced features, like localenvironments
or setupmodules, modules and environments are the same)
I have created a directory texmf-local/tex/context/aditya where I put all
my files (and sync them to a svn server so that I can use them on
different computers).
> I suppose I should do something like "context --make" after placing the
> file. If I do the usual upgrade what happens then?
You make need to run luatools --generate (or texhash if using mkii) if
place the files in texmf-local. To prevent any accidents with upgrades,
create a directory in texmf-local/tex/context that is unique. You can also
create the directory in $TEXMFHOME/tex/context (which is usually
$HOME/tex/context in *nix systems, I do not know about win/mac). Normally
upgrades do not touch anything in $TEXMFHOME.
Aditya
[-- Attachment #2: Type: text/plain, Size: 487 bytes --]
___________________________________________________________________________________
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
___________________________________________________________________________________
prev parent reply other threads:[~2008-10-20 13:18 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
2008-10-20 13:18 ` Aditya Mahajan [this message]
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=alpine.DEB.1.00.0810200905580.1178@nqv-yncgbc \
--to=adityam@umich.edu \
--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).