ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
Subject: texexec from parent directory
Date: Fri, 1 Sep 2006 01:20:27 -0400 (EDT)	[thread overview]
Message-ID: <Pine.WNT.4.63.0609010109410.3804@nqvgln> (raw)

Hi,

  I have the following project structure

base/
   |
   +--project.tex
   |
   +--product.tex
   |
   +--environment.tex
   +
  subdir/
     |
     +---component.tex


If I in subdir and texexec component it compiles fine. If I am in base 
and texexec subdir/component it works fine. However, if I am in the 
parent directory of base and

texexec base/subdir/component

it does not work as the environment file is not found. It seems that 
the search for files is taking place relative to the directory from 
where texexec is invoked, rather than relative to the directory where 
the file resides. Is there some way I can make the component file 
compile from the parent directory of base?

Thanks,
Aditya

             reply	other threads:[~2006-09-01  5:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-01  5:20 Aditya Mahajan [this message]
2006-09-02  7:24 ` Aditya Mahajan
2006-09-03  4:46   ` 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=Pine.WNT.4.63.0609010109410.3804@nqvgln \
    --to=adityam@umich.edu \
    --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).