Multiple issues here. The Markdown is I guess a question of priorities. If knowledge workers and programers are to be a big focus going forward, Markdown is an obvious place to invest—but it’s not my software! I can just make the request as I see so many issues referenced on these forums that would be solved. Would love to see it in the future.
For the other two—I’m trying to figure out how to fork this conversation in Discourse—any tips?
For prism.js I’ve done as you’ve suggested (originally following the instructions from the primary thread on the topic) but I can’t tell why it’s not working. I’ve tried every style of reference—put the files inside a group named assets and then link at “assets/prism.css” (and .js); using the x-link URLs; hard-coding a link on my file system… None seem to work. It’s hard to debug if DT is seeing the files.
For WikiLinking, for example if I have two pre-existing documents:
“DEVONThink is awesome, everyone should use it”
“DEVONThink’s limitations for networked knowledge and how to get around it”
… and then in a new note try to type [[DEVONThink Notes]] to create a Wiki link to a new document, it’s damn near impossible to overcome the fervent efforts of the autofill system to fill with the longer item names.