91–100 of 179 posts
came join the dark side, we have tables³ :)
1. https://docutils.sourceforge.io/rst.html 2. https://www.sphinx-doc.org 3. https://docutils.sourceforge.io/docs/ref/rst/restructuredtex...
MD is popular because most do not know org-mode, that's is. As usual bad things spread most thanks to some third party interests...
I think the author is missing a fairly major point, that Markdown was intended to be a way to process text written the way people already wrote it. ASCII is absolutely the best way to write documents, if you're working in a primarily ASCII environment. Crabbit old bastards like me who remember the dialup BBS days consider Markdown-like text to be standard - underline things with a row of hyphens, mark a heading by un…
/italics/
*bold*
Earlier quoted context omitted.
Does slack even use markdown? It seems to me that it just uses some markdown-like sybtax as a shortcut for generating its rich text. Like Google Docs will start a list after - .
There's an option to post in markdown instead of WYSIWYG. The one and only reason I use Slack's WYSIWYG instead of markdown is because their markdown parser doesn't handle links. If they just fixed that, I could stop using their WYSIWYG and its atrocious handling of inline code blocks.
>It’s barely a spec Which is fitting. It evolved long before the term 'markdown' itself existed, a practice having been used in email and usenet and BBSes for many years before. The 'spec' is just trying to codify the already-existing usage, which evolved organically in many different areas by many different people. >You need to use a WYSIWYG tool or you don’t use it. No, no you absolutely don't. Almost no one uses a…
> No, no you absolutely don't. Almost no one uses a WYSIWYG for markdown. That would completely negate the point. > Probably 99% wrong. I've never met anyone that chose to make things more difficult for themselves by using a clunky WYSIWYG instead of just typing the markdown in a text editor. Sometimes that's an IDE, but that's beside the point. Plain text does matter. You repeat this point but the trend of markdown…
>It’s barely a spec Which is fitting. It evolved long before the term 'markdown' itself existed, a practice having been used in email and usenet and BBSes for many years before. The 'spec' is just trying to codify the already-existing usage, which evolved organically in many different areas by many different people. >You need to use a WYSIWYG tool or you don’t use it. No, no you absolutely don't. Almost no one uses a…
> Markdown will never get beyond developers. My brother wrote his master thesis in LaTex. Being a non-techie (he's an archeologist) I had to do all the 'fixing'. We switched to LaTex after both Word and OpenOffice Writer made working with the document a non-option. I also used git to manage changes. This was 2009. He could not have done it without my help with this setup. But he could also not have done it without me…
- It is a what you see is what you mean editor - It supports some markdown annotations to support your writing flow - it exports in LaTeX, Markdown - It creates a PDF based on LaTeX and allows to choose a template with some configurations
On one of my sites (message board), I use Markdown but custom HTML tags for extensions like file attachments. You can allow these custom tags in your HTML sanitizer and replace them at render time with output from some template. So dragging and dropping a file would add to your input box. Seems like a decent middle ground with common things easy to type with Markdown and special magic as HTML tags.
Earlier quoted context omitted.
> On the actual spec/implementation: yes, it's a complete disaster. Especially the way it is kind of mapped on to HTML, so you get weird things like writing "1. blah; \ 1. blah" makes a numbered list with a 1 and a 2. There is a trade off here though. When people sit down to write something that doesn't have weird edge cases they're not likely to end up with a lightweight markup like Markdown. So simultaneously the s…
I've heard very similar arguments, for Perl, a couple of decades ago. And yeah, it's not entirely wrong. Perl was useful, too. But I desperately want the thing that is for markdown what modern JavaScript, Python and Go have become for Perl. I want a markup language that supports the most basic things, looks reasonable on the eyes in un-rendered form (so we don't need terrible rich text editors everywhere), and is ver…
Asciidoc might be it. It's fairly comprehensive.
That, or Org-mode -- but then you have to learn Emacs.
Consumers should be able to control the presentation of the content they view. They should provide the theme. Markdown could provide the minimal content and linking.
It seems like it would be possible to remake all the major web properties this way while returning control back to the consumer and preventing egregious advertising, tracking, and popups. Reddit, Google Search, substack/medium/etc all could be remade in this more consumer-centric viewport. The markdown browser would be a strong promise a lot of anti-user behavior.
The modern browser is more an application development platform - let's treat it that way. A web browser's presentation should be in control of the consumer.
>It’s barely a spec Which is fitting. It evolved long before the term 'markdown' itself existed, a practice having been used in email and usenet and BBSes for many years before. The 'spec' is just trying to codify the already-existing usage, which evolved organically in many different areas by many different people. >You need to use a WYSIWYG tool or you don’t use it. No, no you absolutely don't. Almost no one uses a…
> Markdown will never get beyond developers. My brother wrote his master thesis in LaTex. Being a non-techie (he's an archeologist) I had to do all the 'fixing'. We switched to LaTex after both Word and OpenOffice Writer made working with the document a non-option. I also used git to manage changes. This was 2009. He could not have done it without my help with this setup. But he could also not have done it without me…
Is she though? Markdown doesn't even have image captions or like support for citations.