On Sun, Sep 29, 2019 at 2:43 PM Viktor Ransmayr <viktor.ransm...@gmail.com>
wrote:

>
> I tried to find out, if I can enable 'auditing/ tracing' for Leo in order
> to 'visualize' the run-time behavior of Leo Core ...
>

The various --trace options are good if they tell you what you want to see.

Usually, I put g.trace statements into Leo's source code.  A cff shows
there are 414 nodes in Leo's code with such statements, so you shouldn't
have too much trouble finding examples :-)

Edward

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/CAMF8tS04WpTkhNO6B3G1CCJ%3DVvdqFcsjyzATD3V%2Bz1XGRiKXFw%40mail.gmail.com.

Reply via email to