From: Hans Hagen <pragma@wxs.nl>
Subject: Re: \typefile with a file in \usepath fails
Date: Sun, 30 Apr 2006 12:33:20 +0200 [thread overview]
Message-ID: <44549270.2080506@wxs.nl> (raw)
In-Reply-To: <ops8qi9owt9niby6@localhost>
nico wrote:
> Hello,
>
> \typefile does not output a file not in the current directory but
> available from a path defined by \usepath. It sounds like a bug since the
> file is actually found; if not, a message telling that the file does not
> exist would be printed.
>
> Example:
> \usepath[/path/to/my/file]
> \typefile{filebasename}
>
>
what version of context do you run? i though that i added support for that some time ago
Hans
-----------------------------------------------------------------
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
-----------------------------------------------------------------
next prev parent reply other threads:[~2006-04-30 10:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 20:30 nico
2006-04-30 10:33 ` Hans Hagen [this message]
2006-04-30 12:23 ` nico
2006-04-30 13:22 ` Hans Hagen
2006-04-30 15:04 ` nico
2006-04-30 16:59 ` Hans Hagen
2006-04-30 18:28 ` nico
2006-04-30 19:02 ` nico
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=44549270.2080506@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).