ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: context@vivaldi.net
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Retrieving original value of enviroment variable HOME
Date: Tue, 12 May 2020 11:36:39 +0200	[thread overview]
Message-ID: <5c25a84573ea3156ef1fd403579d9163@vivaldi.net> (raw)
In-Reply-To: <b34e60d4-1d3b-cbc3-e874-d81e0d9d7e69@xs4all.nl>

Hello,

On 2020-05-12 10:53, Hans Hagen wrote:
> On 5/11/2020 5:57 PM, context@vivaldi.net wrote:
> 
>> d:\Lukas\ConTeXt\Test\EnvHome>
>> ----
>> 
>> - I'm still getting:
>> 
>> 1       C:/Users/u×ivatel
>> 2       C:/Users/u×ivatel
>> 3       C:/Users/u×ivatel
>> 4       C:/Users/u×ivatel
>> 
>> whilst HOME environment has been set to "DummyHome"  (see "echo 
>> %HOME%").
>> 
>> What's wrong?

I can try.

I found 'oldhome' text in these files:

d:\Ctx-Beta\tex\texmf-context\scripts\context\lua\mtxrun.lua
d:\Ctx-Beta\tex\texmf-context\scripts\context\stubs\mswin\mtxrun.lua
d:\Ctx-Beta\tex\texmf-context\scripts\context\stubs\unix\mtxrun
d:\Ctx-Beta\tex\texmf-context\scripts\context\stubs\win64\mtxrun.lua
d:\Ctx-Beta\tex\texmf-context\tex\context\base\mkiv\data-ini.lua
d:\Ctx-Beta\tex\texmf-mswin\bin\mtxrun.lua

Which files do you recommend to try to insert debug prints into?

And - once I "inject" an extra debug info - do I have to call 
"context.exe --make --generate" (or similar)?

Lukas


> I don't know ... maybe it pick up HOME from someplace else (the outer
> process space or so)
> 
> you can insert prints (say os.getenv('HOME')) and see what happens
> 
> Hans
___________________________________________________________________________________
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
___________________________________________________________________________________

  reply	other threads:[~2020-05-12  9:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 15:43 context
2020-05-07  6:54 ` Hans Hagen
2020-05-07 10:30   ` context
2020-05-08 12:18     ` Hans Hagen
2020-05-10 12:33       ` context
2020-05-10 15:20         ` Hans Hagen
2020-05-11  7:44           ` context
2020-05-11  8:51             ` Hans Hagen
2020-05-11 10:50               ` context
2020-05-11 10:54                 ` Henning Hraban Ramm
2020-05-11 13:36                   ` Henning Hraban Ramm
2020-05-11 10:58                 ` Marco Patzer
2020-05-11 15:20                   ` context
2020-05-11 15:57               ` context
2020-05-12  8:53                 ` Hans Hagen
2020-05-12  9:36                   ` context [this message]
2020-05-12 11:53                     ` Hans Hagen
2020-05-14  7:47                       ` context

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=5c25a84573ea3156ef1fd403579d9163@vivaldi.net \
    --to=context@vivaldi.net \
    --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).