From: David Petrou <dpetrou@ece.cmu.edu>
Cc: ntg-context@let.uu.nl
Subject: Re: Q: problems finding syst-pln.tex
Date: Mon, 3 Jun 2002 13:45:48 -0400 [thread overview]
Message-ID: <20020603134548.B27369@cs.cmu.edu> (raw)
In-Reply-To: <20020603074309.D393-100000@prudence.compuserve.de>; from fritsch_andreas@gmx.de on Mon, Jun 03, 2002 at 07:44:20AM +0200
> did you update your lsr?
>
> 'texconfig rehash'
>
> should do the trick.
That works! Thanks!
I think the documenation should be updated to mention that this should
be run. Do the developers of ConTeXt read this mailing list? If not,
who should I contact to suggest this?
Now, I have another problem. When I try to do `texexec --make
metafun' I get this:
----------------------------------------------------------------------
bash-2.04# texexec --make metafun
TeXExec 2.8 - ConTeXt / PRAGMA ADE 1997-2002
This is MetaPost, Version 0.641 (Web2C 7.3.1) (INIMP)
! I can't find file `metafun'.
<*> metafun
Please type another input file name:
----------------------------------------------------------------------
The only file that I have that looks like `metafun' is
`metapost/context/metafun.mp'. What am I doing wrong?
Finally, could you answer whether I should have run `fmtutil --all'?
The documentation is kind of unclear in this section. The
documentation mentions this command, but not whether or not the user
should run it. And it's a very time-consuming process. Finally, it
seems like `texexec --make' replicates some of what `fmtutil --all'
does.
> Andreas
thanks,
david
next prev parent reply other threads:[~2002-06-03 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-03 3:53 David Petrou
2002-06-03 5:44 ` Andreas Fritsch
2002-06-03 17:45 ` David Petrou [this message]
2002-06-04 10:56 ` David Antos
2002-06-10 16:13 ` David Petrou
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=20020603134548.B27369@cs.cmu.edu \
--to=dpetrou@ece.cmu.edu \
--cc=ntg-context@let.uu.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).