Hello Edward,
Am Mo., 30. Sept. 2019 um 23:04 Uhr schrieb Edward K. Ream <
edream...@gmail.com>:
> On Sun, Sep 29, 2019 at 2:43 PM Viktor Ransmayr
> 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 ...
On Sun, Sep 29, 2019 at 3:59 PM Brian Theado wrote:
> I've discovered https://github.com/ionelmc/python-hunter and it is
> excellent. You can filter exactly which modules do and don't get traced and
> the colorized output looks nice.
>
Thanks for this link. I've bookmarked it.
Edward
--
You
On Sun, Sep 29, 2019 at 2:43 PM Viktor Ransmayr
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
Hello Brian,
Am So., 29. Sept. 2019 um 22:59 Uhr schrieb Brian Theado <
brian.the...@gmail.com>:
> Edward can speak to the built-in leo traces, but there are also other
> options.
>
> I mentioned in the thread at
> https://groups.google.com/forum/#!topic/leo-editor/r6ktpQNWySk, about
> using the
Edward can speak to the built-in leo traces, but there are also other
options.
I mentioned in the thread at
https://groups.google.com/forum/#!topic/leo-editor/r6ktpQNWySk, about using
the python trace module for debugging python applications, but I no longer
recommend using it because it is too
Hello Edward,
I tried to find out, if I can enable 'auditing/ tracing' for Leo in order
to 'visualize' the run-time behavior of Leo Core ...
I started with something, that I thought should/ would be an easy starting
point: I tried to audit/ trace what happens, when Leo opens an empty
outline
