From: Marco Patzer <homerow@lavabit.com>
To: ntg-context@ntg.nl
Subject: Re: Prioritise TEXMFHOME
Date: Wed, 23 Jan 2013 15:17:14 +0100 [thread overview]
Message-ID: <20130123141714.GJ15403@homerow> (raw)
In-Reply-To: <CALBOmsZC9j5EDf8jFy2yLBidQkaJKdE9kkv2S+KQ6X8TCsPHZQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1607 bytes --]
On 2013–01–23 Mojca Miklavec wrote:
> On Wed, Jan 23, 2013 at 11:26 AM, Marco Patzer wrote:
> >
> > I used the following setup to create a reproducible clean
> > environment without interference of possibly set variables.
> >
> > echo '\sans' >mymodules/t-gnuplot.tex
>
> You should put the file under
> mymodules/tex/context/third/t-gnuplot.tex
> and not just anywhere on top level of $TEXMFHOME.
That works, thanks. I didn't think about the importance of the tex
file system structure within TEXMFHOME since my personal files
always have been picked up from random subdirectories within
TEXMFHOME.
> At least somewhere under mymodules/tex/ (but I'm not sure if that
> alone is 100% safe - that is - I'm not sure about the search/sort
> order of two files with the same name under a different path inside
> the texmf tree).
mymodules/tex doesn't seem to be sufficient. My tests revealed that
for files not present in the distribution tex tree the location
within TEXMFHOME does not matter. Files present in the distribution
which are supposed to be overwritten in TEXMFHOME need the same
path. Maybe this is more strict than necessary, but it works. A
version mismatch that gets unnoticed can be very frustrating.
> > I didn't know ConTeXt uses kpsewhich.
>
> In MkII it does. But I meant it more like a cross-check. It might be
> that there would be some bug in mtxrun when searching for files and in
> that case kpsewhich may serve as a confirmation that your set up works
> or doesn't work properly.
All right. Problem solved. Thanks Mojca!
Marco
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 bytes --]
___________________________________________________________________________________
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:[~2013-01-23 14:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 19:58 Marco Patzer
2013-01-22 20:05 ` Mojca Miklavec
2013-01-22 20:29 ` Marco Patzer
2013-01-22 22:10 ` Mojca Miklavec
2013-01-23 10:26 ` Marco Patzer
2013-01-23 13:52 ` Mojca Miklavec
2013-01-23 14:17 ` Marco Patzer [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=20130123141714.GJ15403@homerow \
--to=homerow@lavabit.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).