Adding block id for Callout

[Moy]

For example, you can create a callout like this:

> [!NOTE] Title
> Contents
> Other Lines.
> ^test

We can then use [[#^test]] to jump to this block.

However, currently, it is somewhat challenging to retrieve the block ID.

For instance, if you are not in edit mode for the callout, the block ID data may be lost (or perhaps I missed it?).

As a result, it becomes difficult to write scripts or plugins to quickly copy the block ID for the callout or adding ID for a specific Callout.

Could you please assist with this? I believe that if we could bind such Block ID data to the callout, it would greatly enhance its practical usability, especially for synchronizing notes with various reading plugins.

[PlayerMiller]

if you are not in edit mode for the callout

I’m not sure which technical scenario this sentence will ultimately be applied to. But a callout is a multiline block, right? Usually, when dealing with multiple lines, the position where we place the ref can be after the multiline block. In Chinese forum, someone has made a detailed explanation 一文让你理解什么是块，及具体如何记笔记有利于块链接. You can go and take a look. (I know you and I’m aware you can speak Chinese.)

> [!NOTE] Title
> Contents
> Other Lines.
^test

[Moy]

Thank you for your reply!

Yes, I think putting the block id behind the block is a feasible way.

However, I personally prefer to put the block id inside the block id.

And sometimes I would even put the id in the middle of a callout:

Like this one, this is a Callout (Annotation with comment) synced from Wucai.
So I was trying to figure out how to quickly copy block id from those callouts.

[Moy]

I’m developing a plugin to implement my request, it looks like this:

（Based on a new plugin Callout Copy Button)

When it’s more mature, I’ll share it : )

[PlayerMiller]

this is a Callout (Annotation with comment) synced from Wucai

If putting the block ID inside the block is Wucai’s format, the plugin that matches the format is really suitable. Developing a tool is primarily to meet one’s own needs.

Though, there could be difficulties in promotion, as it might still be more appropriate to place it at the end in Obsidian’s default state. Otherwise, it will be inconvenient without installing this plugin.

Anyway, thanks for your efforts.