Hi, What's the way to get a list of all definition assigned values in a compile job ? Ex: \def\myFirstParameter{one} \def\mySecondParameter{two} ... -> in log file (or other file), something like: myFirstParameter=one myFirstParameter=two ... I tried \tracingmacros=1 but that's not what I'm looking for. -- Best, Alan * TeX engine = LuaTeX * ConTeXt minimals ver: 2008.56.06 19:11 MKIV fmt: 2008.11.10 int: english/english * Ubuntu 8.04 Hardy Heron
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
On Tue, Nov 11, 2008 at 12:08 PM, Taco Hoekwater
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.
Considering the enormous amount of information these \tracing* commands blurp into the log file, I think I'll read Tolstoy's "War and Peace" instead. ;O)
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}
Thanks a lot Taco. This is better already, though still too much information in the log file to be user friendly. Would it be possible to restricts the output to the \def'\s which begin with specific characters, for example "my" as in \def\my* ? Or... Do you know some tool (Windows/Linux) which enables to filter these from the log file into a text file, or delete the unwanted ones from the log file ? Best, Alan
On Tue, Nov 11, 2008 at 2:33 PM, Alan STONE
On Tue, Nov 11, 2008 at 2:03 PM, Alan STONE
wrote:
Do you know some tool (Windows/Linux) which enables to filter these from the log file into a text file, or delete the unwanted ones from the log file ?
Under Linux, grep should be able to do that. Under Windows ?
maybe grep of cygwin ? -- luigi
luigi scarso wrote:
On Tue, Nov 11, 2008 at 2:33 PM, Alan STONE
mailto:software.list.1es9s@gmail.com> wrote: On Tue, Nov 11, 2008 at 2:03 PM, Alan STONE
mailto:software.list.1es9s@gmail.com> wrote: Do you know some tool (Windows/Linux) which enables to filter these from the log file into a text file, or delete the unwanted ones from the log file ?
Under Linux, grep should be able to do that. Under Windows ?
maybe grep of cygwin ?
or mtxrun --script grep ... ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Tue, Nov 11, 2008 at 3:43 PM, Hans Hagen
luigi scarso wrote:
On Tue, Nov 11, 2008 at 2:33 PM, Alan STONE
mailto:software.list.1es9s@gmail.com> wrote: On Tue, Nov 11, 2008 at 2:03 PM, Alan STONE
mailto:software.list.1es9s@gmail.com> wrote: Do you know some tool (Windows/Linux) which enables to filter these from the log file into a text file, or delete the unwanted ones from the log file ?
Under Linux, grep should be able to do that. Under Windows ?
maybe grep of cygwin ?
or
mtxrun --script grep ...
This is a cool one... http://www.wingrep.com -- Best, Alan * TeX engine = LuaTeX * ConTeXt minimals ver: 2008.56.06 19:11 MKIV fmt: 2008.11.10 int: english/english * Ubuntu 8.04 Hardy Heron
On Tue, Nov 11, 2008 at 2:33 PM, Alan STONE wrote:
On Tue, Nov 11, 2008 at 2:03 PM, Alan STONE wrote: wrote:
Do you know some tool (Windows/Linux) which enables to filter these from the log file into a text file, or delete the unwanted ones from the log file ?
Under Linux, grep should be able to do that. Under Windows ?
This package is great: http://gnuwin32.sourceforge.net and grep is part of it. Mojca
Another debugging question: how do you return the filename of the file being compiled ? -- Best, Alan * TeX engine = LuaTeX * ConTeXt minimals ver: 2008.56.06 19:11 MKIV fmt: 2008.11.10 int: english/english * Ubuntu 8.04 Hardy Heron
participants (6)
-
Aditya Mahajan
-
Alan STONE
-
Hans Hagen
-
luigi scarso
-
Mojca Miklavec
-
Taco Hoekwater