From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Re: font mystery
Date: Tue, 07 Oct 2003 09:12:06 +0200 [thread overview]
Message-ID: <6.0.0.22.2.20031007091143.033166e0@server-1> (raw)
In-Reply-To: <39B20D31-F721-11D7-A8F9-00039318D414@uni-bonn.de>
At 12:46 05/10/2003, you wrote:
>Maybe one further element that would suggest Context is using a cached
>copy of the tfm-file instead of the newly created file: when I move the
>file Myfont.tfm out of the $home/texmf/fonts/tfm directory, pdftex gives
>me the expected error "! I can't find file `Myfont'." However, Context
>will still happily produce output--with an outdated copy of the tfm! So
>context must be caching it somewhere, and I need to flush that cache.
>Anyone an idea how this can be done?
maybe issuing the command "mktexlsr" helps
Hans
next prev parent reply other threads:[~2003-10-07 7:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-05 10:46 Thomas A.Schmitz
2003-10-07 7:12 ` Hans Hagen [this message]
2003-10-07 8:09 ` Thomas A.Schmitz
2003-10-07 19:09 ` Matt Gushee
2003-10-08 9:07 ` Thomas A.Schmitz
2003-10-10 17:05 ` Patrick Gundlach
2003-10-10 20:52 ` Hans Hagen
2003-10-11 11:23 ` Thomas A.Schmitz
2003-10-14 19:45 ` Hans Hagen
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=6.0.0.22.2.20031007091143.033166e0@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).