From: contact@thomas-corbiere.name
To: <ntg-context@ntg.nl>
Subject: Project structure and path evaluation
Date: Thu, 25 Apr 2013 14:10:51 +0200 [thread overview]
Message-ID: <62c1776ecede63917560b3a644307f41@thomas-corbiere.name> (raw)
Hello,
I am experimenting with the project structure
feature of ConTeXt and so far it seems that paths
used with \project, \product and \component are relative
to the current working directory of the context program.
What I am doing right now, I use paths relative to my
project file "project.tex".
project.tex:
\startproject proj
\product product1/product.tex
\product product2/product.tex
\stopproject
product1/product.tex:
\startproduct prod1
\component product1/components/component1.tex
% I would like to use "components/component1.tex"
% that is a path relative to the current file
\stopproduct
This is really annoying as it makes it difficult to organize
files into directories. I would like the path to be relative
to the file containing the command. I tried \usepath[{.}]
without success. So, is this possible in ConTeXt?
Also, at the end of the PDF on project structure there is
an example with \startdocument ... \stopdocument. But I don't
understand where I should use these commands. From the source,
it looks like \starttex ... \stoptext with the ability to register
a before and after command. I am under the impression that I have
to choose between using :
- the project structure (project, product and component)
- the \startdocument and \stopdocument commands
- the \starttex and \stoptext commands
But that I should not mix them together. Is this right?
Regards,
Thomas Corbière
___________________________________________________________________________________
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:[~2013-04-25 12:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=62c1776ecede63917560b3a644307f41@thomas-corbiere.name \
--to=contact@thomas-corbiere.name \
--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).