3 ms·
Does this only support GitHub-flavoured markdown? I didn't find the website very informative (honestly, confusing if anything), and couldn't find reference to
by GordonS 10y ago
Does this only support GitHub-flavoured markdown?
I didn't find the website very informative (honestly, confusing if anything), and couldn't find reference to anything else, like Asciidoctor.
- vonklaus 10y agoI like it. Used it for >several months. If you have used mou before it is similar. You can edit the themes (ive downloaded some from github) and you can configure a couple markdown flavors out of the box iirc. It renders in place in real time unlike some of the ones that load on half of the screen. Worth a download. They smoothed out a lot of the issues with updating content & cursor movement. Best markdown editor ive used, if viewing the rendered markdown matters to you. You can export as a pdf and a couple other doctypes which is nice for sending to non-technical teamenbers who have no markdown reader.
- GordonS 10y agoAny idea if it works with Asciidoctor?
- vonklaus 10y agoNot familiar with that. Probably not. Its a few MBs of diskspace & works out of the box. Prob be quicker to dl & dump it if you dont like it. All editors/notes/workflow are highly subjective, i tried macdown, mou, a bunch of similar os x notes clones, notes, evernote, ect. I like this for notes & simple docs. I would really like it if it had a sidebar with directories but the reason so many of these things exist is that everyone angry enough just builds their own.
- algorithmsRcool 10y agoAccording to their docs they use Github-flavored markdown. But they also apparently support lots of extensions to it. See here http://support.typora.io/Markdown-Reference/ http://support.typora.io/Markdown-Reference/ And here for other docs http://support.typora.io/ http://support.typora.io/
- joshpadnick 10y agoHuge fan of Typora. My one issue is with line breaks. I like to edit GitHub README's directly in Typora and add line breaks around the 80 character mark, but Typora's window seems to wrap them differently. For example: - README on GitHub: http://i.imgur.com/pq581xN.png http://i.imgur.com/pq581xN.png - README in Typora: http://i.imgur.com/oYnyzMJ.png http://i.imgur.com/oYnyzMJ.png I posted a support ticket, and the developer responded that "the difference is that Typora will render single line break, while Github will ignore those single line break". That's fine, but GitHub parity seems like a top use case, so AFAIK this remains an open issue.