ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Cc: ntg-context@ntg.nl
Subject: Re: documentatie texexec
Date: Wed, 04 Nov 1998 09:12:23 +0100	[thread overview]
Message-ID: <36400C67.3740391F@wxs.nl> (raw)

W.H. Dekker wrote:
> 
> where  do I find documentation for texexec?
> 
> I tried (in linux):
> 
> texexec -help
> 
> and got:
> 
>  TeXExec 1.1 - ConTeXt / PRAGMA 1997-1998
> 
>                warning : ././texexec.ini not found
> 
> Is -help not yet implemented?

It is. Currently texexec searches texexec.ini (is in the distribution)
on the path where texexec.pl is present. You need to set up this ini
file (not that hard to do for a perl expert like you). 

Recently Thomas Esser and I discussed how to give tex* a place inthe
texmf tree and he proposed a closer integration with web2c (especially
using its path search mechanism). So, in the next tetex release context
will be more integrated than currently. In this respect, suggestions are
welcome. 

Furthermore, I suggest to use pdftex instead of normal tex: gives you
dvi and pdf where texexec sorts things out. There is a new update of
pdftex (see www.tug.org) or the tetex update site.

Hans

Hans

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
    tel: 038 477 53 69 | fax: 038 477 53 74 | mail: pragma@wxs.nl
-----------------------------------------------------------------


             reply	other threads:[~1998-11-04  8:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-11-04  8:12 Hans Hagen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-10-23 16:38 Gilbert van den Dobbelsteen
1998-11-04 13:48 W.H. Dekker
1998-11-03 23:32 W.H. Dekker
1998-11-04 11:56 ` Taco Hoekwater

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=36400C67.3740391F@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).