Live data from Hacker News

Import and Export Markdown in Google Docs

workspaceupdates.googleblog.com

11–20 of 140 posts

Re: Import and Export Markdown in Google Docs

#12
post #5

If 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

#13
post #12
post #5

If 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?

Because not everyone is interested in setting up a Pandoc/Latex toolchain. Overleaf almost solved this problem but they don't support Pandoc as a frontend and want money unless you self-host.

Re: Import and Export Markdown in Google Docs

#14
This would have been very useful at several companies I worked at as a product manager for release blogs.

I 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

#17
post #10
post #9

No 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)

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

#18
post #17
post #10

Earlier 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.

It would let you paste a lot of existing markdown into google docs

Re: Import and Export Markdown in Google Docs

#19
post #17

Earlier 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

They meant here on HackerNews. The only thing I really miss sometimes is a way to quote without resorting to indented code blocks.

> Just a tiny hint that any paragraph like this starting with a greater-than sign is a quote.

Post reply on HN