From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to add directory to input path?
Date: Tue, 21 Jul 2009 23:19:45 +0200 [thread overview]
Message-ID: <4A6630F1.5020008@wxs.nl> (raw)
In-Reply-To: <6faad9f00907210751i374b9183ga959f69c02241473@mail.gmail.com>
Mojca Miklavec wrote:
> On Tue, Jul 21, 2009 at 15:31, Wolfgang Schuster wrote:
>> Am 21.07.2009 um 14:28 schrieb Mojca Miklavec:
>>
>>> Thanks. So basically there's no way to convince \input to work
>>> "properly" (that is: respecting some additional input path) in mkii?
>>> (In mkiv it seems to work, but it could be that that's just because it
>>> interacts with its own "kpathsea".)
>> The question is should \input kn MkIV behave like it did in MkII
>> or should it take subdirectories into account.
>
> I see no serious reason speaking against that.
there is:
\input tree://whaterver/**/somefile.tex
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | fax: 038 477 53 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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2009-07-21 21:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 8:37 Mojca Miklavec
2009-07-21 11:22 ` Wolfgang Schuster
2009-07-21 12:28 ` Mojca Miklavec
2009-07-21 13:31 ` Wolfgang Schuster
2009-07-21 14:51 ` Mojca Miklavec
2009-07-21 21:19 ` Hans Hagen [this message]
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=4A6630F1.5020008@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).