From: Taco Hoekwater <taco@elvenkind.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: debugging
Date: Tue, 11 Nov 2008 12:08:57 +0100 [thread overview]
Message-ID: <491967C9.3000103@elvenkind.com> (raw)
In-Reply-To: <326847810811110245n78f15278qf8f3a8435b8ce688@mail.gmail.com>
Alan STONE wrote:
>
> I tried \tracingmacros=1 but that's not what I'm looking for.
\tracingassigns=1 is as close as you can get.
Otherwise, you will end up with extremely dangerous constructs
like this trick that may very well interfere with what you are
trying to debug:
\let\normaldef\def
\def\dumpDEF
{\immediate\write16
{\expandafter\string\theDEF=\expandafter\meaning\theDEF}}
\unexpanded\normaldef\def#1% yes, this redefines \def!
{\normaldef\theDEF{#1}\afterassignment\dumpDEF\normaldef#1}
Best wishes,
Taco
___________________________________________________________________________________
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 : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2008-11-11 11:08 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 10:45 debugging Alan STONE
2008-11-11 11:08 ` Taco Hoekwater [this message]
2008-11-11 13:03 ` debugging Alan STONE
2008-11-11 13:33 ` debugging Alan STONE
2008-11-11 13:39 ` debugging luigi scarso
2008-11-11 14:43 ` debugging Hans Hagen
2008-11-11 14:50 ` debugging Alan STONE
2008-11-12 9:51 ` debugging Mojca Miklavec
2008-11-14 15:48 ` debugging Alan STONE
2008-11-14 16:21 ` debugging Aditya Mahajan
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=491967C9.3000103@elvenkind.com \
--to=taco@elvenkind.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).