ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Max Chernoff via ntg-context <ntg-context@ntg.nl>
To: ntg-context@ntg.nl
Cc: Max Chernoff <mseven@telus.net>
Subject: Re: [NTG-context] update
Date: Thu, 27 Apr 2023 17:54:54 -0600	[thread overview]
Message-ID: <3494cdac53c266e46cee5015202f4f2816e041f5.camel@telus.net> (raw)
In-Reply-To: <45108ef43900d773f2c414938183c587@polarcom.com>

Hi Lynx,

>         * How can I be sure that the standalone version is the one being
> implemented?

It depends on what your $PATH is set to. On Linux/macOS, you can run

   $ type -ap context

to list all the ConTeXts in your $PTAH. The first one in that list is
the one that will be ran by default.

If you want to always run the standalone version, then you'll need to
make sure that your ConTeXt directory comes before your TL directory in
your PATH. On Linux/macOS, you'd add something like

   export PATH="/path/to/context/bin/:$PATH"
   
to your ~/.profile; on Windows, you can use the "setx" command. Googling
something like "add location to path" will get you more specific
instructions for your OS/shell.

>         * How do I update the standalone version

Just run the installer again. On my system, I run

   $ cd /opt/context
   $ sudo sh ./install.sh

> (I assume that, as of today,
> it is already the most up-to-date version

Correct.

> if and when it is
> required or desired to do so?

You only need to update ConTeXt if a new update fixes a bug that affects
you or adds a new feature that you want. Most updates are announced on
the list, so you could just update whenever you see a new update. Or you
could just try updating once per week. You could also just never update.
Up to you.

The general recommendation is to save an old copy of the ConTeXt folder
before you update in case something breaks. I've never done this before
though since I can usually patch the bugs myself, and I can always fall
back on the version in TL if something is really broken.

-- Max
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2023-04-27 23:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-26 21:55 Hans Hagen via ntg-context
2023-04-26 23:54 ` Jairo A. del Rio via ntg-context
2023-04-27  2:25   ` Rik Kabel via ntg-context
2023-04-27  2:34     ` Jairo A. del Rio via ntg-context
2023-04-27  7:52   ` Hans Hagen via ntg-context
2023-04-27  0:50 ` lynx--- via ntg-context
2023-04-27  1:52   ` Aditya Mahajan via ntg-context
2023-04-27  5:11     ` Max Chernoff via ntg-context
2023-04-27  7:58       ` Hans Hagen via ntg-context
2023-04-27  7:38   ` Hans Hagen via ntg-context
2023-04-27  8:32     ` Max Chernoff via ntg-context
2023-04-27 21:51       ` lynx--- via ntg-context
2023-04-27 23:54         ` Max Chernoff via ntg-context [this message]
2023-06-04 17:01 Hans Hagen via ntg-context
2024-01-08 10:36 Hans Hagen via ntg-context
2024-03-11 17:48 Hans Hagen

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=3494cdac53c266e46cee5015202f4f2816e041f5.camel@telus.net \
    --to=ntg-context@ntg.nl \
    --cc=mseven@telus.net \
    /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).