From: Hans van der Meer <H.vanderMeer@uva.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: simplefonts not found
Date: Tue, 29 Dec 2009 23:55:14 +0100 [thread overview]
Message-ID: <1C62F6F3-4194-49C7-8A63-65C124DC86BD@uva.nl> (raw)
In-Reply-To: <056CCD58-9C59-4EF4-A211-5DF4F26F8DE4@googlemail.com>
> Did you update the file database with 'luatools --generate',
> what's the output from 'luatools t-simplefonts.tex'.
No, I thought that in TeX the given TeX-home is always searched first.
Such that normally a 'texhash' is not required whenthings are changed.
I seem to remember that changes in files residing in that ../tex/
context/user directory always had an immediate effect.
It is also possible that I have let myself been misled by the fact
that the contextbeta is installed in location separate from the
texlive setup used with older versions. In that case, will it be
sufficient if I add the relevant location in a TEXMF (or whatever
should I use?) shell variable? I is "luatools --generate" an absolute
must?
Hans van der Meer
On 29 dec 2009, at 22:46, Wolfgang Schuster wrote:
>
> Am 29.12.2009 um 22:40 schrieb Hans van der Meer:
>
>>>> Unpacked the zip and put the t-simplefonts .lua and .tex files
>>>> inside the directory where all my context (user) input files
>>>> reside.
>>>
>>> Is your user directory in the TeX directory?
>>>
>>> This is where my local version of simplefonts resides:
>>> /Users/wolf/context/tex/texmf-local/tex/context/third/simplefonts/
>>> t-simplefonts.tex
>>
>> My files reside in /Users/hans/Library/texmf/tex/context/user/t-
>> simplefonts.tex
>> where for example also is /Users/hans/Library/texmf/tex/context/
>> user/hvdm-cas.tex
>> and that file is found and the module in it loaded without a hitch.
>
> Did you update the file database with 'luatools --generate',
> what's the output from 'luatools t-simplefonts.tex'.
>
> Wolfgang
>
> ___________________________________________________________________________________
> If your question is of interest to others as well, please add an
> entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
> archive : http://foundry.supelec.fr/projects/contextrev/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2009-12-29 22:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-29 20:30 Hans van der Meer
2009-12-29 20:39 ` Wolfgang Schuster
2009-12-29 21:40 ` Hans van der Meer
2009-12-29 21:43 ` Aditya Mahajan
2009-12-29 21:46 ` Wolfgang Schuster
2009-12-29 22:55 ` Hans van der Meer [this message]
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=1C62F6F3-4194-49C7-8A63-65C124DC86BD@uva.nl \
--to=h.vandermeer@uva.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).