ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	Thangalin <thangalin@gmail.com>
Subject: Re: Update setpath to set the path
Date: Mon, 10 May 2021 09:40:03 +0200	[thread overview]
Message-ID: <1c27e820-fd44-3451-a1d2-27810c264f32@xs4all.nl> (raw)
In-Reply-To: <CAANrE7oWTek1v1LL7G-BAYHdLvHtkdoDmg9FmS+A9rSV2Do-TQ@mail.gmail.com>

On 5/10/2021 9:18 AM, Thangalin wrote:
> 
>     One of the benefits of context minimals is that you can install
>     multiple versions in parallel, which allows the user to update
>     frequently without the risk of breaking something for long-term
>     projects. Specifically, you can keep a "frozen" version of context
>     for long-term projects and install a newer version in parallel for
>     newer projects.
> 
> 
> For sure! My environment looks as follows:
> 
> export CONTEXT_HOME=/opt/context
> export PATH="$PATH:...:$CONTEXT_HOME/tex/texmf-linux-64/bin:..."
> 
> The /opt/context directory is a symbolic link, which eases switching 
> between versions: I seldom have to change the environment variables 
> settings.
> 
>     So, your suggestions should be included as a separate script and not
>     as part of the default. Then there is the question of providing an
>     uninstall script as well...
> 
> 
> Using a ConTeXt-specific environment variable (e.g., LMTX_HOME) would 
> make uninstalling a matter of removing it from the PATH and registry (on 
> Windows, anyway). Here are the current instructions:
> 
> https://github.com/DaveJarvis/keenwrite/blob/master/docs/typesetting.md#windows 
> <https://github.com/DaveJarvis/keenwrite/blob/master/docs/typesetting.md#windows>
> 
> Is there a way we can eliminate steps 3 - 6 for Windows installs?
if one starts up mtxrun or context with a fully quallified path it will 
work ok (because it then knows where it sits in the tex tree), like

c:\data\context\tex\texmf-win64\bin\mtxrun --script context ...

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
___________________________________________________________________________________

      reply	other threads:[~2021-05-10  7:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-09 19:14 Thangalin
2021-05-09 23:50 ` Thangalin
2021-05-10  7:00 ` Aditya Mahajan
2021-05-10  7:18   ` Thangalin
2021-05-10  7:40     ` Hans Hagen [this message]

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=1c27e820-fd44-3451-a1d2-27810c264f32@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=ntg-context@ntg.nl \
    --cc=thangalin@gmail.com \
    /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).