I’m sure it’s technically possible to set up updating with every edit, but I’m not clear on that so wouldn’t focus on it at this point. This suggests to me either there’s some other way to use this API, client-side API looks about right. Glad to hear you like Karthik yeah, it sounds like you follow me - in an ideal world, you’d end up with real-time changes in sync (in both directions) between Google Doc and the Rmarkdown, but (for now at least) the ‘triggers’ available for Apps Script are limited to time repeats, at most every hour. I’d love to hear others’ thoughts on this have desktop publishing covered but Google Docs is a nice cross-platform, accessible and (currently) free program so could be worth considering or developing with. I’m aware Microsoft Word, OpenOffice etc.

Basically, it could allow us to write more effectively, and also collaboratively (Google Docs are excellent for collaboration, they’re used for real time shared document editing at academic events sometimes). One of my main complaints (and presumably other users’ experience) in writing in Rmarkdown is the cognitive overhead of looking at code rather than a WYSIWYG document. You could potentially then have a setup to preview changes to documents without actually having to edit Rmarkdown - the reproducible document would still be available. Ideally, you could get the markdown output written to Drive instead, or failing that retrieve the attachment with twitteR (GitHub: geoffjentry/twitteR). When run, the script emails markdown as an attachment to the Gmail inbox associated with the Google account logged into Drive. and the research panel, and more sophisticated features like change tracking. Google Drive is potentially a far better environment to draft research documents in than starting directly in Rmarkdown from a text editor/Rstudio - keyboard shortcut simplicity for hyperlink entry ( Ctrl+ K), etc. The repo contains a Google Apps script (essentially Javascript), but there’re currently a few bugs in it - italicised/bold links don’t convert properly, something like an off-by-one error, but the debugging is pretty straightforward.įor those who follow it, the Jupyter (née IPython) project is working on Google Drive integration - see the jupyter/jupyter-drive repository for details. upstream of the existing RStudio/Rmarkdown framework.

I just found this repo which contains a script to convert Google Docs to markdown, and it’s got me wondering whether Google Docs could be used somehow to go about Rmarkdown document editing differently, i.e.

Icing google drive url