Re: Leo doesn't start because of some Qt-problems

2024-07-22 Thread p.os...@datec.at
Shouldn't I mark this thread as solved? How do I do that? And, OT, yet I could not figure how to answer a specific poster. There's only a "Reply All" button. On Tuesday, July 23, 2024 at 7:44:14 AM UTC+2 p.os...@datec.at wrote: > I knew I am right here: > > QT_Q

Re: Leo doesn't start because of some Qt-problems

2024-07-22 Thread p.os...@datec.at
nd /home//.local/lib/python3./site-packages > -name libqxcb.so -ls` (or similar). > > Sorry this is being one of those mystery pains. :( > > Jake > > On Mon, Jul 22, 2024 at 11:32 AM p.os...@datec.at > wrote: > >> Yes, /usr/lib/qt6/plugins/platforms/libqxcb.so exists. Settin

Re: Leo doesn't start because of some Qt-problems

2024-07-22 Thread p.os...@datec.at
suggested in the error message. That time I >> lucked out with an Internet search. >> >> Which distro is this, BTW? >> >> On Monday, July 22, 2024 at 10:48:32 AM UTC-4 p.os...@datec.at wrote: >> >>> Latest qt6-tools are Installed already. Installed qtuti

Re: Leo doesn't start because of some Qt-problems

2024-07-22 Thread p.os...@datec.at
it then Qt worked. I don't remember any details, > though. I also recall that in one case the library name was different from > the one or two that had been suggested in the error message. That time I > lucked out with an Internet search. > > Which distro is thi

Re: Leo doesn't start because of some Qt-problems

2024-07-22 Thread p.os...@datec.at
mative. BTW, you don't need > PyQt5. Leo doesn't use it any more. Please post the Qt error message here > if you can't resolve the problem. > On Monday, July 22, 2024 at 7:20:05 AM UTC-4 p.os...@datec.at wrote: > >> Installed xcb-util-cursor, libxinerama. R

Re: Leo doesn't start because of some Qt-problems

2024-07-22 Thread p.os...@datec.at
red library goes by this name: *libqxcb.so* instead. >> Sometimes the error message will suggest two possible names instead of just >> the one. Try them both if the first doesn't do the job. >> On Monday, July 22, 2024 at 5:40:34 AM UTC-4 p.os...@datec.at wrote: >

Leo doesn't start because of some Qt-problems

2024-07-22 Thread p.os...@datec.at
Issuing export QT_DEBUG_PLUGINS=1 && leo yields setting leoID from os.getenv('USER'): 'X' qt.core.plugin.factoryloader: checking directory path "/usr/bin/platforms" ... qt.qpa.plugin: Could not find the Qt platform plugin "xcb" in "" This application failed to start because no Qt platform p

Re: @auto-md: multiple vnodes with gnx

2023-09-01 Thread p.os...@datec.at
Well I am a long-term user of rST and the respective Leo plugin. But this is about creating and maintaining MkDocs websites. I consider Leo being superior here (just as elsewhere also). On Tuesday, August 29, 2023 at 7:53:21 PM UTC+2 Edward K. Ream wrote: > On Tue, Aug 29, 2023 at 8:03 AM Thoma

Re: @auto-md: multiple vnodes with gnx

2023-09-01 Thread p.os...@datec.at
Looks good! I'll stick with it. Replaced if p.h and p != root: by if p.h and not p.h.startswith( "!") and p != root: though. Thanks a lot! On Monday, August 28, 2023 at 9:58:26 PM UTC+2 tbp1...@gmail.com wrote: > On Monday, August 28, 2023 at 4:56:12 AM UTC-

Re: @auto-md: multiple vnodes with gnx

2023-08-28 Thread p.os...@datec.at
ngle file. rst3 has some extra functionality that you probably > don't need. You would want it to honor << sections >> and @others, right? > Or maybe there already is such a command; I haven't found it in a quick > look, but one could exist somewhere anyway. >

Re: @auto-md: multiple vnodes with gnx

2023-08-27 Thread p.os...@datec.at
I do not import MD files, I create and write them in Leo. The bad about @clean files is, that they do not convert my node tree into a valid MD files containing headings with the right level. Or do they? On Sunday, August 27, 2023 at 9:05:16 PM UTC+2 tbp1...@gmail.com wrote: > One possibility is

Re: @auto-md: multiple vnodes with gnx

2023-08-27 Thread p.os...@datec.at
stored w/i my Leo file. Everything would be fine and work as expected ;-) On Sunday, August 27, 2023 at 3:59:28 PM UTC+2 p.os...@datec.at wrote: > The behaviour I experience seems documented: > https://leoeditor.com/FAQ.html#why-doesn-t-leo-support-cross-outline-clones > - and that ma

Re: @auto-md: multiple vnodes with gnx

2023-08-27 Thread p.os...@datec.at
The behaviour I experience seems documented: https://leoeditor.com/FAQ.html#why-doesn-t-leo-support-cross-outline-clones - and that makes sense, if MD files are read by Leo. But why are they read? They only need to be written as I want to create MD files using Leo and only Leo. On Friday, Aug

Re: @auto-md: multiple vnodes with gnx

2023-08-23 Thread p.os...@datec.at
[M] @ bool createatpersistencenodesautomatically = True Forgot to mention I am still running ver. 6.7.1 and on Linux. Guess I'll keep an eye on this by running Leo in an IDE. On Wednesday, August 23, 2023 at 5:03:55 PM UTC+2 Edward K. Ream wrote: > On Wednesday, August 23, 2023 at 7:18:26 AM U

@auto-md: multiple vnodes with gnx

2023-08-23 Thread p.os...@datec.at
It becomes more and more annoying, that when I want to clone a node below a @auto-md file into another @auto-md I get this error: multiple vnodes with gnx: 'xxx.20230509132609.1' id(v): 139738387243504 gnx: xxx.20230509132609.1 Variable id(v): 139738508086256 gnx: xxx.20230509132609.1 Variable ch

Re: @auto-ms does not get along with Leo's clones

2023-06-07 Thread p.os...@datec.at
at 3:05:51 AM UTC-4 p.os...@datec.at wrote: > > Again it happended. But now it happoend with vanilla nodes, as I replaced > all clones by copies of the respective nodes. A section is cut off at > > ```bash > > which becomes a node title. This node's body contains then all

Re: @auto-ms does not get along with Leo's clones

2023-06-02 Thread p.os...@datec.at
that does not read, which for me makes no sense anyway: The content is in my Leo tree and should just be written into an MD-file, that will be processed by mkdocs. Cheers Paul On Friday, May 26, 2023 at 12:58:51 PM UTC+2 p.os...@datec.at wrote: > Thanks a lot! > > As for the loss of &q

Re: @auto-ms does not get along with Leo's clones

2023-05-26 Thread p.os...@datec.at
a tree that suffers from the problem? Or a minimal version that does? On Wednesday, May 24, 2023 at 5:12:30 AM UTC-4 p.os...@datec.at wrote: Sorry, it's Leo 6.6.4 on Arch Linux. On Tuesday, May 23, 2023 at 8:17:44 PM UTC+2 tbp1...@gmail.com wrote: I tried out what you wrote and didn

Re: @auto-ms does not get along with Leo's clones

2023-05-24 Thread p.os...@datec.at
k for you (not that I've tried them >> with clones, which I'll try out soon) instead of @auto-md. I don't think >> that @auto-md really gets you anything that they don't, although you will >> need to put *@language md* at the start of the body of the

Re: @auto-ms does not get along with Leo's clones

2023-05-24 Thread p.os...@datec.at
hat I've tried them > with clones, which I'll try out soon) instead of @auto-md. I don't think > that @auto-md really gets you anything that they don't, although you will > need to put *@language md* at the start of the body of the top node. > > On Tuesday,

@auto-ms does not get along with Leo's clones

2023-05-23 Thread p.os...@datec.at
An example: @auto-md file1.md clone-node_1 clone-node_2 @auto-md file2.md clone-node_1 clone-node_2 Changes in a clone causes (don't know exactly when, probably when reading the LEO file) that the tree hierarchy is partially destroyed. The content remains, but ends up in a node

Re: How can I keep md-content in Leo instead of importing it?

2023-04-02 Thread p.os...@datec.at
Sorry, folks, found a thread back in 2020, where the appropriate setting is described: @bool create-at-persistence-nodes-automatically = True Seems to work, but: Any caveats to watch out for? Cheers Paul On Sunday, April 2, 2023 at 4:31:36 PM UTC+2 p.os...@datec.at wrote: > I recently star

How can I keep md-content in Leo instead of importing it?

2023-04-02 Thread p.os...@datec.at
I recently started to document some of my Python projects using MkDocs and mkdocstrings. I write all markdown text using Leo, of course.That makes it possible to use clones for stuff being important to more than one MkDocs document. Alas, all clones are just copied on import (of course) and the