ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Mojca Miklavec <mojca.miklavec.lists@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: updating ConTeXt standalone
Date: Sat, 23 Apr 2016 18:50:27 +0200	[thread overview]
Message-ID: <CALBOmsYBs1+YULWOc_3QouZRWMDDfpqcX1MUWm+TQBGw2BLA+A@mail.gmail.com> (raw)
In-Reply-To: <995F8954-4625-40F7-8924-30402D416C5B@gmail.com>

On 23 April 2016 at 17:21, Otared Kavian wrote:
> Ooops… Indeed I think I made a mistake: when I tried to check what Alan was saying, I ran first-setup.sh and immediatel after I issued the command
>         context —version
>
> so that probably I got the version number from last year’s stable TeXLive. (I have always ate least two versions of Context on my machine…).
> But trying again right now the whole procedure, I get now my standalone version updated to
>         Context version: 2016.04.22 09:10
>
> So probably meanwhile Mojca fixed the server…

No, the server is still not available. I was only "hotfixing" the update.

Mojca
___________________________________________________________________________________
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://tex.aanhet.net
archive  : http://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2016-04-23 16:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-23 12:15 Alan Bowen
2016-04-23 12:48 ` Otared Kavian
2016-04-23 13:10   ` Pablo Rodriguez
2016-04-23 15:21     ` Otared Kavian
2016-04-23 16:50       ` Mojca Miklavec [this message]
2016-04-23 21:24         ` Alan Bowen
2016-04-23 13:06 ` Mojca Miklavec

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=CALBOmsYBs1+YULWOc_3QouZRWMDDfpqcX1MUWm+TQBGw2BLA+A@mail.gmail.com \
    --to=mojca.miklavec.lists@gmail.com \
    --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).