From: "Thomas A. Schmitz" <thomas.schmitz@uni-bonn.de>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Error in installing new beta
Date: Sun, 13 Jun 2010 23:06:27 +0200 [thread overview]
Message-ID: <A1C38E32-4157-448F-928F-5C287FF0019C@uni-bonn.de> (raw)
In-Reply-To: <4C154658.9010009@wxs.nl>
On Jun 13, 2010, at 10:58 PM, Hans Hagen wrote:
> On 13-6-2010 7:32, Thomas A. Schmitz wrote:
>>
>>
>>
>> TEXMFHOME = "~/texmf-home", -- "tree:///~/texmf
>>
>> for mkii, however, it is set in texmf.cnf (l. 31)
>>
>> TEXMFHOME = $HOME/texmf
>>
>> why these two different values? I consider texmf-home as wrong.
>
> because i dislike having a 'texmf' other than the main one anywhere (if only because it makes tracing a pain) .. i'll set it to texmf but will probably add some warnings in a future version
>
Well, I know that, we've been discussing it for a while. But then both mkii and mkiv still should have the same value. And ~/texmf is the canonical thing; disregarding it will confuse any casual user.
>
> strange as that should be intercepted. I'll see what my mac does with it when i hav eit up and running.
>
I get the same behavior on linux.
>
> tree:// is just one of the uri's supported (and permits loading files from some tree) and this scheme is autoinserted when no !! is used; the !! will become cache:// .. much of that is still experimental
OK, thanks for the info. I used to have my own configuration, but environment variables aren't used any more. How does mkiv store the config information now? How could I overwrite the values that mtxrun --variables shows?
All best
Thomas
___________________________________________________________________________________
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:[~2010-06-13 21:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-11 14:19 status message of mtxrun --ifchanged Aditya Mahajan
2010-06-12 15:55 ` Hans Hagen
2010-06-12 23:49 ` Error in installing new beta (was: status message of mtxrun --ifchanged) Aditya Mahajan
2010-06-13 7:24 ` luigi scarso
2010-06-13 7:33 ` Thomas A. Schmitz
2010-06-13 17:32 ` Thomas A. Schmitz
2010-06-13 20:58 ` Error in installing new beta Hans Hagen
2010-06-13 21:06 ` Thomas A. Schmitz [this message]
2010-06-13 21:13 ` Mojca Miklavec
2010-06-13 22:10 ` Hans Hagen
2010-06-13 22:15 ` Hans Hagen
2010-06-13 14:27 ` 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=A1C38E32-4157-448F-928F-5C287FF0019C@uni-bonn.de \
--to=thomas.schmitz@uni-bonn.de \
--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).