nothing works 👀

[b-yp]

nothing works 👀

[lef-est]

ahhhhh yes it's working now!! thanks!!
yes i installed it from the marketplace, unlucky timing 😅 glad that i included the plugins panel in my video

[b-yp]

I'm not sure what the reason is, but I still have a Windows computer at home. I can use it for debugging when I go back at night. Thank you for the information you provided.

[b-yp]

I noticed that you are using version v1.2.0 of the Logseq-d2 plugin, while I have only updated to version v1.1.0. I suggest you completely delete the Logseq-d2 plugin and then reinstall it.

For code blocks, only markdown's ``` is currently supported. I will try to support org-mode code blocks in the next version.

[b-yp]

I tested on my computer and found that the /d2 command does exist. I'm not sure what the issue is on your end. If you want to use {{ renderer :d2_xxx }} to achieve the function, you need to write the code for d2 in the sub-block.
For example:

- {{ renderder :d2_xxx }}
  - ```d2
    A -> B
    ```

[lef-est]

thanks for the quick reply. i did write that in the sub-block (and i tried both org-mode code block and markdown's triple ```). the parent block contains {{renderer :d2_lang_gkkbq, 100, 200}} but it looks empty in viewing mode.

further info: logseq 0.8.18, windows 10

[b-yp]

thanks for the quick reply. i did write that in the sub-block (and i tried both org-mode code block and markdown's triple ```). the parent block contains {{renderer :d2_lang_gkkbq, 100, 200}} but it looks empty in viewing mode.

further info: logseq 0.8.18, windows 10

Hello, I have tested it on a Windows computer and it works normally. The slash command /d2 also takes effect. If it's convenient, would you please record a GIF animation so that I can find the problem faster.

[lef-est]

GIF.2023-03-29.10-40-43.mp4

hope it helps!

[b-yp]

As for why you are version v1.2.0, I think it may be because I updated a test version when I was testing another implementation method before. Later, there were some problems with that method, so I restored it to the current implementation method. If you have any problems in use, please feel free to raise an issue again.