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?) > >

Re: Leo 6.7.8 released to pypi

On Fri, Mar 22, 2024 at 12:33 PM Thomas Passin wrote: > I've tried out installing post3 on my fleet of Linux VMs. It succeeded on > all of them although for some I had to add the pip install option > *--break-system-packages. > *After installation, there was a also new "leo" script that

Re: Leo 6.7.8 released to pypi

> Leo 6.7.8.post3 is now working as expected in an existing 'venv' w/i a > Fedora 38 VM ! > Excellent. Thanks for your testing :-) Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails

Leo 6.7.8 released to pypi

Leo 6.7.8.post3 is now available on Leo's pypi page . This version installs leo.exe, leo-c.exe, and leo-console.exe in the "Python3.x/scripts" folder. These scripts work for me. This release concludes work on Leo 6.7.8. Onward! Edward -- You received

Re: ENB: Distribution challenges

On Wednesday, March 20, 2024 at 11:15:05 AM UTC-5 Edward K. Ream wrote: > This post will be pre-writing for a new info item. See #3837 <https://github.com/leo-editor/leo-editor/issues/3837>: How to create pypi distributions. I'll update this item as necessary. The "workflow&q

Re: ENB: Distribution challenges

On Monday, March 18, 2024 at 4:43:22 PM UTC-5 Edward K. Ream wrote: This Engineering Notebook post briefly summarizes the challenges in distributing Leo on pypi. Here is an update and summary: - PR #3835 <https://github.com/leo-editor/leo-editor/pull/3835> contains the latest code.

Re: Leo 6.7.8.post1 is ready for testing

On Wednesday, March 20, 2024 at 3:13:41 AM UTC-5 Viktor wrote: I installed Leo 6.7.8.post1 into an existing 'venv' on a Fedora 38 VM - but - I could NOT run it using the 'leo' cmd from the shell. I also tried installing Leo 6.7.8.post1 into a completely new Fedora 38 VM w/o using a 'venv' -

Leo 6.7.8.post1 is ready for testing

You can now install Leo *6.7.8.post1* from pypi . This "post" release changes only distribution-related files. See PR #3835 for the details. The "post1" prefix is required to meet the more stringent

Re: ENB: Distribution challenges

On Tue, Mar 19, 2024 at 9:03 AM Thomas Passin wrote: > > On Monday, March 18, 2024 at 5:43:22 PM UTC-4 Edward K. Ream wrote: > > *I would greatly appreciate help debugging either PR*. My *guess* is that > pyproject.toml needs only a tweak, but finding that tweak has

Re: ENB: Distribution challenges

On Tue, Mar 19, 2024 at 5:05 AM Edward K. Ream wrote: > In this kind of challenging project, I look for small gains. Here are today's: And one more. Now that I can test locally, there is no need for a timestamp. Indeed, the .toml file will be different, so the overall hash will be differ

Re: ENB: Distribution challenges

On Monday, March 18, 2024 at 4:43:22 PM UTC-5 Edward K. Ream wrote: This Engineering Notebook post briefly summarizes the challenges in distributing Leo on pypi. In this kind of challenging project, I look for small gains. Here are today's: *Test locally* *Aha/Doh*: test my wheel file

ENB: Distribution challenges

This Engineering Notebook post briefly summarizes the challenges in distributing Leo on pypi. PRs #3834 and #3835 (both drafts) contain the relevant code. *New security restrictions*

Re: Leo 6.7.8 released, but not to PyPi

On Mon, Mar 18, 2024 at 8:42 AM Thomas Passin wrote: > Then there's the brute force method - get the zip file from github, unzip > it, and copy the leo directory into the user's site-packages directory. Thanks to you and Viktor for your comments. I'll be writing an Engineering Notebook post

About pip install leo

I have been working on distribution issues for Leo 6.7.8 for several days. This an extremely challenging project: - New pypi security measures prevent uploads of files with identical contents or names. This restriction causes surprising difficulties. - One would think that creating a

Re: TIL in Leo: environment variables are expanded in @url parameters

On Sun, Mar 17, 2024 at 6:35 AM jkn wrote: > I tried this, fully expecting it to fail, but it works! > Heh. I would have expected it not to work, but then, what do I know :-) Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To

Re: Leo 6.7.8 fully released

On Fri, Mar 15, 2024 at 9:37 AM Edward K. Ream wrote: > Leo https://leo-editor.github.io/leo-editor/ 6.7.8 is now available on > GitHub <https://github.com/leo-editor/leo-editor/releases>, *including * > pypi <https://pypi.org/project/leo/>. > Well, the PyPi version exis

Leo 6.7.8 fully released

Leo https://leo-editor.github.io/leo-editor/ 6.7.8 is now available on GitHub , *including *pypi . I'll wait at least until Monday before announcing Leo 6.7.8 more widely. *The highlights of Leo 6.7.8* This

Leo 6.7.8 released, but not to PyPi

Leo https://leo-editor.github.io/leo-editor/ 6.7.8 is now available on GitHub but *NOT *on pypi . I have filed this twine issue . I am enraged by the difficulties of

Re: Leo 6.7.8 is coming this Friday, March 15

On Thu, Mar 14, 2024 at 5:57 PM Félix wrote: > No problem with me, I'll release a new LeoInteg version, a day or two > after everything is settled, which depended on Leo 6.7.8. > > but dont hesitate to delay it if anything feels that need more time > Thanks for your comments. I'm going to

Leo 6.7.8 is coming this Friday, March 15

Félix has just released LeoJS 0.2.12 beta, so I assume it will be several more weeks until LeoJS 1.0 goes out the door. That being so, I would like to release Leo 6.7.8 immediately. Besides the usual improvements, Leo 6.7.8 changes Leo's distribution machinery and deprecates Qt5. Both

FYI: Installing pyqt6 works on all platforms

Recent experiments show that installing pyqt6 is straightforward on all platforms. As a result, Leo's *installers *for 6.7.8 will only install qt6. Installing only qt6 is an *experimental policy.* If all goes well, the *next* release (6.7.9) will remove support for qt5. For *this* release

Re: ✨LeoJS beta 0.2.12 Released!

On Sat, Mar 9, 2024 at 8:41 PM Félix wrote: > Introducing LeoJS Beta 0.2.12 > Félix here, ecstatic to unveil the latest milestone in our coding > odyssey—LeoJS > Beta 0.2.12 > ! > And I'm ecstatic with your work and images :-)

Re: FYI: Simplified installation instructions

On Sun, Mar 3, 2024 at 10:45 PM HaveF HaveF wrote: > Nowadays, I always use pipx install or update leo(instead of conda env) > > install like: > pipx install leo > > update from the source: > git clone ... > cd ... > git pull > pipx inject leo /Users/mac/Desktop/proj/leo-editor >

Re: FYI: Simplified installation instructions

On Sun, Mar 3, 2024 at 1:37 PM Geoff Evans wrote: > Obvious question: if I use both Anaconda *and* MacOS (Ventura), which > part of the Installation instructions supersedes the other? Is Homebrew > necessary? > I don't know. The new installation instructions have not changed any of the MacOS

FYI: Simplified installation instructions

Leo's "devel" and "6.7.8" branches now contain simplified installation instructions. These instructions are now live on Leo's website. A few changes turned into general housecleaning: - Greatly simplified the Getting Started and

Re: .csv Importer Is Specialized For MindManager Export Files

On Sat, Mar 2, 2024 at 8:08 AM Thomas Passin wrote: > It seems to me that Leo ought to have separate import commands for > MindManager and ordinary tabular .csv files, which will be easy enough to > arrange. If the MindManager import command were simply removed, it might > bite someone who

Re: .csv Importer Is Specialized For MindManager Export Files

On Fri, Mar 1, 2024 at 8:33 PM Thomas Passin wrote: > The process for importing any file delegates .csv files to files exported > the MindJet's MindManager program. Using it to import ordinary tabular .csv > data produces unusable results on the samples I tried today. > Thanks for this report.

Re: Discuss: Leo 6.7.8 will install only PyQt6

On Fri, Mar 1, 2024 at 6:32 AM Thomas Passin wrote: > > On Friday, March 1, 2024 at 5:33:34 AM UTC-5 Edward K. Ream wrote: > > I meant to ask whether potential errors concerning the missing xcb-cursor0 > or libxcb-cursor0 libraries are a show stopper. > > Imo, most linux u

Re: Discuss: Leo 6.7.8 will install only PyQt6

On Thu, Feb 29, 2024 at 10:38 AM Thomas Passin wrote: >> Do you think requirements.txt can specify only PyQt6? > It's looking better than say a year ago. I currently don't have any more distros to try. My question wasn't clear. I meant to ask whether potential errors concerning the missing

Re: Discuss: Leo 6.7.8 will install only PyQt6

On Thu, Feb 29, 2024 at 9:46 AM Thomas Passin wrote: > So far all the distros I have checked do now support pyqt6: > > Ubuntu/XUbuntu > Debian > OpenSuSE > Fedora > Manjaro > Mint > > These are all the distros I've got VMs for. > Thanks for the report. Do you think requirements.txt can specify

Re: Heads Up - Malicious Git Forks

On Thu, Feb 29, 2024 at 9:42 AM Thomas Passin wrote: > See This Slashdot story - GitHub Besieged By Millions of Malicious > Repositories In Ongoing Attack >

Re: Discuss: Leo 6.7.8 will install only PyQt6

On Thu, Feb 29, 2024 at 9:25 AM Edward K. Ream wrote: > It looks like requirements.txt must specify Qt5 on Linux. I've just changed the requirements as follows: # Use PyQt5 by default. "PyQt5>= 5.15; os_name != 'nt'", "PyQtWebEngine; ; os_name != 'nt'",

Re: Discuss: Leo 6.7.8 will install only PyQt6

On Thu, Feb 29, 2024 at 8:37 AM Thomas Passin wrote: > I think that whether we can require pyqt6 should depend on whether it can > be installed on a particular flavor of Linux. That didn't used to be the > case, but it may be now. It is available on Ubuntu/XUbuntu, and probably > on most

Re: Discuss: Leo 6.7.8 will install only PyQt6

On Thu, Feb 29, 2024 at 7:20 AM Edward K. Ream wrote: Recent revs to the 6.7.8 and "devel" branches install only PyQt6 when > installing either from PyPi or GitHub. > Here is how I test the new dependencies without using PyPi. *pip-uninstall-all.cmd* @echo off rem uninstal

Re: Discuss: Leo 6.7.8 will install only PyQt6

On Thu, Feb 29, 2024 at 7:20 AM Edward K. Ream wrote: > Recent revs to the 6.7.8 and "devel" branches install only PyQt6 when > installing either from PyPi or GitHub. That is, both of the following will > install PyQt6: > > > pip install leo # From PyPi > &g

Discuss: Leo 6.7.8 will install only PyQt6

Recent revs to the 6.7.8 and "devel" branches install only PyQt6 when installing either from PyPi or GitHub. That is, both of the following will install PyQt6: pip install leo # From PyPi pip install -r requirements.txt # after git clone leo *Don't panic* *This* release, Leo 6.7.8,

Simplified installation with `pip install -r requirements.txt`

PR #3775 supports simplified installation using GitHub. The new (recommended) way to install Leo is to do the following *once*: - git clone https://github.com/leo-editor/leo-editor.git - pip install -r requirements.txt After that,

Leo 6.7.8 status report

Leo 6.7.8 is formally due on May 31. However, I'll release it about the time Félix's releases LeoJS 1.0. Félix estimates that will happen in a few weeks, but there is no rush :-) Leo 6.7.8 is almost code complete. I expect to complete work in about a week. Recent revs have completed the

Re: TIL in Leo: decluttering headlines

On Tue, Feb 20, 2024 at 4:42 PM jkn wrote: > update - it does seem to work ... but I have seen some strangenesses. > > - an exception failure, ~ bad number pof parameters > - a case where no more headlines appear below the 'decluttered' one. > > I will continue to investigate... > Thanks for

<    1   2   3   4   5   6   7   8   9   10   >