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: Sun, 10 May 2020 14:33:41 +0200	[thread overview]
Message-ID: <85f9408fdd5a251278872b5629028d9c@vivaldi.net> (raw)
In-Reply-To: <1572af58-d279-3070-02e7-6808d25ac9bd@xs4all.nl>

[-- Attachment #1: Type: text/plain, Size: 1103 bytes --]

Hello, Hans,

I've just renewed the Ctx Beta installation, but 'environment.oldhome' 
seems be unavailable.

Was I "too quick" with renewing Ctx?

Testing sample:

----
\starttext
   Ahoj
   \startluacode
     context(environment.oldhome or "??")
   \stopluacode
\stoptext
----

- prints "??".

I also attache the "status-of-update.lua" and the batch 
"first-setup.bat" (maybe a bit obsolete, but working so far) I used to 
renew Ctx.

Also result of "dir /s" is available here (~84 k packed):

   http://leteckaposta.cz/302654804

What am I doing wrong?

Best regards,

Lukas


On 2020-05-08 14:18, Hans Hagen wrote:

> 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

[-- Attachment #2: ChkEnv.mkiv --]
[-- Type: text/plain, Size: 106 bytes --]

\starttext
  Ahoj
  \startluacode
    context(environment.oldhome or "??")
  \stopluacode
\stoptext

[-- Attachment #3: ChkEnv.pdf --]
[-- Type: application/pdf, Size: 5720 bytes --]

[-- Attachment #4: status-of-update.lua --]
[-- Type: text/plain, Size: 812 bytes --]

-- generator : luat-sta.lua
-- state tag : whatever

return {
 ["context"]={
  ["version"]="beta",
 },
 ["engines"]={
  ["luatex"]=true,
  ["pdftex"]=true,
  ["xetex"]=true,
 },
 ["formats"]={
  ["cont-en"]=true,
  ["cont-nl"]=true,
  ["metafun"]=true,
 },
 ["info"]={
  ["comment"]="this file contains the settings of the last 'mtxrun --script update' run",
  ["count"]=138,
  ["date"]="2020-05-10 11:59:36",
  ["runtime"]=94.039,
  ["version"]=0.1,
 },
 ["modules"]={
  ["all"]=true,
 },
 ["paths"]={
  ["root"]="d:\\Ctx-Beta\\tex",
 },
 ["platforms"]={
  ["mswin"]=true,
  ["win64"]=true,
 },
 ["repositories"]={
  ["current"]=true,
 },
 ["rsync"]={
  ["flags"]={
   ["delete"]="--delete",
   ["normal"]="-rpztlv",
  },
  ["module"]="minimals",
  ["program"]="rsync",
  ["server"]="contextgarden.net::",
 },
}

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #5: first-setup.ba~ --]
[-- Type: text/x-msdos-batch; name=first-setup.ba~, Size: 1079 bytes --]

@echo off

setlocal

echo okay > ok.log
ruby -e "File.delete('ok.log')"
if not exist "ok.log" goto okay

echo.
echo You need to install Ruby first (if you want to use pdfTeX or XeTeX).
echo Fetching files anyway.
echo.

:okay


set OWNPATH=%~dp0
set CONTEXTROOT=%OWNPATH%tex

set PATH=%OWNPATH%bin;%CONTEXTROOT%\texmf-mswin\bin;%PATH%

set CYGWIN=nontsec

rsync -av --exclude 'rsync.exe' --exclude 'cygwin1.dll' --exclude 'cygiconv-2.dll' rsync://contextgarden.net/minimals/setup/mswin/bin/ bin

mtxrun --script ./bin/mtx-update.lua --force --update --make --engine=all --context=beta --texroot=%CONTEXTROOT% %*

echo.
echo When you want to use context, you need to initialize the tree with:
echo.
echo   %CONTEXTROOT%\setuptex.bat %CONTEXTROOT%
echo.
echo You can associate this command with a shortcut to the cmd prompt.
echo.

if not exist "ok.log" goto end

echo.
echo If you want to use pdfTeX or XeTeX you need to install Ruby first.
echo Remake formats or rerun this script afterwards.
echo.

del /q ok.log

:end

endlocal


[-- Attachment #6: Type: text/plain, Size: 493 bytes --]

___________________________________________________________________________________
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-10 12:33 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 [this message]
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=85f9408fdd5a251278872b5629028d9c@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).