Logseq Quoted List doesn't render accurately

[FlorianF]

Hello, I have noticed this before but I don’t think I or somebody else reported it, at least a search in the forums didn’t bring up anything.

I have the following situation:

Text
* List
    * List Item 1
    * List Item 2

Logseq seems to render at the same alignment the list title and the list items:

while VSCode for example renders it correctly:

Also if the list items have sub items it does the same, rendering ALL at the same alignment…

I am on 0.10.8 (haven’t moved to the beta yet).
I also opened https://github.com/logseq/logseq/issues/11575 .

[Ramses]

This is a known issue and cannot be fixed at this moment. The reason is that Logseq doesn’t support nested lists within a single block. * and - have the same behavior in Markdown, but this error only shows when using -:

- doesn’t work at all probably because Logseq uses that in the Markdown files it creates. * does render, but as Logseq doesn’t support nested lists in a single block, it shows them all at the same indentation level.

Likely this isn’t the answer you were looking for, but at least you know why it is. In Logseq DB (in alpha) — which doesn’t use Markdown files for storage — there’s an inkling of quotes supporting nested lists though it doesn’t render perfectly yet:

[FlorianF]

Thanks @Ramses for your answer. That’s a bummer for me as I have quite large such lists inside quoted text…

[Ramses]

As an alternative, you could use a code block and just call the language quote. That will give you the ability to create nested lists:

This is what the block looks like in editing:

You can simply type this and click out of the block, then the code editor appears and you can write directly in the code editor (which also keeps track of the indentation level for you):

The only downside is that you can’t put > in front of the block as it’ll result in the same error I shared before. But calling the code block “quote” might be enough.

[FlorianF]

That’s an interesting approach but inside the code block all formatting is gone, so I’ll stick with the “quotless” quote as indented lists in bullet blocks work fine.

Edit: I can “hack” it somehow so it still renders nice in markdown-compliant renderers as well as in Logseq by using the unicode “2004” via this method and then I insert 4 spaces after the unicode blank character. This way Logseq doesn’t remove the blank spaces at the begining of the line and renders somewhat okish:

But also kind of breaks the markdown and looks the same in VSCode: