From: Hans Hagen <pragma@wxs.nl>
Subject: Re: How to set paths
Date: Wed, 17 Sep 2003 23:01:09 +0200 [thread overview]
Message-ID: <5.2.0.9.1.20030917230033.01a17100@server-1> (raw)
In-Reply-To: <003c01c37d31$a97c21e0$0500a8c0@best>
At 17:37 17/09/2003 +0200, you wrote:
>Hello!
>
> > you can set the directory (gebied in dutch) with:
> >
> > \setupsystem
> >
> > or pass --path to texexec
>
>Thanks a lot Hans! Although I can't still use \setupsystem properly (even
>with looking at core-code tricks), --path option seems to be the solution.
>I've solve processing XML files in this way. Typing (\typefile) and inputing
>(\input) files are still the quest. --path seems not to work with this
>commands
>or I do something wrong. I'll look closely into it.
another option is to use:
\usepath[list of paths]
\usesubpath[list of subpaths]
Hans
-------------------------------------------------------------------------
Hans Hagen | PRAGMA ADE | pragma@wxs.nl
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: +31 (0)38 477 53 69 | fax: +31 (0)38 477 53 74 | www.pragma-ade.com
-------------------------------------------------------------------------
information: http://www.pragma-ade.com/roadmap.pdf
documentation: http://www.pragma-ade.com/showcase.pdf
-------------------------------------------------------------------------
next prev parent reply other threads:[~2003-09-17 21:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-16 6:40 Pawel Jackowski na Onet
2003-09-16 21:01 ` Hans Hagen
2003-09-17 15:37 ` Pawel Jackowski na Onet
2003-09-17 21:01 ` Hans Hagen [this message]
2003-09-18 10:18 ` How to set paths -- wider view Pawel Jackowski na Onet
2003-09-18 12:46 ` Hans Hagen
2003-09-18 13:30 ` Adam Lindsay
2003-09-18 14:27 ` Hans Hagen
2003-09-18 16:47 ` Pawel Jackowski na Onet
2003-09-17 3:09 ` How to set paths for input files (again) Pawel Jackowski na Onet
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=5.2.0.9.1.20030917230033.01a17100@server-1 \
--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).