Opinion: development focus should shift towards improving LogSeq's partially unstable core

Hi Alex,
Thanks for responding. I really appreciate it :slight_smile:
Here’s a link to my actual bug report:

As you can see even assests don’t work (with the exception of PDF’s and Jpegs).
The assets folder (situated inside the Logseq folder as usual) is on a separate data partition, not on the root partition. (But the home folder is on the root partition.)
I have tried sym-links as well as uploading files to the assets folders (which is not my preference).

As you can see, the best I can get, is the document file locked message…

As you can also see - in Obsidian it just works, right out of the box - no need for any messing about. I don’t know why that could not also be the case for Logseq.
If that worked as a temporary work around until file linking was fixed, I would have been happy to use it; sadly it does not work.
However in the long run I don’t really want to have to add sym-links for every file I want to link to - it will become cumbersome over time.
My understanding is that it is intended to just work by design, and that the fact it doesn’t is just a bug. If I have misunderstood something there, then please correct me.

Meanwhile I am having to look into ways to make Obsidian behave more like Logseq, with a myriad of plugins etcetera. I am also experimenting with using both on the same files; but with mixed results.
Anyway - I do appreciate the response. And if there’s anything you else can think of that I can try I would be happy. I really would love it if Logseq comes through in the end.

1 Like