Re: How to wait for a key press

2017-12-21 Thread tscv11
Wow, there's some neat stuff in there, thanks! However, If I'm not mistaken, no values are passed outside the class definition. Perhaps there's no way to do that. Or did I just miss it? Anyway I did enjoy the example of the @g.command decorator and I'm learning how it works - I just ran the

Re: How to wait for a key press

2017-12-21 Thread Terry Brown
On Thu, 21 Dec 2017 16:31:11 -0800 T C wrote: > That clears it up a lot - I'm looking forward to the upcomming > snippet, though! Here's some code that adds a `get-db-stuff` command to Leo, which can be run with Alt-X. ---cut here--- from leo.core.leoQt import QtWidgets

Re: How to wait for a key press

2017-12-21 Thread T C
That clears it up a lot - I'm looking forward to the upcomming snippet, though! tsc On Thu, Dec 21, 2017 at 4:22 PM, Terry Brown wrote: > On Thu, 21 Dec 2017 15:13:19 -0800 > T C wrote: > > > That made it easy to understand. I do have a question

Re: How to wait for a key press

2017-12-21 Thread Terry Brown
On Thu, 21 Dec 2017 15:13:19 -0800 T C wrote: > That made it easy to understand. I do have a question about g.es - > is there any reason to use it instead of print? Well no, except that it shows up in the Leo log, which is where I was running the code. > Now, I understand -

Re: Linking to nodes from lines in the log.

2017-12-21 Thread tscv11
This is exciting - I was just wondering why Leo didn't do that already and now here it is! Having links to lines/columns will be brilliant! Thanks for this. tsc -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and

Re: Linking to nodes from lines in the log.

2017-12-21 Thread Edward K. Ream
On Thu, Dec 21, 2017 at 1:00 PM, Terry Brown wrote: These changes (please review, Edward): > https://github.com/leo-editor/leo-editor/compare/master...log_links ​Looks good. Feel free to merge, providing all unit tests pass. Extending various methods by adding a new

Re: How to wait for a key press

2017-12-21 Thread T C
Thanks for your repy, That's an interesting bit of code showing a function that dynamically creates other functions. For a minute it confused me so I added a print statement like so: def test(): funcs = [] for i in range(5): --> print(i) def func(n=i): g.es(i, n)

Linking to nodes from lines in the log.

2017-12-21 Thread Terry Brown
This is discussion of https://github.com/leo-editor/leo-editor/issues/635 moved here just to get maximum audience. These changes (please review, Edward): https://github.com/leo-editor/leo-editor/compare/master...log_links add hyperlinks in the log pane that link to nodes in the outline. An

Re: How to wait for a key press

2017-12-21 Thread Terry Brown
On Wed, 20 Dec 2017 21:42:52 -0800 T C wrote: > Hello, > > I got a little worked up but the fact is you shared a lot with me, > which I appreciate. I am willing to study Leo in depth - if you can > drop a few more clues I might figure things out. I find the code you > wrote

Re: How to wait for a key press

2017-12-21 Thread Terry Brown
On Wed, 20 Dec 2017 14:55:56 -0800 (PST) tscv11 wrote: > Hello, > > Okay, so you're saying it's too complicted to wait for a key press or > detect the vr pane being, > hidden, which seems a bit crazy - at least the key press part. I It's not so much that they're impossible