The nested-splitter project has collapsed in complexity

PR #3911 eliminates the free_layout and nested splitter plugins. This work has reached a milestone. A single method, *LeoQtGui.find_widget_by_name*, replaces both plugins! The node *g.command('vr')* shows the *new world order*. See the PR.

Re: Status report re PR #3911

On Thu, May 16, 2024 at 10:14 PM Thomas Passin wrote: This will be complicated enough and have a potentially big impact on > existing code and users that I'd like to see a concept of operations and > some requirements. Every time I wake up the project (PR #3911) gets simpler! It looks like a

Re: Status report re PR #3911

On Thursday, May 16, 2024 at 1:44:43 PM UTC-5 Edward K. Ream wrote: >> I hope that existing GUI plugins that use the nested-splitter/free-layout will be able to continue working without needing to be reworked > When True, the *g.allow_nested_splitter* switch enables both plugins

Re: Status report re PR #3911

On Thursday, May 16, 2024 at 9:49:43 AM UTC-5 Thomas wrote: I'm very enthusiastic about this work. It will eventually be a real boon to users and developers, I'm sure. Glad you like the concept. I hope that existing GUI plugins that use the nested-splitter/free-layout will be able to

Status report re PR #3911

PR #3911 contains preliminary work on deprecating Terry's trailblazing free_layout and nested_splitter plugins. This post is a progress report. *Goals* Scripts (@button nodes) and plugins should be able to do the following* easily *and

Re: glitches installing and starting Leo

On Wednesday, May 15, 2024 at 11:22:18 AM UTC-5 Thomas wrote: The TypeError message is from the spellchecker. Correct. #3912 is the issue and PR #3913 contains the proposed fix.

Re: glitches installing and starting Leo

On Wed, May 15, 2024 at 10:23 AM andyjim wrote: > Thanks Edward and tbp1 (Thomas, is it?) You're welcome. Yes, it's Thomas Passin. I just rolled the dice and figured it shouldn't hurt to just install again. > Very brave :-) Leo launched, but no menu bar. Also got TypeError. Here is the

Re: glitches installing and starting Leo

On Wed, May 15, 2024 at 8:50 AM Thomas Passin wrote: > It's a little hard to help with Mac-related problems because most of the > developer-minded people (like Edward and myself) don't have Macs to try > things out on. I do have a Mac, but I have been lax about testing. I typically update Leo

Re: glitches installing and starting Leo

On Wed, May 15, 2024 at 6:54 AM andyjim wrote: > I spoke from frustration, sir. I should not complain so loudly on day one. > No I don't have the complete message. Should I uninstall and start over? > If so, how do I uninstall? > It would be helpful if you could reproduce the message. `pip

Re: glitches installing and starting Leo

On Tue, May 14, 2024 at 7:46 AM andyjim wrote: > Leo seems like a tough road for a non-techie. My apologies. It shouldn't the *that* tough :-) > It was a challenge just installing it (on Mac 14.4.1), and Terminal gave me an error: > TypeError: expected str, bytes or os.PathLike object, not

ENB: More about the VR and free_layout plugins

This Engineering Notebook post continues a previous entry concerning Leo's VR and free_layout plugins. I've revised my thoughts while working on PR #3893 . *The free_layout plugin*

Re: A Script To Display The Viewrendered3 Pane in the Same Place s The Body

On Mon, May 13, 2024 at 9:38 AM Thomas wrote: >> Thomas, your private email on this topic was a Eureka moment for me. I realized that we Leo devs aren't aware of the hierarchy of Leo's Qt widgets. > That's an understatement! - at least for me... It explains why I had so much trouble discovering

Re: A Script To Display The Viewrendered3 Pane in the Same Place s The Body

On Sunday, May 12, 2024 at 4:17:19 PM UTC-5 tbp1...@gmail.com wrote: I have devised a script that can [swap the body and VR3 panes]. You can put it into a button for easy activation, or you could make it into a command in the Settings tree and bind it to a keystroke. Thomas, your private

Re: Big Ruff Speedup

On Sat, May 11, 2024 at 10:04 AM Thomas Passin wrote: > The Ruff Python linter, written in Rust, has just gotten a big increase in > speed. The old ruff was already essentially instantaneous :-) Edward -- You received this message because you are subscribed to the Google Groups

Re: ENB: VR panes and the NestedSplitter plugin

On Friday, May 10, 2024 at 1:18:49 PM UTC-5 Thomas wrote: >>>Going by last night's devel rev, VR was close to working as expected when I used the toggle command, at least with the particular layout I was using when I tried it. > Turns out it was only for one particular layout. When I tried

Re: ENB: VR panes and the NestedSplitter plugin

On Friday, May 10, 2024 at 8:47:46 AM UTC-5 Thomas wrote: Going by last night's devel rev, VR was close to working as expected when I used the toggle command, at least with the particular layout I was using when I tried it. That's good to know. The branch for this PR, though, was a mess so

ENB: VR panes and the NestedSplitter plugin

This Engineering Notebook post discusses issues with the nested_splitter (NS) plugin uncovered two days ago while working on #3892 : Add VR commands to cover/uncover the body pane. I've been considering what to do ever since. *tl;dr*:

Re: TLA+: Format Verification Language And Toolkit

On Thu, May 9, 2024 at 9:17 AM Thomas Passin wrote: > I always thought that formal verification (FV) of programs would be too > hard and error prone beyond simple programs. Apparently I was wrong about > that, and one reason is that FV should be applied above the program level - > e.g., to

Re: Another YouTube video worth watching twice

On Thu, May 2, 2024 at 11:13 AM Jacob Peck wrote: > Semi-related, James P. Carse's book "Finite and Infinite Games" is a good, > if occasionally overtly-spiritual (and easily enough ignored if that kind > of thing isn't for you), look at life through the lens of games. > > Weirdly, I find all of

Re: How to Modify LeoJS From Within LeoJS?

On Tuesday, April 30, 2024 at 10:52:57 AM UTC-5 Thomas wrote: Using Leo, we can edit LeoPyRef, save the edits, restart Leo, and test our changes. With LeoJS, how can we do the equivalent: editing the code of LeoJS and testing it? Interesting question. I am using a hybrid approach: Develop

DARPA's *public* projects

This YouTube video discusses DARPA's *public* projects. I recommend watching it once :-) Two big surprises: - DARPA is working on all the evident problems with AI. - Many of DARPA's projects are public collaborations with business and academia.

Another YouTube video worth watching twice

This video is about game theory and its implications for us and the world. None of us specializes in this area of mathematics so we will all learn a lot. It changed my view of the world. It will likely change yours. I've just watched this video a

Re: What The Ultimate Study On Happiness Reveals

On Thu, May 2, 2024 at 10:12 AM Thomas Passin wrote: > I haven't watched it yet, but I am sure that many people labor under a > mistaken notion. Happiness isn't something that you achieve and then you > just have it. Happiness is a temporary condition, one that you get used to > and it just

What The Ultimate Study On Happiness Reveals

No matter how happy we are, it is good to know explicitly (and in detail) what makes people happy. And what doesn't. This video discusses the science of happiness. It's worth watching twice, as I have just done. I highly recommend this video to

Re:  LeoJS Beta 0.2.13 Released

On Wed, May 1, 2024 at 8:02 PM Félix wrote: > Thanks Edward, Thomas and Viktor for the bug reports and feature requests > you've filed on the repository! You're welcome. I'm enjoying the transition to LeoJS! (I've now added an *issue template* to help remind leonistas to grab a > screenshot

Re:  LeoJS Beta 0.2.13 Released

On Tuesday, April 30, 2024 at 9:46:00 AM UTC-5 Edward K. Ream wrote: I have filed some *minor* LeoJS issues: #123 <https://github.com/boltex/leojs/issues/123>, #124 <https://github.com/boltex/leojs/issues/124>, #125 <https://github.com/boltex/leojs/issues/125>, #126 <http

Re:  LeoJS Beta 0.2.13 Released

On Tue, Apr 30, 2024 at 9:52 AM Thomas Passin wrote: >> I can now recommend LeoJS without reservation! LeoJS supports all of Leo's essential features enhanced with vs-code's stupendous capabilities. > I can't go that far at this time because I depend on several GUI plugins I've written. Fair

Re:  LeoJS Beta 0.2.13 Released

On Monday, April 29, 2024 at 9:41:57 AM UTC-5 Edward K. Ream wrote: This release of LeoJS is a personal milestone. I shall work on the remaining *desktop* issues using LeoJS! I can now recommend LeoJS without reservation! LeoJS supports all of Leo's essential features enhanced with vs-code's

Re:  LeoJS Beta 0.2.13 Released

On Monday, April 29, 2024 at 5:13:42 AM UTC-5 Edward K. Ream wrote: I've been playing with LeoJS, and it looks great. I'll be using LeoJS more now. This release of LeoJS is a personal milestone. I shall work on the remaining *desktop* issues using LeoJS! Edward -- You received this message

Re: ENB: Seconds thoughts about Trilium Notes

On Sun, Apr 28, 2024 at 1:43 PM Thomas Passin wrote: > It is possible to try out having VR/VR3 display in the same frame as the > body editor. You can get them both into the Log frame. ... > A screen shot illustrating this layout is attached. > Many thanks for all your comments. The design

Re:  LeoJS Beta 0.2.13 Released

On Sun, Apr 28, 2024 at 10:46 PM Félix wrote: *Introducing LeoJS Beta 0.2.13*  Congratulations! I've been playing with LeoJS, and it looks great. I'll be using LeoJS more now. LeoJS is already a viable alternative to desktop leo. It will be valuable to compare the vs-code way with the Leo

Re: ENB: Seconds thoughts about Trilium Notes

On Friday, April 26, 2024 at 2:50:16 PM UTC-5 Edward K. Ream wrote: > I'm convinced. Replacing the body pane is a preference worth considering. See #3892 <https://github.com/leo-editor/leo-editor/issues/3892>. The corresponding PR will make minimal changes to Leo's core and the V

Re: On Leo's strengths outside the technical

On Friday, April 26, 2024 at 5:03:06 PM UTC-5 Matt wrote: *On the topic of Leo--Trilium and Leo's strengths, something not mentioned there so far but I feel worth lifting out into a distinct theme instead: longevity, centrality, and community.* Thanks for the kind words, Matt. Leo's

Re: ENB: Seconds thoughts about Trilium Notes

On Fri, Apr 26, 2024 at 2:38 PM Thomas Passin wrote: The Easter Egg is the only way to expand the VR pane. An optional floating > VR window would solve that problem. > > > Here you go: > > ns = c.free_layout.get_top_splitter() > ns.open_window('_leo_viewrendered3') > Wow. Thanks for this. And

Re: ENB: Seconds thoughts about Trilium Notes

On Fri, Apr 26, 2024 at 11:49 AM Thomas Passin wrote: >> Trilium undervalues the power of text: > I think that Edward does not appreciate how often users want to use Leo as a Notebook... I agree. Leonistas *should *be able to use lots of graphics :-) That's why improving the VR plugins and

Re: ENB: Seconds thoughts about Trilium Notes

On Fri, Apr 26, 2024 at 8:02 AM Thomas Passin wrote: >> As an option, the VR pane could become a floating window. > This is already possible, at least with VR3. With VR3 enabled, right click on the boundary between two frames to get the splitter menu. Select *Window* then *VR3*. VR3 opens in

ENB: Seconds thoughts about Trilium Notes

This Engineering Notebook post contains second thoughts about Trilium Notes. *tl;dr:* Leo might add only *incremental *improvements inspired by Trilium Notes. All fundamental aspects of Leo will remain as they are. *Leo's body pane* Yesterday, I proposed that Leo's body might contain either

Re: A Leo relative in the wild: Trilium Notes

On Thursday, April 25, 2024 at 6:57:17 AM UTC-5 Thomas wrote: Hmm, instead of rendering those nodes in a separate frame as VR/VR3 does, we could overlay the rendering frame over the editing frame. We could switch in and out of rendering mode to allow editing. I bet that wouldn't be too hard.

Re: A Leo relative in the wild: Trilium Notes

On Thu, Apr 25, 2024 at 6:57 AM Thomas Passin wrote: > Except that standard Leo nodes don't render graphics and other non-text > items. That's a big difference. We get around it to a degree with VR/VR3. > Hmm, instead of rendering those nodes in a separate frame as VR/VR3 does, > we could

Re: Leo 6.7.8 released to pypi

On Thursday, March 28, 2024 at 9:44:52 AM UTC-5 iamap wrote: > When I using `pipx inject leo /Users/mac/Desktop/proj/leo-editor` for newest code. it throws: >error: package directory 'leo/doc/_static' does not exist > after `mkdir -p leo/doc/_static`, it works as before. > Maybe we need an

Re: Current Devel Branch Fails To Start Using Python 3.9

On Wednesday, April 24, 2024 at 11:33:19 AM UTC-5 Edward K. Ream wrote: > PR #3885 <https://github.com/leo-editor/leo-editor/pull/3885> ...moves *from typing import TypeAlias* into the range of *if TYPE_CHECKING*: ... > Even if the import fails, only mypy will be affected. At worst,

Re: A Leo relative in the wild: Trilium Notes

On Thu, Apr 25, 2024 at 3:49 AM Christoph wrote: Of course, dealing with hierarchical data sooner or later requires a > mechanism that allows to put data in more than one branch of the > hierarchy so this seems to be a logical step. However, Leo has taken > this step more than 20 years ago and

Re: A Leo relative in the wild: Trilium Notes

On Wed, Apr 24, 2024 at 2:57 PM Matt Wilkie wrote: > Hello Leonistas, > > I've been exploring a program the last few weeks that seems like it might > be an answer to a long felt wish: to have a Leo-like experience for editing > and managing a rich text and media notes knowledgebase. That program

Re: Leo website suspended?

On Wed, Apr 24, 2024 at 12:03 PM Matt Wilkie wrote: > When I visit leoeditor.com today it redirects to > https://leoeditor.com/cgi-sys/suspendedpage.cgi > That's the old link, hosted by my brother. The correct link is: https://leo-editor.github.io/leo-editor/ Edward -- You received this

Re: Current Devel Branch Fails To Start Using Python 3.9

On Wednesday, April 24, 2024 at 10:02:34 AM UTC-5 Edward K. Ream wrote: Thanks for this report, Thomas. See #3884 <https://github.com/leo-editor/leo-editor/issues/3884>. I'll fix this immediately. PR #3885 <https://github.com/leo-editor/leo-editor/pull/3885> contains an elegant

Re: Current Devel Branch Fails To Start Using Python 3.9

On Wed, Apr 24, 2024 at 9:30 AM Thomas Passin wrote: > py -3.9 -m leo.core.runLeo > ... >from leo.core import leoVim > File "C:\Tom\git\leo-editor\leo\core\leoVim.py", line 25, in > from typing import Any, TypeAlias, TYPE_CHECKING > ImportError: cannot import name 'TypeAlias' from

Re: I plan no further work with Rust

On Tue, Apr 23, 2024 at 5:08 AM Christoph wrote: I came across something that looks a bit more like Python: zig ( > https://ziglang.org/) Thanks for the link! Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this

Re: Leo shortcut on windows fail with devel branch

On Mon, Apr 22, 2024 at 7:59 AM Thomas Passin wrote: > You can see what would get installed with requirements.txt by adding the > flag --dry-run. Thanks for this tip! Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from

New study outline: rust_beautifier.leo

I have just created #3874 as a placeholder for my recent prototype work on creating a Rust version of leoTokens.py. As mentioned in #3874, rust_beautifier.leo

Re: Leo shortcut on windows fail with devel branch

On Sun, Apr 21, 2024 at 7:55 PM Félix wrote: Searching for ' leo-message ' in Leo's codebase, I see the 'leo-message' > script is mentioned in 'running.html' > Thanks, Thomas, for your help. And thanks, Félix for reporting this problem. This glitch is what Viktor asked about several days ago.

Re: Leo shortcut on windows fail with devel branch

On Sun, Apr 21, 2024 at 5:37 PM Félix wrote: > I had to revert to the master branch on my windows pc to get the shortcut to work. leo-messages.exe probably isn't nefarious, but it sure is mysterious. Running *pip -r requirements.txt* should install the missing dependency. Edward -- You

Re: Leo shortcut on windows fail with devel branch

On Sun, Apr 21, 2024 at 5:37 PM Félix wrote: I had to revert to the master branch on my windows pc to get the shortcut > to work. > > It's the one that points to [Python]/Scripts/leo-messages.exe > I have no knowledge of this script! There is nothing suggestive of this file in the leo-editor

I plan no further work with Rust

PR #3870 failed to speed up Leo's beautifier but did speed up Leo's beautification scripts. As a result, I see no reason to transliterate leoTokens.py into Rust. I now know what programming in Rust feels like. Rust has its place, but I

PR #3870 merged into devel

The devel branch now contains PR #3870 . This PR concludes all planned work on Leo's beautifier, leoTokens.py. *Lazy evaluation* leoTokens.py now generates whitespace using *lazy evaluation*. It writes whitespace only when the

Re: ENB: leoTokens.rs: Leo's beautifier in Rust

On Wednesday, April 17, 2024 at 7:40:09 AM UTC-5 Edward K. Ream wrote: The perspective gained suggests a significant improvement to Leo's Python beautifier. It may be possible to speed up leoTokens.py significantly. The speedups would likely apply also to leoTokens.rs, but the faster

Re: ENB: leoTokens.rs: Leo's beautifier in Rust

On Wednesday, April 17, 2024 at 7:40:09 AM UTC-5 Edward K. Ream wrote: *Improving Leo's beautifier* Yesterday's work created a list of *output tokens* from the corresponding list of *input tokens*. Leo's beautifier does the same. But Aha! A simpler architecture *might* work: - Don't

ENB: leoTokens.rs: Leo's beautifier in Rust

Five days ago, on April 11, I started work on *leoTokens.rs*, a prototype transliteration of *leoTokens.py*, Leo's token-based beautifier. This work was my first significant Rust project. This Engineering notebook post discusses my experiences. I'll also discuss an idea for improving

Re: What's next for me

On Fri, Apr 12, 2024 at 9:47 PM Félix wrote: > I'm gonna quote our friend @Zoom.Quiet : "*of course thanx Leo again, > make me create so many kinds of projects so funny."* > > I don't know why, but I enjoy reading the way he wrote it. And to me this > is so true... It makes creating and

Re: Eight more PRs merged into devel

On Fri, Apr 12, 2024 at 1:25 PM Viktor Ransmayr wrote: > With the new simplified installation process from Leo 6.7.8 in place, I do have another ~ simple ~ question: *Is it safe to perform a 'git pull ...' operation* *-OR - * *is it always required to start with a 'git clone ...' & a

What's next for me

In my last post, I hinted that Leo has reached a milestone. Once again, little work remains. In particular, here are some projects that I *won't* do: - Revise Leo's design to aid annotations. - Use Qt Designer to simplify Leo's gui code. - Use stricter mypy settings or annotations to aid

Re: Eight more PRs merged into devel

On Thursday, April 11, 2024 at 5:25:03 AM UTC-5 Edward K. Ream wrote: Eight recent PRs complete all planned work involving Leo's annotations. I doubt that the improved annotations will have much effect on LeoJS. After all, Typescript encourages stricter annotations than Python does. The last

Eight more PRs merged into devel

Eight recent PRs complete all planned work involving Leo's annotations. You can see the list of all PRs here . I plan no further significant changes to Leo's codebase. Several ugly corners remain in

Two more PRs merged into devel

Both PRs strengthen Leo's mypy annotations. - PR #3856 completes the annotations in leoApp.py. - PR #3857 completes the annotations in leoGlobals.py The second PR is the big one.

Two PRs merged into devel

PR #3850 improves many annotations. This PR is too big for my liking. I'll make further improvements to annotations in smaller PRs. PR #3855 improves support for Ruff. Please see the

Re: A big hole in Python's checkers

On Mon, Apr 8, 2024 at 4:17 AM Edward K. Ream wrote: There is a surprising hole in Python's checkers: Ruff, Mypy, Pylint, and > Pyflakes. > Oh Joy, the Ruff devs plan to implement static type checking. See the response to Ruff issue #10833 <https://github.com/astral-sh/ruff/iss

A big hole in Python's checkers

There is a surprising hole in Python's checkers: Ruff, Mypy, Pylint, and Pyflakes. *The test file* Consider the following file: class Test: __slots__ = ('good',) def main(): t = Test() print(t.bad) main() When executing this file, Python throws an

Re: MACOS M2 Ventura

On Sat, Apr 6, 2024 at 6:27 AM Thomas Passin wrote: > Solved in > > > https://stackoverflow.com/questions/76898551/qt-qpa-plugin-could-not-find-the-qt-platform-plugin-cocoa-in Thanks for your help, Thomas. Edward -- You received this message because you are subscribed to the Google Groups

Re: MACOS M2 Ventura

On Mon, Apr 1, 2024 at 5:58 AM Geoff Evans wrote: > I've tried to get leo via pip: > > pip install pyqt6 leo > > but when I try to run it I get: > > ~/WXP/OGMAP/now/base > leo ogmap.leo > qt.qpa.plugin: Could not find the Qt platform plugin "cocoa" in "" > This application failed to start

Re: Leo 6.7.8 released to pypi

On Thu, Mar 28, 2024 at 9:44 AM HaveF HaveF wrote: When I using `pipx inject leo /Users/mac/Desktop/proj/leo-editor` for > newest code. it throws: > > [snip] > error: package directory 'leo/doc/_static' does not exist > Thanks for this report. See #3853

ENB: Leo's startup order

Recent ENBs have discussed two implicit graphs of import dependencies. Leo's fast pylint project, #3852 , will likely sidestep such issues. However, I laboriously calculated Leo's startup dependencies by hand. I'll present them here.

Design of a super-fast pylint

The previous Engineering Notebook post explained why type inference (and checking) is much easier than I ever imagined. This ENB will discuss a preliminary design of a new (super fast) pylint. Whenever I say "pylint," I'll mean the *new *pylint. *Ignore import graphs* In the last ENB, I

ENB: Big Aha re type inference

This Engineering Notebook post explains why type inference (and checking) is much easier than I ever imagined. For over a decade, I believed that (while doing type inference) *everything depends on everything else*. I thought inferring the types (of objects) in module *A* required

Re: Script to expand toolbar

On Wed, Apr 3, 2024 at 1:10 PM Thomas Passin wrote: > Better, I think: background-color: @text-foreground; This should work for > any (dark) color theme. If you omit the #qt_toolbar_ext_button, the style > will get applied to the menubar's "menu-indicator" also, as well as any > other toolbar

Re: Script to expand toolbar

On Wed, Apr 3, 2024 at 1:10 PM Thomas Passin wrote: > Better, I think: background-color: @text-foreground; This should work for > any (dark) color theme. If you omit the #qt_toolbar_ext_button, the style > will get applied to the menubar's "menu-indicator" also, as well as any > other toolbar

Re: Script to expand toolbar

On Wednesday, April 3, 2024 at 9:56:16 AM UTC-5 Edward K. Ream wrote: Googling shows that the QToolbar class has inherent limitations. There is *no way* to split QToolButton widgets into separate rows. This statement is misleading. The easiest workaround is to assign buttons/widgets

Re: Script to expand toolbar

On Wednesday, April 3, 2024 at 11:04:00 AM UTC-5 Tom wrote: It's not just a black background that hides it. There must be a css selector for it, mustn't there? Probably yes, but the defaults for buttons should work. Here is my selector: QToolButton#qt_toolbar_ext_button {

Re: Script to expand toolbar

On Wednesday, April 3, 2024 at 4:54:32 AM UTC-5 Edward K. Ream wrote: It took me a while to understand what the @button node is doing. ... I'm satisfied neither with #407 <https://github.com/leo-editor/leo-editor/issues/407> nor with the script. I would prefer some ways of splitting th

Re: Script to expand toolbar

On Tue, Apr 2, 2024 at 4:29 PM lewis wrote: > From original issue #407 - You can put that in *@button expand-toolbar* > node in your myLeoSettings.leo under @buttons node. > If it is first child of @buttons then this button will be on left side of > toolbar and it will be easier to click this

Re: Script to expand toolbar

ssion on the web visit > https://groups.google.com/d/msgid/leo-editor/6590e9b3-9ffa-4ed8-ba38-cf403c4ed62fn%40googlegroups.com > <https://groups.google.com/d/msgid/leo-editor/6590e9b3-9ffa-4ed8-ba38-cf403c4ed62fn%40googlegroups.com?utm_medium=email_source=footer> > . > -- -

Next steps for Leo

Here are my expectations and plans as I gradually resume work after eye surgery. - LeoInteg 1.0.20 contains significant UI improvements. I expect Félix will fold those improvements into LeoJS. That work shouldn't take too long, but that doesn't mean that LeoJS 1.0.0 will happen imminently.

Re: Script to expand toolbar

On Tuesday, April 2, 2024 at 4:25:35 AM UTC-5 lewis wrote: @vitalije first provided a script to expand the toolbar in https://github.com/leo-editor/leo-editor/issues/407 Here is an update that works with PyQt6 Hurray! I'll check it out soon! Edward -- You received this message because you

Re:  LeoInteg 1.0.20 Released

On Sat, Mar 30, 2024 at 10:47 PM Félix wrote: In the wake of the Leo 6.7.8 release, I'm thrilled to unveil the latest > version of LeoInteg, the VSCode extension that seamlessly integrates the > power of Leo into your coding environment. LeoInteg 1.0.20 is a more > intuitive, efficient, and

Re: LeoJS Status Report & Video Demo/Tutorial

On Sun, Mar 31, 2024 at 3:28 PM Félix wrote: https://www.youtube.com/watch?v=M_mKXSbVGdE *This five-minute video quickly goes over each of the following:* > >- Using LeoJS on the web >- Commits & pull requests from VSCode's UI >- Running Leo scripts in LeoJS >- Interacting with

Re: I just had successful eye surgury

On Thursday, March 28, 2024 at 3:03:52 PM UTC-5 Edward K. Ream wrote: A vitrectomy <https://www.hopkinsmedicine.org/health/wellness-and-prevention/vitrectomy#:~:text=A%20vitrectomy%20is%20a%20type,middle%20portion%20of%20your%20eye.>of the rt eye. I'll be limited in what I can do for

I just had successful eye surgury

A vitrectomy of the rt eye. I'll be limited in what I can do for about a week. Edward -- You received this message because you are subscribed

Re: PR #3842 merged into devel. Leo's headline decluttering should work as before

On Mon, Mar 25, 2024 at 1:54 PM jkn wrote: > Hi Edward > as it happens I have made a couple of local changes recently to > improve headline decluttering. After I am happy with them shall I submit a > pull request? > Please do! Edward -- You received this message because you are

PR #3842 merged into devel. Leo's headline decluttering should work as before

PR #3842 suppresses two pyflakes complaints in the code that does headline decluttering. The changes should be harmless. Please let me know if they aren't :-) Edward -- You received this message because you are subscribed to the Google

PR #3828 is now in devel

PR #3828 has been merged into devel. All known bugs have been fixed and Leo should continue to work as before. Please report any problem immediately. Edward -- You received this message because you are subscribed to the Google Groups

Re: Please test the ekr-2882-qt-only2 branch

On Monday, March 25, 2024 at 6:37:36 AM UTC-5 Edward K. Ream wrote: The "ekr-2882-qt-only2" branch is ready for testing. See PR #3828 <https://github.com/leo-editor/leo-editor/pull/3828>. This PR is a milestone: it removes all vestiges of Qt5 from Leo's codebase. As a resul

PR #3841 in devel: two great new tracing functions

PR #3841 (now in Leo's "devel" branch) adds two spectacularly useful tracing functions: *g.traceUnique* and *g.traceUniqueClass*. Both functions take one *value *argument (which can be of any type) and one keyword-only *n* argument that

Re: Please test the ekr-2882-qt-only2 branch

On Mon, Mar 25, 2024 at 8:45 AM Thomas Passin wrote: Nav tab is missing on Debian, Python Console tab is missing on Linux Mint. > No apparent error messages. > Thanks for your testing! Now I'll definitely delay the merge. Edward -- You received this message because you are subscribed to the

Re: Please test the ekr-2882-qt-only2 branch

On Mon, Mar 25, 2024 at 8:25 AM Thomas Passin wrote: What is Leo using QScintilla for? > For alternative syntax coloring, iirc. BTW, the best way to install requirements is: cd leo-editor pip install -r requirements.txt I've been talking to Rebecca about the transition process. The more I

Re: Please test the ekr-2882-qt-only2 branch

On Mon, Mar 25, 2024 at 7:47 AM Thomas Passin wrote: > Fails on Ubuntu: > > *cannot import name 'Qsci' from 'PyQt6' > (/home/tom/.local/lib/python3.10/site-packages/PyQt6/__init__.py)* > Good catch. My apologies for the confusion. This is a documentation error or a "transition" problem,

Please test the ekr-2882-qt-only2 branch

The "ekr-2882-qt-only2" branch is ready for testing. See PR #3828 . This PR is a milestone: it removes all vestiges of Qt5 from Leo's codebase. As a result, much stronger mypy annotations are possible, but improved annotations will be the

Re: About PR #3828: Require Qt6.6+

On Sun, Mar 24, 2024 at 7:53 AM Thomas Passin wrote: > Every one of my fleet of Linux VMs has finally got PyQt 6.6, so that's > favorable. No one can prove that *every* distro will have it - there are > just too many variations - but so be it. I don't know about ARM versions > and don't have a

Re: A Script To Insert An Image

On Sun, Mar 24, 2024 at 7:01 AM Thomas Passin wrote: > Settings and headlines are not the same. > At last I understand :-) As Thomas says, the syntax for settings nodes is different from directives. In other words, Leo's documentation appears to be correct. Edward -- You received this

Re: A Script To Insert An Image

On Sun, Mar 24, 2024 at 5:39 AM jkn wrote: I put the link (to a different part of the documentation) in an earlier > post: > https://leo-editor.github.io/leo-editor/customizing.html#simple-settings-nodes > Thanks. I'll take a look. Edward -- You received this message because you are

About PR #3828: Require Qt6.6+

I am now working on PR #3828 : require Qt 6.6+. This PR is experimental and possibly controversial. *The good news* - leoQt.py contains no conditional imports. - leoQt.py defines all constants unambiguously. - No Qt-related switches

Two PRs merged into devel

Leo's "devel" branch now contains two significant PRs: PR #3838 updates developer scripts that build and test Leo. The (newly revised) info issue #2867 lists these scripts. All these

Re: A Script To Insert An Image

On Sun, Mar 24, 2024 at 4:20 AM jkn wrote: > > I am commenting on the fact that the documentation says that an @path > directive (and all the others in the table below) takes the form > > @path **=** my/path > > whereas in fact no equals sign is necessary (any might well cause an > error?) > >

  1   2   3   4   5   6   7   8   9   10   >