From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How to add directory to input path?
Date: Tue, 21 Jul 2009 16:51:54 +0200 [thread overview]
Message-ID: <6faad9f00907210751i374b9183ga959f69c02241473@mail.gmail.com> (raw)
In-Reply-To: <F6766225-EE0F-4CA6-93BA-431658AD85B5@gmail.com>
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.
>> But then I have another question. I actually wanted to use that inside
>> a module (gnuplot) that uses something like
>>
>> \processmyfile[#1][#2]{
>> ....
>> \readlocfile{#2}{}{}
>> ....
>> }
>>
>> I wish I remembered why I decided for \readlocfile (I guess it was for
>> error handling that is still waiting to be implemented). How should I
>> change the module in this particular case? (What should I use instead
>> of \readlocfile, so that the file will be found?)
>
> What behaviour do you want?
>
> I would expect when I load a file it should found in the current directory
> or the TeX tree but not in subdirectories, when you want to take
> subdirectory
> searching I would use something like
>
> \setupgnuplot[directory={,myplots/}]
Hmmm ... that's not a bad idea either.
> \def\inputgnuplotfile#1%
> {\!!donefalse
> \def\doinputgnuplotfile##1%
> {\doiffileelse{##1#1}
> {\readlocalfile{##1#1}{}{}\!!donetrue\quitcommalist}
> {\!!donefalse}}
> \processcommacommand[\gnuplotparameter{directory}]\doinputgnuplotfile
> \!!ifdone\message{gnuplot}{...}\else\message{gnuplot}{file #1 not
> found}\fi}
Thank you very much. I'll build this into the module. I can actually still use
\processcommacommand[,\gnuplotparameter{directory},\allinputpaths]
with your code :) :) :)
Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2009-07-21 14:51 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 [this message]
2009-07-21 21:19 ` Hans Hagen
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=6faad9f00907210751i374b9183ga959f69c02241473@mail.gmail.com \
--to=mojca.miklavec.lists@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).