On Sun, Feb 14, 2016 at 2:50 AM, John Wiegley <[email protected]> wrote: > I prefer to have docs maintained under Git, offline accessible, in an open > format that Emacs is able to edit. That could be Markdown, LaTeX, TeXinfo, or > any of the other free formats available.
I agree with this - the offline ability, combined with history and the ability to grep for what you want is hugely important to me. You can also run this kind of docs through a static site generator (Jekyll or Hugo work great for this, possibly with a run through Pandoc as needed), and generate very nicely structured, web-based documentation sites. > I can't think of even one advantage > Google Docs has to offer me, given the way I work on software projects: It's > not offline accessible, it uses its own UI, it puts me in the browser for > editing, and I can't use Git to examine history. I might as well be editing a > Microsoft Word document in a network mounted folder, as work sometimes makes > me do. Agreed. I would also add that Google Docs, and pretty much all word processors are designed for <10 page unstructured documents, and quickly fall down on any larger, structured documentation work. I've found this Google Docs to Markdown conversion script to be useful in the past: https://github.com/mangini/gdocs2md - Zack -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
