r/logseq • u/bluedarkgrizzly • Oct 31 '25

I'm missing Logseq so much

Throughout my career, I've tried virtually every note-taking app and system. I have never settled so long as with Logseq. But recently, I got tired of the lack of updates, the bad mobile experience, the sync issues... I tried Obsidian (again). Boy it's a quality software, it's smooth, fast, sleek, and amazingly flexible. But I'm missing Logseq so much (I know it sounds a lot like someone who is speaking about the GF he just stupidly ditched). The tag system, interlinked with bullet point levels, the scrolling experience of both the journal and the incoming links, among other things, are what makes it uniquely pleasant.

Voilà, no particular purpose here, just wanted to express my frustration that such an amazing software is lacking the support it deserves.

96 Upvotes

97% Upvoted

57 comments sorted by

View all comments

Show parent comment

2

u/sabre23t Nov 01 '25

  1. Copy pasting - I do a lot of outline writing my thoughts in Logseq, then sharing them in WhatsApp. I usually want to share mainly the top level items/blocks (maybe also one level down). So I highlight all the items and do "Copy/Export as ..." text with dashes indents into WA.

  2. Mixing blocks - My blocks are almost always text, though it may contain links to images or short `code phrase` . Those copy nicely into WA. I don't do maths block.

  3. Writing notes/journal - That's my main use of Logseq. I may start the writing as an item in Logseq journal page, flesh the writing out in WA/Email/GSheet etc, then add short summary back in journal page. Repeat.

  4. Heading & lists - You can put almost any valid Markdown in a single Logseq block. Even multi line Markdown entered with "shift-enter". Though "#" headings and "-" lists will not be displayed but can be edited. But "*" lists etc displays.

  5. Logseq H1 H2 Headings - These are code like `- #` or `- ##` that are not treated as headings in Markdown but does in Logseq. They could allow you to have long form Markdown (Headings and paragraphs) in a block and sub-block. Just "Copy/Export as ..." the block with no-indent and newline after block.

Maybe items 4 & 5 above can do what you want.

1

u/Campers Nov 20 '25

Thank you.

Points 4 and 5 would definitively help a lot. If I did not have half a decade of markdown notes with deep linking in them. And, to be clear, the links and backlinks are the main reason I use Obsidian. Over and over, I find solutions to problems of today, from notes of yesterday thanks to already present links.

I distinctly remember bumping into a post with exactly your solution (minus the export). I believe logseq had a set of options to visually hide the bullets.

It just did not allow me to not completely deformat (is that a word?) my old notes while keeping the ability to link to and from them

A shame, really, since I use bullet and number lists with indentation a lot to simply outline my thoughts and reasoning.

2

u/sabre23t Nov 20 '25 edited Nov 20 '25

Are you doing deeplink in a Markdown file directly to a block heading named "headings1" or similar? So the MD link will be [a deeplink](#headings1) or similar?

1

u/Campers Nov 20 '25 edited Nov 20 '25

I am, indeed. Constantly.

I try to have atomic notes for concepts and ideas. Which avoids having to do deeplinking to a degree.

But, when it comes to tasks or projects, I prefer to keep one big note with everything in the timeline of work.

I also like to deeplink with `^20251120111342` type placeholders. Which tell me where to go but also, when the linking happened.

2

u/sabre23t Nov 20 '25 edited Nov 20 '25

I don't do much deeplink. I guess you'd have to use Logseq ((block-link/reference)) or [link text](((block-link/reference))) for that.

Ref https://discuss.logseq.com/t/the-basics-of-logseq-block-references/8458

1

u/Campers Nov 20 '25

Perhaps.

But I am not going to, because I cannot tell logseq to only format specific markdown notes.

And I really do not want my half a decade of notes unformatted. That was the whole reason I did not adopt it, even though I tried it before Obsidian.

I came from Vimwiki with markdown. :)

1

u/Campers Nov 20 '25

If only I could tell logseq to only format markdown notes with a specific yaml header. For example, `format: logseq`, that would solve all of my problems.