ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Subject: Re: components and figure search paths
Date: Wed, 10 May 2006 16:09:23 +0100	[thread overview]
Message-ID: <E1FdqJX-0002sb-00@skye.ra.phy.cam.ac.uk> (raw)
In-Reply-To: Your message of "Wed, 10 May 2006 16:38:06 +0200." <4461FACE.7050001@wxs.nl>

> so how is this component, when run on itself, supposed to locate itself, 

Not sure I completely understand your question.  But if I run one
component, I change to its directory first:

  cd chap/1 && texexec c_ch1.tex

Or is the canonical method:

  texexec chap/1/c_ch1.tex 

?

I've been in the habit of not doing it this way with tex tools, since
(la/pdf)tex put the generated files in the current directory instead
of in the directory of the source file.

> - how does the dir structure look

./chap/1/abc-1.eps
./chap/1/c_ch1.tex
./project_books.tex
./env_books.tex
./onebook.tex

> - where did you put the file

It's in chap/1/ (along with the eps figure)

> - where did you run it

I ran 'texexec onebook' in the ./ directory.

Running the component works fine (if I cd to its directory first),
because abc-1.eps is easy to find.

-Sanjoy

`Never underestimate the evil of which men of power are capable.'
         --Bertrand Russell, _War Crimes in Vietnam_, chapter 1.

  reply	other threads:[~2006-05-10 15:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-10  2:46 Sanjoy Mahajan
2006-05-10 11:25 ` Hans Hagen
2006-05-10 12:56   ` Sanjoy Mahajan
2006-05-10 13:31     ` Hans Hagen
2006-05-10 14:17       ` Sanjoy Mahajan
2006-05-10 14:38         ` Hans Hagen
2006-05-10 15:09           ` Sanjoy Mahajan [this message]
2006-05-10 15:13           ` David Arnold
2006-05-11  4:29             ` Sanjoy Mahajan
2006-05-11  5:21               ` 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=E1FdqJX-0002sb-00@skye.ra.phy.cam.ac.uk \
    --to=sanjoy@mrao.cam.ac.uk \
    --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).