@User this is making me realize i need to actually read through the commonmark spec. as for having dendron render in github, i'm thinking it might make sense at some point to implement rendering via browser extensions. this way you get the full richness of the markup without unnecessary compromises

> @User this is making me realize i need to actually read through the commonmark spec. It's pretty dry, but relatively painless for a reference spec? > as for having dendron render in github, i'm thinking it might make sense at some point to implement rendering via browser extensions. this way you get the full richness of the markup without unnecessary compromises That's really interesting– will reflect. (There will be a couple of edge-cases ... iOS+iPadOS, embedded renderers ... but perhaps insignificant?)

yeah, its very readable. like the interactive examples as well. fyi, the language server specs are actually also very readable in case you're curious https://microsoft.github.io/language-server-protocol/specification

as for edge cases on ios/ipad - i'm thinking that folks would browse/edit notes using a dedicated app (eg. gitjournal/iawriter) vs navigate to the mobile website 🤷‍♂️

@User @User @User @User this is still very rough but i've written out a short note on how org-mode can be currently enabled in dendron and how we might implement it in the future. feedback appreciated 🙏 https://dendron.so/notes/c3800271-dd56-46fb-8de7-e850f3c006b7.html

That's very interesting and I need to reflect on it. My initial reaction is that option 2 won't lead to much. Maybe we need to think what supporting orgmode should achieve. One thing would be to allow people like me having lots of org files to easily migrate them into dendron (I used pandoc for this purpose). Another would be to support specific orgmode features that go beyond the markup part. The issue with the latter is that orgmode has such an incredible large set of capabilities that even long-time users seem to use completely different parts of it. E.g. I find the clocking features very handy for time tracking but don't care about exporters and publishing.

I have to agree with Bassmann, option 2 probably won't lead to much. Option 1 would be super cool, but I sympathize with the challenge and don't expect anything. 😅

> fyi, the language server specs are actually also very readable in case you're curious > i'm thinking that folks would browse/edit notes using a dedicated app (eg. gitjournal/iawriter) vs navigate to the mobile website 🤷‍♂️ I edit our repos on mobile web from time-to-time, but yes, likely not the norm.

Is there interest in supporting the HTML abbreviation syntax, e.g.

*[HTML]: HTML

?

I took a quick look at getting it working and it looks like it's supported in Kramdown, the renderer used in Jekyll, but Dendron's buildSite command seems to mangle the syntax:

_[HPC]: High Performance Compute
\*[IoT]: Internet of Things

I think there's a Remark plugin that'll do the job, I'm just getting a development env set up 😅

@User I've never been an org mode user - I feel like I missed the boat with emacs or something but it seems like a good move to allow other workflows to benefit from the hierarchy and perusal of notes that dendron has.

Why org mode? I'd used org mode before but I think markdown is better, maybe I'm used to md

@User what is the abbreviation syntax? this was the first result I found on google: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/abbr also, just wrote a summary for our remark pipeline yesterday so this might help if you're thinking of adding to it :) https://dendron.so/notes/d8a09d7b-8693-437c-8a2c-2bfe0b3c2768.html

@User got it. for some reason, i thought you were one of the emacs folks 😅 i realize d i had you confused with the person who submitted this issue https://github.com/dendronhq/dendron/issues/178

@User there's certain functionality in org-mode like toggling bullets, agendas, timers, aggregating todos, that are hard to do anywhere else. working on implementing those features natively into dendron but in the meanwhile, i'm exploring if there's an easy way for folks to use org-mode functionality since vscode has extensions that support it

This is great, thanks. I’m not sure which Markdown dialect it originated in, but it renders to the HTML abbr element. You use the footnote-like syntax to provide the abbreviated and expanded form, and references to the abbreviated form above the footnote are wrapped in an

There’s a remark plugin that provides that syntax but I wasn’t sure how best to add a typescript typing for it. I can have a go later 🙂

@User @User reading over my message, i noticed i had a typo 😅 i'm in favor of option 1 -> supporting

org

files in dendron. currently, if folks want to use org-mode, i would recommend using the org extension and setting markdown files manually to org-mode if you want dendron to pick it up. in the future, we want to handle multiple markup types (eg. restructured text is another biggie). that being said, it'll be a while (eg. end of the year or next year) until I can work on that.

Since there is some vsc extensions that supports org mode, does it mean that we can use it in dendron now? @User

Ha no worries!

@User you can. its just a little cumbersome because those extensions look for files with a

.org

extension. you can get around this by manually setting the language on the note

wait, isn't the only thing that i should do is changing my file types into

.org

after installing one of those extensions?

yep. the problem is that currently, dendron preview expects markdown files so its one or the other. you can toggle between both. it all works - it's just kind of a kludge right now

ahh, hope you can get this supported in the future

but I don't use org mode so frequent personally, i played around org-roam before though

its definitely a nice to have feature at the moment unless some aspiring emacs hacker likes to implement it now 😅

> This is great, thanks. I’m not sure which Markdown dialect it originated in, but it renders to the HTML abbr element. You use the footnote-like syntax to provide the abbreviated and expanded form, and references to the abbreviated form above the footnote are wrapped in an @User got it. as for typescript syntax, I would check if someone has already made a type definition ( @types/packagename)

This articles describes using google collab as a free way to have vscode running in the cloud. Tried it out and seems to work (caveat is that the default setup with a password did not work for me). It doesn't have access to any extension marketplace by default. That being said, with the right bootstrap script, you could probably get a free version of Dendron running in the cloud :D https://amitness.com/vscode-on-colab/

That being said, since this is a google product, I expect it to be sunset without any notice at any time :/

> this is still very rough but i've written out a short note on how org-mode can be currently enabled in dendron and how we might implement it in the future. feedback appreciated 🙏 > https://dendron.so/notes/c3800271-dd56-46fb-8de7-e850f3c006b7.html @User I very much appreciate you looking into org-mode. While I am definitely more comfortable with org syntax than markdown, that is definitely not what I miss from org-mode and I think trying to get Dendron to work with both syntaxes will be a lot of work that only will benefit a few people.