I am getting frustrated with Logseq. I am trying to get a simple note-taking use-case going with it, but I can’t help but keep fighting the tool rather than using it.
I see Logseq has a built-in PDF reader. Nice. I also see that it supports highlighting the text from the PDF file, and doing references to it (block reference, etc.). Great.
Sounds like it would work pretty well, right? Not quite, in my experience.
First of all, I create a new page for keeping notes from a book. Let’s say the book is “How to Take Smart Notes” by Sonke Ahrens.
So, I create a new page,
[[how to take smart notes]]. I use all lower case with my page names, and I just type the book name into the page filename. I will use page properties for adding the
Now, inside the page
[[how to take smart notes]], I do
/Upload an asset and upload the book’s PDF file. This creates a link inside the
[[how to take smart notes]] page.
Then, I click on that file link, and I open the pdf inside Logseq, on the left hand side, and I pick the highlight mode to highlight some portion of text.
What happens in the background is, Logseq creates an additional file, named
hls__sonke_ahrens_how_to_take_smart_notes_1698059081568_0.md in my local filesystem.
So, I have the following files related to my small and simple endeavor of taking book notes with logseq:
how to take smart notes.md hls__sonke_ahrens_how_to_take_smart_notes_1698059081568_0.md
the first one is created by me, and the second one is created by Logseq itself.
The second one is used to store my highlighted portions of text from the book. The problem is, I created the the first page (that is,
how to take smart notes.md) exactly for that purpose already! Why the extraneous file?
This is not the only inconsistent, and thus confusing UX with the internal PDF reader implementation of Logseq.
Now, the Logseq created
hls__sonke_ahrens_how_to_take_smart_notes_1698059081568_0.md file, yet, inside Logseq UI, this file’s name is shown as
sonke ahrens how to take smart notes. Without the
hls__ prepend, and without the underscores present in the original filename.
This is quite confusing for me as I pay attention to my filesystem and what files Logseq creates in it. I seek consistency with my filenames, and how they are presented to me inside the Logseq UI.
This last part is especially annoying to me, as, I would like to store the files in my filesystem without whitespaces, that is, multiple-word files employing underscores in between words, yet Logseq doesn’t offer a user-facing setting for this in its Options menu—YET, Logseq is capable of creating a Logseq page with whitespaces in its UI which are replaced with underscores for the files it writes/creates in the local linux filesystem. Talk about the frustration!
Here’s another post where I try to illustrate what I mean: Cleaner file names - #7 by MoneroDude
Anyone else sharing my frustrations? What do you do to deal with those inconsistent UX stuff??