ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Aditya Mahajan <adityam@umich.edu>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Christian Feuersaenger <cfeuersaenger@googlemail.com>
Subject: Re: TikZ bug fixing (git, minimals, ...)
Date: Mon, 12 Sep 2011 11:32:55 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LNX.2.02.1109121129300.5124@ybpnyubfg.ybpnyqbznva> (raw)
In-Reply-To: <CALBOmsZoh=ccGwTixAEQZjLL6WayK-LURfa3FWSnn3AXweBn9w@mail.gmail.com>

On Mon, 12 Sep 2011, Mojca Miklavec wrote:

> We definitely need some ConTeXt specific bug tracking with automatic
> email reminders for pgf developers to fix those bugs ;) ;) ;)

Another option is to rewrite all the code in $TEXMF/tex/context/pgf 
directory in a more ConTeXtist way. Mainly this means writing a catcode 
table (as my example showed) and enabling them in each file. One could 
also consider using the standard \startmodule ... \stopmodule tags around 
each module.

I can do that rewrite, but someone else will need to test all the changes 
as I don't use pgf/tikz.

> I also have commit rights for TeX Live, but I don't dare applying
> patches without having them applied upstream. If nothing else, that
> just postpones the problem to the time after PGF will release a new
> version and that one won't work.

Please don't do that. In the worst case, it will be better to release a 
module with the different name rather than silently overwriting PGF files.

Aditya
___________________________________________________________________________________
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
___________________________________________________________________________________


      parent reply	other threads:[~2011-09-12 15:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-12  9:51 Mojca Miklavec
2011-09-12 15:14 ` Philipp A.
2011-09-12 21:00   ` Mojca Miklavec
2011-09-12 21:37     ` Aditya Mahajan
2011-09-13  6:33   ` Mojca Miklavec
2011-09-14  9:08     ` Philipp A.
2011-09-14 10:38       ` Mojca Miklavec
2011-09-12 15:32 ` Aditya Mahajan [this message]

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=alpine.LNX.2.02.1109121129300.5124@ybpnyubfg.ybpnyqbznva \
    --to=adityam@umich.edu \
    --cc=cfeuersaenger@googlemail.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).