On Tue, Mar 25, 2014 at 1:12 AM, Fidel N wrote:
> Edward, given you have your test code inside a node body, how would you run
> it with SherlockTracing and show the outcome in leo log pane?
> Is that possible?
The following is tested code::
patterns = ['+test*',]
sherlock = g.SherlockTracer(patt
Hi Terry,
Good to hear from you again. This seems like one tough bug. I dug some more
and found some more threads on this:
https://groups.google.com/forum/#!searchin/leo-editor/F.S./leo-editor/eH5cspNNOD0/SZm95-olO-EJ
https://groups.google.com/forum/#!searchin/leo-editor/F.S./leo-editor/vd2d3pMS_
On Tue, 25 Mar 2014 10:23:54 -0700 (PDT)
"F.S." wrote:
> So I anonymized the thing I was working on (I did notice that
> "replace all" is rather painfully slow and I don't know how to
> specify wildcard matching) and will attach it to the end of this
> post. I don't use any custom settings. If I
On Tue, Mar 25, 2014 at 12:37 PM, Terry Brown wrote:
> On Tue, 25 Mar 2014 10:23:54 -0700 (PDT)
> "F.S." wrote:
>
>> So I anonymized the thing I was working on...
>
> Thanks for doing that, it made it easy for me to test and confirm that
> the current gui hierarchy manipulating border code still
I was away after this thread:
https://groups.google.com/forum/#!searchin/leo-editor/F.S./leo-editor/2XqXrh_2a0c/c-m5t4CxD1IJ
and I came back to this post (also for reporting the same scroll jump
issue). It seems the clock didn't move (for me:-)
I read your post about M-H in the stc group. Didn't
On Tuesday, March 25, 2014 6:51:04 PM UTC-7, F.S. wrote:
>
> Didn't know that you are (were?) a closet Prolog user. ...
>
Doh. When I read that:
*Now, this should sound familiar if you've ever used Prolog—you're
essentially computing the proof tree like a human Prolog interpreter. There
is a
