I really have to say that this is a really good tool once you switch from the #markdown default setting to the much better #orgmode syntax. 😉
I'll migrate the #Joplin data from my previous testrun over to logseq and go with that for the moment.
Don't worry, I'll probably never leave my Org setup. It's for another person's management and knowledge base where #Emacs was no option, unfortunately.
@publicvoit Yes, please do keep reporting on what you learn. I've started and stopped with Logseq. I lost data early on and it soured me on it for a long time. For the past few days I've been testing it as an input to my daybook (in Org format of course). I love outliners. There's an emacs package for dealing with Logseq files and links but it's pretty basic.
@phpmacher I you really want to do WYSIWYG, you should not participate in discussions about LML differences :wink: . That's a different class of tools.
@publicvoit Excellent post on this, Karl. This is pretty much what I had learned when I was using it early in 2023 but I used it with Markdown no Orgmode because I had read about the incompatibility with emacs orgmode. I especially found your test with the 215k lines interesting and answers a lot of my questions. I really had hoped it could be a frontend to my org files from emacs but I just don't think that's doable.
@publicvoit I'm going to do a fresh test on it. I'm going to create a new graph and try that way. My current instance is broken and I'm not sure why. And this time I want to default to Org syntax.
I stopped using it around march 2023 because 1) there was an AI branch they were working on and I don't want AI in my notes; and 2) they used spec design for a new logo which the artist/designer side of me strongly disagrees with.
Add comment