From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Retrieving original value of enviroment variable HOME
Date: Fri, 8 May 2020 14:18:20 +0200 [thread overview]
Message-ID: <1572af58-d279-3070-02e7-6808d25ac9bd@xs4all.nl> (raw)
In-Reply-To: <6b5a178a3137a3fdc168754b1babb578@vivaldi.net>
On 5/7/2020 12:30 PM, context@vivaldi.net wrote:
> Hello Hans,
>
>>> - I would need to work with the original value in run-time (Win7 /
>>> WinX; ConTeXt MkIV).
>> I'll add
>>
>> environment.oldhome
>>
>> being the original one (but no testing done here)
>
> would be great, thank you!
>
> I guess it will be available over the night (= ConTeXt latest)?
You can check it. Btw, when you're using lmtx there should be no real
differences between for instance unix and windows, although on windows
lmtx does support wide characters in environment variables, command line
arguments, filenames, filelinks etc. (not that that matters much as one
will seldom use more than ascii). Specific environment variables like
HOME are a bit tricky on windows as they come in variants, so let me
know if some more magic is needed.
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2020-05-08 12:18 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 [this message]
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=1572af58-d279-3070-02e7-6808d25ac9bd@xs4all.nl \
--to=j.hagen@xs4all.nl \
--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).