ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: context@vivaldi.net
To: ConTeXt <ntg-context@ntg.nl>
Subject: Retrieving original value of enviroment variable HOME
Date: Wed, 06 May 2020 17:43:53 +0200	[thread overview]
Message-ID: <49ac0f366628190337f80efccc25a6c6@vivaldi.net> (raw)

Hello,

before I run ConTeXt, I set a (new) variable "HOME" to point to a 
particular directory.

ConTeXt changes its value during startup - it sets its value to 
%USERPROFILE% - I guess it is to unify environment somehow for all 
platforms ConTeXt supports; probably here:

---- data-ini.lua, ln. ~86
do

     local homedir = osgetenv(ostype == "windows" and 'USERPROFILE' or 
'HOME') or ''

     if not homedir or homedir == "" then
         homedir = char(127) -- we need a value, later we wil trigger on 
it
     end

     homedir = file.collapsepath(homedir)

     ossetenv("HOME",       homedir) -- can be used in unix cnf files 
<<<<<<<<<<<<<< HERE
     ossetenv("USERPROFILE",homedir) -- can be used in windows cnf files

     environment.homedir = homedir

end
----

But anyway - would it be possible to store the original value of HOME 
environment variable (if set) before it gets changed during 
initialization - e.g. to a Lua table?

- I would need to work with the original value in run-time (Win7 / WinX; 
ConTeXt MkIV).

Best regards,

Lukas
___________________________________________________________________________________
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-06 15:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-06 15:43 context [this message]
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
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=49ac0f366628190337f80efccc25a6c6@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).