public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Gdoc to md
Date: Sat, 20 May 2023 10:10:59 -0400	[thread overview]
Message-ID: <fcfc070a-495f-6669-8045-1517c8548f8d@reagle.org> (raw)
In-Reply-To: <b3abcff6-701d-4a64-b5b0-9faee1b2b1a4n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

It's in Beta, and I've not used it, but you might be interested in https://zed.dev/ for collaboration.

You might also try a shared online platform, like https://hackmd.io/ .

Or, Quarto with Conflunce: https://quarto.org/docs/publishing/confluence.html


On 5/19/23 17:49, Mark Pinsley wrote:
> I have a whole bunch of google docs in a folder. Let say 20 files for the time being, I have a lot more than that, but in one directory there are twenty files.
> 
> I want to convert all of these files from .gdoc to .md
> 
> 1. I didn't see any way for pandoc to do this, is there a way?
> 2. Is there a way to batch process this? I don't want to have to go into every google doc and save as, and then convert
> 
> Lastly, what tools are you using to collaborate in MD. are you putting things into github? If so are you using the Github editor or another editor. I was using StackEdit, but it doesn't look like it is being supported.
> 
> Thanks
> 
> -- 
> You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org <mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>.
> To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/b3abcff6-701d-4a64-b5b0-9faee1b2b1a4n%40googlegroups.com <https://groups.google.com/d/msgid/pandoc-discuss/b3abcff6-701d-4a64-b5b0-9faee1b2b1a4n%40googlegroups.com?utm_medium=email&utm_source=footer>.

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/fcfc070a-495f-6669-8045-1517c8548f8d%40reagle.org.


  parent reply	other threads:[~2023-05-20 14:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-19 21:49 Mark Pinsley
     [not found] ` <b3abcff6-701d-4a64-b5b0-9faee1b2b1a4n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-19 21:55   ` Craig Parker
     [not found]     ` <CAHzYjEskCjZkHZcxmNj2n5Y19Y-PN3gq+DxWS8cUXg6XwcfsGA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-05-20  0:38       ` Alan Tyree
2023-05-20 14:10   ` Joseph Reagle [this message]
2023-05-21  7:34   ` BPJ
     [not found]     ` <CADAJKhA7A1QLd5SMqkvxs+NCCSxSap-NBVzG1-XW1wf8zjdxwg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-05-21 14:47       ` Mark Pinsley
     [not found]         ` <8A9C0319-D2C4-4A77-B50E-02B2FCC050AD-85mlybbDJu0gu7xKmIUUUg@public.gmane.org>
2023-05-22  7:20           ` ThomasH
     [not found]             ` <948f1dc9-3efb-4b0c-b6b8-d72b446999adn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-05-22 13:05               ` Mark Pinsley
     [not found]                 ` <CAOtJyj6a2TLz9fUC+f0RcHXCy3a=n+WaaE=zskP3_tsDnPrCLA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-05-22 15:40                   ` BPJ
     [not found]                     ` <CADAJKhBnEqDvSh6EEm56zah-+Tt0hYwnQUbm3fjQqzcbvWh7Aw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-05-22 15:57                       ` BPJ
     [not found]                         ` <CADAJKhC4jVpHARoWWhuUSHbMzC=zk=hnvkdS6+Ly6ci6XhuykQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-05-22 16:23                           ` BPJ
2023-05-22 15:34           ` BPJ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fcfc070a-495f-6669-8045-1517c8548f8d@reagle.org \
    --to=joseph.2011-t1oy19wchswdnm+yrofe0a@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).