From: Gavin via ntg-context <ntg-context@ntg.nl>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: Gavin <gavinpublic@comcast.net>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: pgfplots module needs update from December
Date: Sun, 22 Aug 2021 10:30:48 -0600 [thread overview]
Message-ID: <4894015E-2754-493D-BF1B-A6FFA0B4944D@comcast.net> (raw)
In-Reply-To: <bd15db5f-2b22-3e89-d31a-2267dff70eba@xs4all.nl>
>> Hi Hans,
>> It doesn’t keep failing for me because the fix is well documented, so I fixed it on my machine. I am just imagining that it might be nice to put that fix in the modules that people download. For example, a teacher wants to help me test my book, so he followed the instructions on the wiki to instal ConTeXt (LMTX) and the modules (https://wiki.contextgarden.net/Modules). Then he had to go in and change two commands the file:
>> context-osx-64/tex/texmf-modules/generic/pgfplots/pgfplots.code.tex
>> The changes are:
>> Line 7928: change “\begin{axis}" to “\axis”
>> Line 7934: change “\end{axis}" to “\endaxis”
>> Then everything is great.
>> I don't know where the modules live and how they are maintained, but if this fix could be put into those modules before people download them, that would be helpful as I add more collaborators.
> it makes no sense to mojca to fix modules that come from elsewhere because a next time it might be different so when tikz is not updated on ctan (where it's fetched from) it's not an official fix
>
> (a well documented tikz fix that doesn't go into tikz is not really a fix, is it?)
>
> Hans
TikZ is fixed on ctan (based on the fixed version in my TeXLive distribution). Mojca has directed me to a fixed version at distribution.contextgarden.net. I’m trying to figure out why my collaborator and I did not get that fixed version when we followed the instructions at https://wiki.contextgarden.net/Modules#ConTeXt_LMTX. I’ll keep working on it.
Gavin
___________________________________________________________________________________
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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2021-08-22 16:30 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-21 4:05 Gavin via ntg-context
2021-08-21 11:26 ` Mojca Miklavec via ntg-context
2021-08-21 12:02 ` Hans Hagen via ntg-context
2021-08-22 12:25 ` Gavin via ntg-context
2021-08-22 13:20 ` Hans Hagen via ntg-context
2021-08-22 13:42 ` Gavin via ntg-context
2021-08-22 14:13 ` Hans Hagen via ntg-context
2021-08-22 14:32 ` Gavin via ntg-context
2021-08-22 16:13 ` Hans Hagen via ntg-context
2021-08-22 16:27 ` Mojca Miklavec via ntg-context
2021-08-22 17:32 ` Gavin via ntg-context
2021-08-22 17:36 ` Mojca Miklavec via ntg-context
2021-08-22 21:19 ` Gavin via ntg-context
2021-08-22 16:30 ` Gavin via ntg-context [this message]
2021-08-22 16:57 ` Mojca Miklavec via ntg-context
2021-08-22 14:44 ` Mojca Miklavec via ntg-context
2021-08-22 15:45 ` Gavin via ntg-context
2021-08-22 16:00 ` Mojca Miklavec via ntg-context
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=4894015E-2754-493D-BF1B-A6FFA0B4944D@comcast.net \
--to=ntg-context@ntg.nl \
--cc=gavinpublic@comcast.net \
--cc=j.hagen@xs4all.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).