Re: Last call before deprecating the nested_splitter plugin

On Thu, May 23, 2024 at 10:39 AM Thomas Passin wrote: [The free_layout.get_top_splitter] method is used by the *richtext* plugin > as well as the flc itself. > Good catch. I'll convert the richtext plugin. Edward -- You received this message because you are subscribed to the Google Groups "l

Re: Last call before deprecating the nested_splitter plugin

Speaking of which, the free layout controller still has this method: def get_top_splitter(self) -> Optional[Wrapper]: """Return the top splitter of c.frame.top.""" f = self.c.frame if hasattr(f, 'top') and f.top: child = f.top.findChild(*NestedSplitter*) *<*

Re: Expect Leo 6.8.0 b1 on Friday, May 31

On Thursday, May 23, 2024 at 10:25:06 AM UTC-5 Edward K. Ream wrote: Work is substantially complete on Leo 6.8.0, but there is plenty of time for tweaks. There are four delegated items scheduled for 6.8.0

Expect Leo 6.8.0 b1 on Friday, May 31

Work is substantially complete on Leo 6.8.0, but there is plenty of time for tweaks. The beta version/s will allow us to find kinks in the distribution process. Expect 6.8.0 final one or two weeks after b1. Edward -- You received this message because you are subscribed to the Google Groups "

Re: Last call before deprecating the nested_splitter plugin

On Thu, May 23, 2024 at 7:00 AM Thomas Passin wrote: Is it correct that the "main" splitter is the one whose splitter bar runs > all the way either from top to bottom or from side to side, depending on > orientation? > Yes, kinda. But you shouldn't take my word for it. Consult the code! Search

Re: Last call before deprecating the nested_splitter plugin

Is it correct that the "main" splitter is the one whose splitter bar runs all the way either from top to bottom or from side to side, depending on orientation? On Thursday, May 23, 2024 at 5:10:32 AM UTC-4 Edward K. Ream wrote: > On Wed, May 22, 2024 at 5:50 PM Thomas Passin wrote: > > I'd lik

Two PRs merged into devel

PR #3911 deprecates the free_layout and nested_splitter plugins. This is a breaking change, so Leo's next version will be 6.8.0. PR #3913 fixes a crasher on MacOS. PR #3911 is a *starting p

Re: Last call before deprecating the nested_splitter plugin

On Wed, May 22, 2024 at 5:50 PM Thomas Passin wrote: I'd like to have a command to place the log frame into its own panel next > to the body editor's. > ... > So there should be three built-in layouts instead of two, and there should > be a command or commands similar to *toggle-split-direction*

Re: The improved restart-leo command

On Thu, May 23, 2024 at 3:20 AM Viktor Ransmayr wrote: > Hello Thomas, > > Thanks a lot for your response. > And thanks, Thomas, for all your work supporting Leo. ...you have to be in the *leo-editor* directory to be able to find > *leo.core.xxx*, etc. > > I was not aware, that I have to star

Re: The nested-splitter project has collapsed in complexity

On Wed, May 22, 2024 at 11:07 PM Thomas Passin wrote: > On Tuesday, May 21, 2024 at 3:36:03 PM UTC-4 Thomas Passin wrote: > > VR3 is working with *ekr-3910-no-fl-ns-plugins*, possible quirks aside. > Will check soon on Linux. Freewin is working. RPCalc is still working. > > > OK on linux so far

Re: The improved restart-leo command

Hello Thomas, Thanks a lot for your response. Am Mi., 22. Mai 2024 um 20:02 Uhr schrieb Thomas Passin : > What directory are you running the tests from? As documented in the logs I'm running the tests in both PyVEs out of " ~/PyVE/GitHub/Leo/leo-editor/leo/" > Unless you set the right one us