From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Bugs with minimals 2015.05.24 12:42
Date: Tue, 24 May 2016 12:14:03 +0200 [thread overview]
Message-ID: <CALBOmsasPxofL1A7W8ASevFuUyJ9xWo6CLk6s1bAn+0QgMzTbw@mail.gmail.com> (raw)
In-Reply-To: <F7A82E2B-1DFB-4EE9-88AC-BFA466FF850B@uva.nl>
On 24 May 2016 at 12:06, Meer, Hans van der wrote:
>> On 02 Jun 2015, at 14:51, Hans Hagen wrote:
>>
>> If you install extra fonts and files, you should put them in
>>
>> tex/texmf-fonts
>> tex/texmf-project
>>
>> as these are left untouched. That has always been the recommendation. The other trees will be synchronized in an update and that also includes deleting obsolete files.
>
> I guess the same applies to /tex/texmf-local?
>
> And how is that with tex/texmf-modules? I am asking because there is also a modules directory:
> context/tex/texmf-context/tex/context/modules
> It would be nice if I safely can put my modules there instead of burying them somewhere else in the trees.
If you put files under texmf-context, they will be removed
automatically with next update. You can install official modules with
"--modules=t-tikz" for example and those will stay. But if you want
your own unrelated modules, you should not use texmf-modules unless
you remove the "--delete" flag for rsync (but then you'll end up with
other obsolete files).
The trees texmf-local, texmf-fonts, texmf-projects are all fine.
Mojca
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2016-05-24 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 12:26 david.boerschlein
2015-06-02 12:51 ` Hans Hagen
2016-05-24 10:06 ` Meer, Hans van der
2016-05-24 10:14 ` Mojca Miklavec [this message]
2015-06-02 19:18 ` Mojca Miklavec
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=CALBOmsasPxofL1A7W8ASevFuUyJ9xWo6CLk6s1bAn+0QgMzTbw@mail.gmail.com \
--to=mojca.miklavec.lists@gmail.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).