ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: Problem with MkIV and TikZ picture remembering
Date: Tue, 3 Mar 2015 13:38:18 +0100	[thread overview]
Message-ID: <hmz0g8wmxlzx.dlg@nililand.de> (raw)
In-Reply-To: <9F017330-602B-452C-A1EE-27F78EDD9A97@gmail.com>

Am Tue, 3 Mar 2015 08:54:00 +0100 schrieb Wolfgang Schuster:

I wanted to try the example in my context standalone installation
and got an "undefined command error" on the \usetikzlibrary.
After a bit digging I could repair this with "first-install.bat
--modules="t-tikz" which seems to get me the newest tikz.

But during this digging I saw

-- that tikz is not mentioned on the module list:
http://modules.contextgarden.net/

-- Following the link to the module
(http://modules.contextgarden.net/TikZ) from
http://wiki.contextgarden.net/TikZ gives an "internal error message"

-- the installation advices on contextgarden doesn't explain what to
do if you want to update modules too. I'm always using (on windows)
first-setup.bat --keep as explained here
http://wiki.contextgarden.net/ConTeXt_Standalone#Updating_2. But
this doesn't seem to update the modules. Is first-setup.bat --all
better if one simply wants the newest complete standalone?


-- 
Ulrike Fischer 
http://www.troubleshooting-tex.de/

___________________________________________________________________________________
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:[~2015-03-03 12:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-03  7:23 Jörg Weger
2015-03-03  7:25 ` Jörg Weger
2015-03-03  7:54   ` Wolfgang Schuster
2015-03-03 12:38     ` Ulrike Fischer [this message]
2015-03-03 13:11       ` Mojca Miklavec
2015-03-03 13:27         ` Ulrike Fischer
2015-03-03 15:29           ` Mojca Miklavec
2015-03-03 13:51         ` Ulrike Fischer
2015-03-03 17:12 ` Aditya Mahajan
2015-03-03 19:04   ` Hans Hagen
2015-03-03 19:28     ` Aditya Mahajan
2015-03-07 12:08       ` Jörg Weger
2015-03-07 14:52         ` Hans Hagen
2015-03-07 17:30           ` Jörg Weger
2015-03-07 18:22             ` Wolfgang Schuster
2015-03-08 10:11               ` Hans Hagen
2015-03-08 11:26                 ` Wolfgang Schuster
2015-03-08 11:55                   ` Hans Hagen
2015-03-08 12:04                     ` Wolfgang Schuster
2015-03-08 17:39                       ` Hans Hagen
2015-03-08 18:07                         ` Wolfgang Schuster
2015-03-08 19:04                           ` Hans Hagen
2015-03-08 22:17                           ` Hans Hagen
2015-03-13 13:17                             ` Jörg Weger
2015-03-13 13:32                               ` Wolfgang Schuster

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=hmz0g8wmxlzx.dlg@nililand.de \
    --to=news3@nililand.de \
    --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).