Follow

I'm seeing 2 different multi-column Obsidian plugins in the plugins list. They both look interesting. I might fiddle with them later today to get a feel which one of them is the more logical/easiest to use. Would be nice to have multiple columns possible in markdown. I wouldn't always need it but it's nice to have an option there!

@trinsec
Is it a table or how does it work with two columns?

@rastinza No idea, I've not checked the details yet. Maybe nested divs. Because you can nest the columns into columns as well.

@rastinza Okay, I’ve taken a peek at it now.

The two plugins in question are: Obsidian Columns (OC) and Multi-Column Markdown (MCM).

They have both pros and cons.

OC uses code blocks, and you can nest them to have columns inside columns. I’m not too fond of this approach much because if you have a genuine text or codeblock inside a codeblock, the normal text formatting or syntax highlighting is gone in editing. It’s just a bit annoying to work with in editor mode. But hey, nested columns! The output is in divs.

MCM uses === keyword type coding, so not codeblocks. It goes like === start-multi-column: name and then right below it a small codeblock for some config settings, and then stuff like === end-column === and ending with === end-multi-column. Rendering was a slight bit buggy but ultimately came out right. I likey because formatting of your content stays intact, but no column nesting possible inside them. And yes, this ended up as a div as well.

Sign in to participate in the conversation
Qoto Mastodon

QOTO: Question Others to Teach Ourselves
An inclusive, Academic Freedom, instance
All cultures welcome.
Hate speech and harassment strictly forbidden.