Live data from Hacker News

Import and Export Markdown in Google Docs

workspaceupdates.googleblog.com

1–10 of 140 posts

Re: Import and Export Markdown in Google Docs

#4

I thought copy as MD existed years ago and then went to look for it recently and it was gone. Now it's back. Am I losing it?

Maybe you've been using the GD2md-html plugin. I've certainly found it useful over the years, and will likely still use it for some of my workflows. https://workspace.google.com/marketplace/app/docs_to_markdow...

Re: Import and Export Markdown in Google Docs

#6

My guess is that this is strongly motivated by the success of LLMs. The lack of MD support makes manual IO from Docs to your favorite LLM lossy (or very annoying). Cool that it's fixed.

At this point, most major changes could be motivated by LLMs/AI.

Re: Import and Export Markdown in Google Docs

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

I'll add that writing a paper might be better handled by a more feature-full format like Asciidoc.

Re: Import and Export Markdown in Google Docs

#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 links?

It's really annoying when you need to share technical documentation with lots of code and code-like content with people and they've started doing the spec in Google Drive. Just give me working Markdown.

Re: Import and Export Markdown in Google Docs

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

Post reply on HN