From: "Mojca Miklavec" <mojca.miklavec.lists@gmail.com>
Subject: Re: bug?: interaction between columns and background
Date: Thu, 5 Oct 2006 18:38:27 +0200 [thread overview]
Message-ID: <6faad9f00610050938w5fa667afv976c3f96b3a9c2ae@mail.gmail.com> (raw)
In-Reply-To: <Pine.WNT.4.63.0610041940190.3328@nqvgln>
On 10/5/06, Aditya Mahajan wrote:
> Hans, can ctxtools be modified to give the option of downloading both
> the stable and latest branch? --updatecontext gives the beta which,
> being a beta, has occasional bugs. So this method of updating context
> can not be recommended to new users. How about adding
>
> ctxtools --updatecontext --stable to give the stable branch, or
> instead make fetching the stable branch default and give --beta to
> download the beta. Maybe even extract everything with --beta to
> TEXMFBETA folder so that maintaining beta and stable in parallel is
> seamless. Right now there is texexec --beta for running the beta, but
> then you have to maintain the beta tree manually.
I would support all that you said (separate tree for beta, --update --beta, ...)
Well, the very first bad experience that I had on other computers when
trying to update ConTeXt with "--update": (un)zip as a command-line
executable is usually missing on just any windows computer, so newbies
have to overcome that one first :(
Mojca
next prev parent reply other threads:[~2006-10-05 16:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-01 7:42 Mojca Miklavec
2006-09-01 9:04 ` Peter Rolf
2006-09-01 10:43 ` Mojca Miklavec
2006-09-29 8:54 ` Patrick Gundlach
2006-09-29 14:03 ` Hans Hagen
2006-09-29 16:12 ` Mojca Miklavec
2006-09-30 11:31 ` Patrick Gundlach
2006-10-02 9:13 ` Hans Hagen
2006-10-04 19:14 ` Patrick Gundlach
2006-10-04 23:49 ` Aditya Mahajan
2006-10-05 16:38 ` Mojca Miklavec [this message]
2006-10-06 10:01 ` Hans Hagen
2006-10-06 6:30 ` Sanjoy Mahajan
2006-10-06 9:56 ` 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=6faad9f00610050938w5fa667afv976c3f96b3a9c2ae@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).