From: Rik Kabel <context@rik.users.panix.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Search path for typescripts
Date: Thu, 28 Feb 2019 21:36:47 -0500 [thread overview]
Message-ID: <b968f55b-5232-e08d-0376-224aa61cfa9e@rik.users.panix.com> (raw)
List,
What is the proper place to put a custom typescript file to make it
accessible to multiple projects?
For testing I placed copies in"
1) the local directory
2) <user>/texmf/fonts
3) <installation>/tex/texmf-local/fonts/
A standard version (uncustomized) exists as part of the distribution in:
4) <installation>/tex/texmf-context/tex/context/fonts/mkiv/
luatools <typescriptfile>
finds the file in 1, 4, and 2.
That is, after the local directory it immediately takes the standard
installation directory, never looking in the places one might store
local versions meant to override the distribution files. It might get to
one of those directories (<user>/texmf/fonts) if there is no standard
file in the distribution, but that is not the case here.
I did not see an appropriate environment variable to control this. It
does not seem sensitive to TEXMF or OSFONTDIR.
So, where do I place the customized typescript, or how do I tell ConTeXt
where to look?
--
Rik
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2019-03-01 2:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-01 2:36 Rik Kabel [this message]
2019-03-01 3:42 ` Aditya Mahajan
2019-03-01 15:28 ` Rik Kabel
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=b968f55b-5232-e08d-0376-224aa61cfa9e@rik.users.panix.com \
--to=context@rik.users.panix.com \
--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).