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: where to install cont-doc.zip and request for enhancement?
Date: Fri, 12 Nov 1999 10:52:10 +0100	[thread overview]
Message-ID: <3.0.6.32.19991112105210.00a17100@pop.wxs.nl> (raw)
In-Reply-To: <19991111211827.A2606@vasili.rlf.org>

At 09:18 PM 11/11/99 -0500, Thomas Porter wrote:
>I located the cont-doc.zip file which appears to have mod-modu.tex and otehr
>things in it, but was unclear as to where to install it.  I copied all the
>...tex files to /usr/share/texmf/tex/context/base where all the other context
>modules and such are at, then ran texhash.  texexec --modu some.pl still did
>not work.

Everything can be unzipped in texmf, so indeed these modules go into base. 

>Do I need to texexec --make en de nl again?

No. These modules are loaded runtime. 

>I liked Ed Cashin's perl hack where he was able to use \typefile to pull in a
>perl file to include in his presentation.  Any chance of enhancing the pretty
>print constructions like \startPL to pull in a file name as opposed to having
>to include the code inline?

\setuptyping[file][option=color]

\setupcolors[state=start]

\typefile{texexec.pl}

So, \typefile is clever enough to determine the file type. No hack needed. 

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


  reply	other threads:[~1999-11-12  9:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-11-12  2:18 Thomas Porter
1999-11-12  9:52 ` Hans Hagen [this message]
1999-11-12 12:38 ` Tobias Burnus

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=3.0.6.32.19991112105210.00a17100@pop.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).