Import and Export Markdown in Google Docs
11–20 of 140 posts
Re: Import and Export Markdown in Google Docs
#12If this is implemented properly it’ll be a game changer for collaboration on papers. Means one can write a paper with colleagues in markdown and then easily knit with pandoc/quarto. Cheaper than overleaf etc.
Re: Import and Export Markdown in Google Docs
#13If this is implemented properly it’ll be a game changer for collaboration on papers. Means one can write a paper with colleagues in markdown and then easily knit with pandoc/quarto. Cheaper than overleaf etc.
Why not a markdown doc + git with each colleague using their own text editor/IDE of choice?
Re: Import and Export Markdown in Google Docs
#14I always start editing in gdocs because it's so much easier to collaborate on than any blog platform, but then you always need to copy/paste the content once final into the blog and nearly every time, it copies some elements of formatting into the rich HTML editor I don't want (fonts, font sizes, etc) while I do want some things (headings, bold, italics). It's usually easy to import markdown to blogs or trivial to convert it to stripped-down HTML that can be imported. One of the teams I worked on built a simple gdoc script to do this
Re: Import and Export Markdown in Google Docs
#15Could you build a confluence/wiki like system on top of this?
Re: Import and Export Markdown in Google Docs
#16Meanwhile, Trello is once again threatening to force everyone onto the new rich-text editor and disable the old markdown one.
Re: Import and Export Markdown in Google Docs
#17No support for code blocks still: ```java String x = "xxx"; ``` No quoting: The docs for `libfloof` state: > The floof is 4 bytes long, at most. And when I type `code` with backticks at the start of a line, the word 'code' is formatted as code as expected, but auto-correct automatically capitalises it to 'Code' — which should never be done with code fragments. So this is basically just headings, italics, bold, and li…
We just have to iterate in the "markdown support feedback/help" pulldown I guess. because without ```code``` it's not useful. Looking at you HN... (ok at least we have 2 indents codeblock)
Beyond that, I think support for ```sh type highlighting would be awful, one of the best things about HN is how clean it is, I'd hate to see syntax highlighting or pictures or whatever when scrolling.
Re: Import and Export Markdown in Google Docs
#18Earlier quoted context omitted.
We just have to iterate in the "markdown support feedback/help" pulldown I guess. because without ```code``` it's not useful. Looking at you HN... (ok at least we have 2 indents codeblock)
What would ``` add that you can't already do with two indents? Beyond that, I think support for ```sh type highlighting would be awful, one of the best things about HN is how clean it is, I'd hate to see syntax highlighting or pictures or whatever when scrolling.
Re: Import and Export Markdown in Google Docs
#19Earlier quoted context omitted.
What would ``` add that you can't already do with two indents? Beyond that, I think support for ```sh type highlighting would be awful, one of the best things about HN is how clean it is, I'd hate to see syntax highlighting or pictures or whatever when scrolling.
It would let you paste a lot of existing markdown into google docs
> Just a tiny hint that any paragraph like this starting with a greater-than sign is a quote.
Re: Import and Export Markdown in Google Docs
#20and