I testing out Wiki Links and MarkDown / Why is this happening

In DevonThink if I open a new markdown note and type

Link 1
Link 2
Link 3
Link 4

The output in the markdown preview is:

Link 1 Link 2 Link 3 Link 4

All on a single line.

Is this expected behavior? Am I missing a setting somewhere?

Well, if “the output in MD” is what you say, what is the input? How do you get from whatever that is to Markdown?

Or are the first four lines what you actually type into your MD document and what you then see in the preview is everything in one line?

Yes. At least with the little context you provide. MD is converted to HTML in the preview, and HTML doesn’t give a damn about line feeds. If you want to see paragraphs (i.e. each “Line x” on its own line) in HTML, use an empty line between them.

Line 1

Line 2

Line 3

Yes, that is the correct behavior per Markdown standards.

Three things…

3 Likes

Added context. Thanks for the response.

Thanks. ‘Force Line Breaks’ gives me what I was expecting. Marked 2, displays it fine either way.

Marked 2, displays it fine either way.

Likely because it’s already forcing linebreaks. That’s not standard Markdown syntax.

You should always be circumspect when comparing the features of one application to another, especially when there seems to be shared features. Many apps will implement their own modifications that work in those apps but should not be treated as any kind of standard. We try to stick to standards as much as is possible, hence we use MultiMarkdown instead of trying to invent our own Markdown renderer.

3 Likes

Got it. That’s one of the reasons I am trying to standardize and keep most of my stuff in one place. I just moved a few hundred markdown files from Obsidian into my DT notes database and had to only fix a few things - mostly the size parameter on the image links. Moving notes from Bear is a very different experience.

While I am here can I ask one more question. Under Settings->Files-Markdown there is a field to specify a folder where images should be placed. That works perfectly.

I wonder if there is a setting somewhere that directs DT to create new files from a clicked wiki-link in a specific folder too?

I wonder if there is a setting somewhere that directs DT to create new files from a clicked wiki-link in a specific folder too?

Nope. New WikiLinked docs appear in the same group as the originating document. In fact, I’ve never heard that request from anyone before.

Thanks.

It is just the way my Obsidian is setup. Part of the Zettelkasten thinking. I should grab a copy of Kourosh Dini’s book on using DT to take smart notes and see how things are setup.

What’s your Zettelkasten naming convention?

I use Unique Note, an Obsidian plug in. Which essentially just uses the date down to the minute. I created a template in DevonThink that creates a note named down to the second.

But I am not a good Zettlekasten citizen. I take notes. But I struggle with how atomic some of the Smart Note ideas are. I do like the notes all in one place. My Obsidian is split into three folders. Journal (daily Note), Zettle (random notes about all sorts of things, and Files (mostly images that are linked to the daily note or zettle notes). And it is those three folders that I copied into DT in the last day or so.

Zettelkasten doesn’t make practical sense to many people (myself included) :blush:

4 Likes

Just to note there is a rendering setting in Marked’s prefs to disable that.

Terpstra does not use his own Markdown processor. He uses either MultiMarkdown or Discount if you select GitHub Flavored Markdown. MD previewers (like Marked) might give the option to render that as a hard line break instead ( i.e. a <br /> tag). It is an option that can be turned off.

@GJT333 if you want a line feed in a Markdown document the standard is adding two spaces at the end of the lines. macOS will automatically add in a period when doing this but that can be turned off in System Settings

I am aware of this. I didn’t say Brett is rolling his own.

Didn’t say you did :wink: I’m just pointing out what he’s using as a very satisfied Marked user.

But you did give some warnings along with:

We try to stick to standards as much as is possible, hence we use MultiMarkdown instead of trying to invent our own Markdown renderer.

Brett is doing the same with options the same as DT is doing.