From: Alan Bowen <bowenalan03@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Project setup query
Date: Thu, 30 Apr 2020 09:07:11 -0400 [thread overview]
Message-ID: <CAFMOkGUCR-UR2NaV+jBq4kJH_LZ_NnK-_srBUV+WdNKG13JLng@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 982 bytes --]
This is a minor issue—to which I expect the answer will be simple,
something I should know by now but do not. I am just trying to see if I can
streamline a working directory.
In Directory01, I have a number of prd_NameXX.tex files as well as a
Directory02 which contains .tex files that are to be called on by each one
of the prd_Name.tex files.
Is there a way to identify the TEX root for each of the common files (in
Directory02) so that
the file will be processed when I process any one of the prd files in
Directory01?
I have tried
% !TEX root=../prd_\mystring.tex
with, e.g., \def\mystring{Name01} in the prd_Name01.tex file, but that does
not seem to work—the various .tex files re not found.
What puzzles me is that the environment files in Directory02 are found.
(That they are identified in a prj file in Directory01 does not seem to be
the reason why.)
There is no problem if I move the contents of Directory02 into Directory01.
Alan
[-- Attachment #1.2: Type: text/html, Size: 2306 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 bytes --]
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2020-04-30 13:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 13:07 Alan Bowen [this message]
2020-04-30 17:30 ` Henning Hraban Ramm
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=CAFMOkGUCR-UR2NaV+jBq4kJH_LZ_NnK-_srBUV+WdNKG13JLng@mail.gmail.com \
--to=bowenalan03@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).