Bullet/numbered list inside callout

Help
1

Pretty straightforward: I want to put a list inside of a callout

I use a foldable callout like this—

[!info]- meta
tags::
related-notes::
apropos::

—to keep my notes organized in a pseudo-Zettelkasten style. Right now, my “related notes” section develops horizontally:

related-notes:: [[Note A]], [[Note B]], [[Note C]]

I would love to know how to turn that into—

related-notes::

  • [[Note A]]
  • [[Note B]]
  • [[Note C]]

—without breaking the callout. I also want the items in that list to be retrievable by Dataview.

Things I have tried

Been around the world and back again looking for solutions, but no luck. I’ve messed around with the callout formatting, but even after almost a year of Obsidian use I’m afraid I don’t know enough about the behind-the-scenes action of this program to know what I am doing wrong, or if my ask is possible.

Edit: pretend the carrots in the callout format are still there! They got snipped.

2

Inline values have to be on the same line as their key. They stop at line breaks.

Does the following work more as you need?

> [!info]- meta
> #addresses, #authors, #philosophy   
> related-notes::  [[Note A]]  
> related-notes::  [[Note B]]  
> related-notes::  [[Note C]]   
> apropos::  Something

  
```dataview
TABLE WITHOUT ID
file.etags, related-notes,
apropos
WHERE file.path = this.file.path
```

This post about tags might be of interest.

3

Ah, I didn’t know that about inline tags!
Visually your format is a perfect workaround. Thanks so much. I use a template for this callout for ease (my goal with Obsidian is to have as few keystrokes and clicks as possible during workflow), and because I can’t predict how many links I’ll add to any one note I might have to keep my current setup, at least for now.

Oof, that does throw a wrench in things! To clarify, that dataview parsing issue only applies to tags, yes? ie double colons for links and categories and the like are fine?

1 Like
4

One thing you might consider doing is creating a template with a line break followed by > related-notes:: . Then, if you’re using templater, you could optionally bind it to a shortcut and whenever you’re adding related notes, just press your shortcut for another line to be added.

It’s not perfect, but it should help keep keystrokes to a minimum

1 Like
5

That’s a great idea. Thanks!

6

It applies to when you start combining definitions of fields both within frontmatter and as inline fields, and especially if you start re-using predefined stuff like tag, tags and/or alias/aliases.

Try the following in a note of your own, to see an illustration of the problem at hand:

---
aField: frontmatterValue
aField: anotherFrontmatterValue
---
aField:: inlineValue
aField:: anotherInlineValue

And just for the fun of it [aField:: yetAnotherInlineValue].

What's the value of `aField`: `= this.aField`

Good for you if you guessed the correct answer… :slight_smile:

1 Like
7

I defer to what holroy said above: he knows far more than I do.

8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.