From: Andre Caldas <andre.em.caldas@gmail.com>
To: Hans Hagen <pragma@wxs.nl>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Search path.
Date: Mon, 10 Sep 2012 09:47:11 -0300 [thread overview]
Message-ID: <CADVh14WCtimsQF6TztEUz56U6eEVp8tnWRHOVnmxtwg_ohwLdg@mail.gmail.com> (raw)
In-Reply-To: <504D9228.9020807@wxs.nl>
>> When I write a project, product, component or environment file, why
>> would I want the references I made to be dependent on the directory
>> where the script was called? Shouldn't things be like the
>> #include "relative_path.h"
>> used in the C language, for example? That is, shouldn't those paths be
>> relative to the script that refers to them? [...]
>
> The way tex (and its path) are set up is that files are looked up on the
> current path (.) or relative to it, or in the (tds compliant) tex tree.
> Auxiliary files are created in the current directory.
I thought the reason was TeX itself. I just had some hope that ConTeXt
would "fix" this behavior some how. Since ConTeXt allows one to have
products and contents relatively independent from the project itself,
I thought that it would make sense to have the references to files
independent from the project structure as well.
Maybe I can just live with TEXINPUTS and BIBINPUTS... :-)
I guess the magic could be at some extent done with "\usepath".
Leaving the probably already extensively discussed "\usepath"
precedence order for another discussion...
> One can hardcode a path in the tex source if needed. Another option is to
> move to the source path (something texmfstart --path ... texexec ... or
> mtxrun --path ... --script context ...) but what's best depends on the kind
> of project.
I definitely prefer not to hard code paths in the source. Actually, I
would like the "components" to not have to worry at all about where
they live...
I will study texmfstart. :-)
> Do you really need to use context mkii? As it's a new project, using context
> mkiv might be a better idea.
No, I don't. I want to use always the preferred solution. I want to
follow your guidelines and be enlightened... :-)
How did you know I was using one and not the other? I didn't know it myself!!!
Thank you very much for your help and for this great piece of software, Hans.
André Caldas.
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2012-09-10 12:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 2:45 Andre Caldas
2012-09-10 7:09 ` Hans Hagen
2012-09-10 12:47 ` Andre Caldas [this message]
2012-09-10 13:13 ` Pontus Lurcock
2012-09-10 14:56 ` Aditya Mahajan
-- strict thread matches above, loose matches on Subject: below --
2005-05-06 4:33 Search Path Randall Skelton
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=CADVh14WCtimsQF6TztEUz56U6eEVp8tnWRHOVnmxtwg_ohwLdg@mail.gmail.com \
--to=andre.em.caldas@gmail.com \
--cc=ntg-context@ntg.nl \
--cc=pragma@wxs.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).