ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: "luigi scarso" <luigi.scarso@gmail.com>
To: "mailing list for ConTeXt users" <ntg-context@ntg.nl>
Subject: Re: {{ double braces }}
Date: Wed, 13 Feb 2008 11:38:13 +0100	[thread overview]
Message-ID: <fe8d59da0802130238p1d3ce646rb7ded90826008127@mail.gmail.com> (raw)
In-Reply-To: <47B2C490.4000408@elvenkind.com>

>  > A bit off-topic:
>  > suppose that I , while I'm making format , I need to trace macro definitions
>  > (\edef,\xdef,\def,\let and eventually alias like \let\define\def, so
>  > also \define too,...)
>  > This can be do only hacking  web source , or not ?
>
>  If you set
>    \tracingassigns=1
>    \tracingrestores=1
>  you will get a dump in the log of all assignments (and that
>  includes definitions) as well as restores.
>
>  You will not get the full definitions of macros though, just the
>  first 32 tokens. If you want the full definition, you really have
>  to hack the web source.

ok, I suppose it.
Hacking the web source should be also permit to trace  primitive of luatex .

Thank you very much

-- 
luigi
it's new .
it's powerful .
it's luatex .
http://www.luatex.org
___________________________________________________________________________________
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
___________________________________________________________________________________


  reply	other threads:[~2008-02-13 10:38 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-21 14:45 Steffen Wolfrum
2008-01-21 15:02 ` Mikael Persson
2008-01-21 15:53   ` Steffen Wolfrum
2008-01-23 20:49 ` Peter Münster
2008-01-23 21:50   ` Peter Münster
2008-01-23 22:17     ` Thomas A. Schmitz
2008-01-23 23:19       ` Aditya Mahajan
2008-01-26 10:11         ` Thomas A. Schmitz
2008-02-06  7:01           ` Aditya Mahajan
2008-02-06  9:11             ` Steffen Wolfrum
2008-02-06 16:36               ` Aditya Mahajan
2008-02-06 19:20                 ` Hans van der Meer
2008-02-06 20:01                   ` Steffen Wolfrum
2008-02-06 20:16                     ` Hans van der Meer
2008-02-06 20:17               ` Otared Kavian
2008-02-12 15:09             ` Thomas A. Schmitz
2008-02-12 15:15               ` Hans Hagen
2008-02-12 17:39                 ` Aditya Mahajan
2008-02-13  8:39                   ` Taco Hoekwater
2008-02-13  9:31                     ` luigi scarso
2008-02-13 10:21                       ` Taco Hoekwater
2008-02-13 10:38                         ` luigi scarso [this message]
2008-01-26 10:52       ` Taco Hoekwater
2008-01-26 11:41         ` Taco Hoekwater

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=fe8d59da0802130238p1d3ce646rb7ded90826008127@mail.gmail.com \
    --to=luigi.scarso@gmail.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).