From: Andre Caldas <andre.em.caldas@gmail.com>
To: ConTeXt users <ntg-context@ntg.nl>
Subject: Search path.
Date: Sun, 9 Sep 2012 23:45:30 -0300 [thread overview]
Message-ID: <CADVh14UD2GuAWH7BKrmYibW-T8EfiJSpfHp260sOF-wLFoXsjg@mail.gmail.com> (raw)
Hello, list!
I am really new to ConTeXt. I am writing a book
http://topologia-geral.ourproject.org/
It is written in LaTeX and I intend to migrate it to ConTeXt.
I want to migrate and I want to be as far from HACKS as I can. So I
want to know the recommended way to do things. One of my first
difficulties comes from the "search path" used by texexec. It seems to
me that the path searched for components, products and environments
depends on the path were the script was called from. That is, it
depends on the "current working directory".
My question (honestly) is:
- Why would I want this behavior?
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?
Am I missing something?
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 reply other threads:[~2012-09-10 2:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-10 2:45 Andre Caldas [this message]
2012-09-10 7:09 ` Hans Hagen
2012-09-10 12:47 ` Andre Caldas
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=CADVh14UD2GuAWH7BKrmYibW-T8EfiJSpfHp260sOF-wLFoXsjg@mail.gmail.com \
--to=andre.em.caldas@gmail.com \
--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).