From: Wolfgang Schuster <schuster.wolfgang@googlemail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \ReadFile in MkII vs MkIV
Date: Sun, 17 Oct 2010 19:28:44 +0200 [thread overview]
Message-ID: <0511A24C-C978-4DE9-804D-1995071C957E@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.01.1010171313130.7119@ybpnyubfg.ybpnyqbznva>
Am 17.10.2010 um 19:21 schrieb Aditya Mahajan:
> It works, but does not fit my need. I wanted to add an option to the filter module to allow the user to say:
>
> \setupexternalfilters[directory=$TEMP]
>
> and have all the tmp files created in $TEMP. Having to set this as a relative path will be really ugly.
>
> I am just looking for macro that takes the filename as a (brace delimited) parameter and typesets it. I can define one on my own; but I thought that \ReadFile is already supposed to do that.
>
> It is straight forward to "fix" \ReadFile so that absolute paths work:
>
> \unexpanded\def\readfile #1{\doreadfile{any} \empty{#1}}
> \unexpanded\def\ReadFile #1{\doreadfile{any} \empty{#1}\donothing\donothing}
>
> I just wondering if the current behavior is a design decision or an oversight.
What i get from the comments in the source is that \readfile looks for the requested file
in the current directory, the parent directories and the tex directory and \ReadFile is
a alternative form for \readfile without the second and third argument.
You can define your own command \ReadFilter which is based in \readsetfile or \readfixfile.
Wolfgang
___________________________________________________________________________________
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:[~2010-10-17 17:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-16 21:09 Aditya Mahajan
2010-10-17 12:50 ` luigi scarso
2010-10-17 17:21 ` Aditya Mahajan
2010-10-17 17:27 ` Aditya Mahajan
2010-10-17 17:28 ` Wolfgang Schuster [this message]
2010-10-17 17:58 ` Aditya Mahajan
2010-10-17 18:06 ` Wolfgang Schuster
2010-10-17 18:54 ` Aditya Mahajan
2010-10-17 20:17 ` Hans Hagen
2010-10-17 21:02 ` Aditya Mahajan
2010-10-17 22:23 ` Hans Hagen
2010-10-17 20:15 ` Hans Hagen
2010-10-17 20:50 ` 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=0511A24C-C978-4DE9-804D-1995071C957E@gmail.com \
--to=schuster.wolfgang@googlemail.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).