locate one node by it's path via leoBridge

Dear Leo User, I want to access the headline and body of a specific node inside that file using the leoBridge interface. Is it possible to get the body and headline from the path of that node? For example, for one node with headline "Display Message":

clone short cut for Mac

Hello Mac Leo User, Please how to clone a node via keyboard? It should be Ctrl-` , but I tried Command-` , Control-`, Option-`, no one works... Also, Alt-x on my key board doesn't work too.. BR,Austin -- You received this message because you are subscribed to the Google Groups

Re: Status report: #1289: singleton docks

On Fri, Aug 23, 2019 at 11:09 AM Edward K. Ream wrote: > More importantly, this suggests using Leo's existing code almost completely unchanged. I have just created the gui2 branch, based on the gui branch, for this experiment. The experiment was successful. I've merged gui2 back into the gui

Re: Status report: #1289: singleton docks

On Friday, August 23, 2019 at 7:40:32 AM UTC-5, Chris George wrote: I will once again put my hand up to try to preserve the ability to make the > body dock the central widget. > I'm very glad you mentioned this. It got me thinking about QMainWindows. Turns out that I forget that DynamicWindows

Re: New Themes

> > After using venv, pyenv, and conda and having them all display the same > problems I can pretty much say that it has nothing to do with the pyqt > version and everything to do with virtual python environments. > > When you did your testing were you using a virtual environment? If so, >

Re: Refactoring probably means using signals

When we talked about this previously I looked at https://pythonhosted.org/blinker/ and it seemed quite good, trying to find it again I also see https://github.com/dgovil/PySignal "A purely Python implementation of the Qt signal system with no QObject dependencies" if you want to think about

Refactoring probably means using signals

Leo's code is a behemoth. Nothing we can do is going to drastically shrink it, or make it a snap to understand or change. Imo, using Qt's signals more effectively is likely to be the best way to simplify Leo's code *just a little bit.* This page

Re: dabbrev-expand command question

On Wed, Aug 21, 2019 at 1:34 PM gar wrote: > > > When I am doing alt+/ (to quickly call dabbrev-expand), select match and > then save the project with ctrl-s - the expanded text disappears. > If I enter some more letters - everything is ok. > > I think this is a bug. > I agree. I've just

Re: New Themes

On Tue, Aug 20, 2019 at 10:44 AM Chris George wrote: It looks like the themes are supplanting font info but not anything else. > I agree. That's why I created #1298 . Edward -- You received this message because you are subscribed to the

Re: Status report: #1289: singleton docks

On Fri, Aug 23, 2019 at 7:40 AM Chris George wrote: > I will once again put my hand up to try to preserve the ability to make > the body dock the central widget. > I'll keep this in mind. Remember, though, that there may be several body docks in an outline. We'll have to see what works.

Re: Status report: #1289: singleton docks

I will once again put my hand up to try to preserve the ability to make the body dock the central widget. It is central to how I work with Leo. I have quickly become fond of the two-pane workspace and that falls apart if my only option is to nest the widgets on top of the body instead of the tree.

Re: Status report: #1289: singleton docks

On Fri, Aug 23, 2019 at 1:57 AM Edward K. Ream wrote: #1289 is a > precondition for pyzo in Leo. There was big progress yesterday. > A few more notes: As of rev cf990e3, the new Outlines dock is always Qt's central widget (in the gui

Status report: #1289: singleton docks

#1289 is a precondition for pyzo in Leo. There was big progress yesterday. *Status* The code creates an *Outlines dock*, containing one tab for each Leo outline. Each of these tabs contains what might loosely be called an *outline