That is a bug, not a version mismatch.
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
webp
At Monday, 25.07.2011 on 12:31 Paul Menzel wrote:
>
> Thanks, but I think this was not the problem at my end.
> `~/.first-setup.sh` is still the one from January, so `extras` worked
> for me.
The parameters (and the actual update process) are handled by
bin/mtx-update.lua which is one of the fir
Am Montag, den 25.07.2011, 12:14 +0200 schrieb Wolfgang Schuster:
> Am 25.07.2011 um 12:10 schrieb Paul Menzel:
>
> >> the updater/installer remembers what you've installed so the next time
> >> the extras will be synchronized along with the core (all or the
> >> selection you've chosen)
> >
>
Am 25.07.2011 um 12:10 schrieb Paul Menzel:
>> the updater/installer remembers what you've installed so the next time
>> the extras will be synchronized along with the core (all or the
>> selection you've chosen)
>
> Well, then this somehow failed for me. The TikZ module was still from
> May 2
Am Montag, den 25.07.2011, 09:06 +0200 schrieb Hans Hagen:
> On 25-7-2011 12:26, Paul Menzel wrote:
> > I just experienced a situation that I wanted to try a module, in this
> > case TikZ [1][2], and I only had run `./first-setup.sh`, so the module
> > and “core” were diverted and I got an error m
On 25-7-2011 12:26, Paul Menzel wrote:
Dear ConTeXt folks,
I just experienced a situation that I wanted to try a module, in this
case TikZ [1][2], and I only had run `./first-setup.sh`, so the module
and “core” were diverted and I got an error message.
! Undefined control sequence.
Dear ConTeXt folks,
I just experienced a situation that I wanted to try a module, in this
case TikZ [1][2], and I only had run `./first-setup.sh`, so the module
and “core” were diverted and I got an error message.
! Undefined control sequence.
system > t
