From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: project structure
Date: Sun, 27 Jul 2014 15:59:35 +0200 [thread overview]
Message-ID: <53D505C7.5080808@wxs.nl> (raw)
In-Reply-To: <op.xjnlyms8tpjj8f@lpr>
On 7/27/2014 1:24 PM, Procházka Lukáš Ing. - Pontex s. r. o. wrote:
> Hello,
>
> On Sat, 26 Jul 2014 11:01:15 +0200, Hans Hagen <pragma@wxs.nl> wrote:
>
>> Hi,
>>
>> There is a new experimental feature (one of the side effects of
>> discussions with Alan about bibliographies and using distributed files
>> in a project structure).
>>
>> Say that you have this:
>>
>> test1.tex : uses \component one/test2
>>
>> one/test2.tex : uses \component two/test3
>>
>> etc. There can be resources under one/two that test3 needs and one way
>> out is to add this path to the used paths. Doing that automatically can
>> result in side effects when multiple resources with the same name are
>> used.
>>
>> However, we now have a concept of the local job path, so when test2 is
>> read the jobfile: prefix will use path one, and when reading test3, that
>> prefix will trigger one/two usage.
>
> very nice and handy feature, thanks for that.
>
> Just a remark -
> - there was a similar prefix "toppath:" introduced some time ago.
>
> And - IIUC - "jobfile" refers to a dir rather than to a file, so
> wouldn't be better to call the prefix "jobdir:" or "jobpath:"?
The difference is that toppath: works on the input stack and jobfile: on
the accumulated subpaths (normally in a job structure) ... in fact, both
could work out the same but the top of the inputstack could be different
... it's all a matter of experiencing, so
\usepath[jobfile:]
\setupexternalfigures[directory=jobfile:]
\usepath[toppath:]
\setupexternalfigures[directory=toppath:]
could have the best of both worlds.
toppath == dir of top of inputstack
jobfile == dir of current jobfile
maybe jobpath is indeed better (i'll change it and keep the old one for
a while)
>> For this to work, one has to say:
>>
>> \usepath[jobfile:]
>> \setupexternalfigures[directory=jobfile:]
>>
>> To what extent this all works out well is to be tested.
>>
>> Hans
>
>
--
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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:[~2014-07-27 13:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-26 9:01 Hans Hagen
2014-07-27 11:24 ` Procházka Lukáš Ing. - Pontex s. r. o.
2014-07-27 13:59 ` Hans Hagen [this message]
[not found] <DUB124-W7A61A44931264E38D65CDB1950@phx.gbl>
2014-02-05 10:21 ` Project structure pol stra
2014-02-06 21:25 ` Marco Patzer
2014-02-09 11:25 ` Pol Stra
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=53D505C7.5080808@wxs.nl \
--to=pragma@wxs.nl \
--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).