Seeking best practices for note taking and journaling that leverages DT3 (and mimic transclusion similar to roamresearch)

No it’s about single quote code and code block

code
here

where in DT3 view mode code blocks

code
here

has gaps with css backgrounds so it loos like code. It has nothing to do with markdown standards, this is plain CSS where a background should be continuous.

Note that in Discourse here it looks as it should.

BTW maybe the most common Markdown today is the github specific Markdown. Typora even adds more formats that are useful for layout, notes and so on. But that’s another story.

A screen capture of what you’re referring to would be helpful.


MultiMarkdown is viewed as the natural successor to Gruber’s original work. And supporting multiple flavors of Markdown is not in our plans.

I filed a bug report already and this has nothing to do with multiple markup formats. It’s a css rendering bug on your side. But here’s another screenshot:

Screen Shot 2020-04-25 at 11.38.46 PM

I assume you could figure out the css rendering issue with the code block. If not let me know and I will point it out.

PS: Typora seems to be nice and support various Markdown formats. It’s nice and the beauty with Markdown is that if the format is not understood, just the plain text tag format is rendered as plain text without causing problems: for example foot notes and table of contents tags.

Anyway, as mentioned many times, this has nothing to do with Markup, the example above is plain Markup, not even MultiMarkup.

1 Like

Are you sure it is not related to the css you are using?

Over here code blocks render just fine.

This is what I’m seeing with code fenced content…

Well, that was a screenshot from DT3.0.4. I think it’s has to do with how the css rendering is done per case. That’s why I sent a detailed example + css file in the previous bug report that I assume you have. Any css rules should render for blocks, if not it’s a bug. Note this works fine in Visual Studio Code view and Typora and other MarkDown editors I have here.

Thanks for sharing the document! I will read it shortly.

You may want to take a look at this script. It’s not Roam Research, but the script will merge all notes under group/tag in one refreshable file and offer direct[almost] editing of the source notes. Just an idea.

2 Likes

@ngan I went through your script. Sounds like an interesting idea, and perhaps is a seed to build some roam like capability in DevonThink.

on that note, here is an outline of features that I think will bring in some of the most powerful roam like features in DT. I would build if I knew how to. my programming skills are rather basic.

  1. use a markdown editor, ideally one that allows folding of text at the node level and one that can indent all “child” bullets if parent bullet is indented. from what I have seen VS Code is an interesting option - allows folding by bullet and with a few extensions can be a decent markdown editor with side-by-side preview.
  2. in a somewhat automated way, create a new journal markdown document for every day that can be the scratch pad for that day. this should be easy given how customizable VS Code is.
  3. be able to autocomplete tags that exist within Devonthink in the editor of choice. there must be a way to get a list of tags in Devonthink, and then perhaps use that list to offer auto-complete choices in the editor of choice.
  4. for every tag that is used in the daily journal document that line and child nodes (indented bullets), a separate “tag-document” titled with that tag is generated (or appended to). The appended text in that document is the tagged line and child nodes (and a link back to that document - to the line number where the tag exists). And when this appending takes place, in addition to the original tag in the daily journal, side by side a link is placed to the Devonthink markdown document with the title and link to the “tag-document”. The daily document can be processed every (say 5 min).

thoughts, in case you read through the above. and if you know how #2 and #3 above can be done, do suggest and I will try and take a crack at it, and then will try to see if I can do #4.

thanks.

I’d go with Markdown: Text decoration is very easy to do in Markdown and it is much more future-proof then RichText.