ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
Subject: Re: Problem with Context ver: 2006.09.11 14:37 MK II fmt: 2006.9.12 int: english/english
Date: Wed, 13 Sep 2006 00:05:46 +0200	[thread overview]
Message-ID: <45072F3A.20005@wxs.nl> (raw)
In-Reply-To: <4507120B.60403@cs.com>

WN wrote:
> Another important thing, how can I make sure, when I update or download 
> Context , it's a stable version
> instead of a beta ? Looking at the entries on the mailinglist related to 
> the ''beta'' release, I wonder
> if I have to use version control instead so I can always revert back to 
> the  release which worked.
> Or will the version control be built into the Context system instead, 
> just wondering ?
>   
if you're not afraid for testing, take the beta (depends on if you asked 
for new features as well)

otherwise take the current

especially the current beta's are real beta's because i'm shuffling some 
code around (mk iv preparations)
 
> savetxt(1,72.52364pt,8.26648pt,0.0pt) shifted (0,-0.0pt);
> savetxt(2,135.12482pt,8.26648pt,2.33331pt) shifted (0,-2.33331pt);
> ! TeX capacity exceeded, sorry [input stack size=10000].
> \@xob@testmp-mpgraph ->\@xob@testmp-mpgraph
>   
strange indeed

Hans 

-----------------------------------------------------------------
                                          Hans Hagen | PRAGMA ADE
              Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
     tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                             | www.pragma-pod.nl
-----------------------------------------------------------------

  reply	other threads:[~2006-09-12 22:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-12 17:07 WN
2006-09-12 17:55 ` Hans Hagen
2006-09-12 20:01   ` WN
2006-09-12 22:05     ` Hans Hagen [this message]
2006-09-13  0:02     ` 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=45072F3A.20005@wxs.nl \
    --to=pragma@wxs.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).