So I currently use the export feature in plaintext for version control over my novel scenes, and I'm wondering how v3 will impact that.
Windows doesn't have the version compare feature, and the snapshots just sort of appear in the notes and don't have logs and diffs and blame and all of the things version control brings--not that I don't use and appreciate them!
To that end:
- Will MultiMarkdown be an option for "export" in v3 on windows? With the upcoming style support, this looks really promising! Yes, per blog
- Is there / will there be a way to automate an export (command-line argument, perhaps?)
- Possible for compile to support a folder structure like export does?
- Will the post-processing/ Pandoc stuff written about also exist in the windows version? I saw Scrivomatic and that looks cool, but currently mac-only? Yes, per blog? Confirmation?
- Is it still worth it to report bugs to the v1 export/compile features on windows? Found a couple.
Really, any small feature improvements you can throw to version control folks would be great! I currently select my whole novel at the end of each day, wait for it to load in the editor, export UTF8, then commit it to my git repository. It's not insufferable, but with multimarkdown and any sort of automation, it could be great. (I secretly hope that scrivener will someday integrate git and use multimarkdown as the underlying file structure to give us native version control, but I imagine that's many years off if ever.)
In addition, any thoughts or expertise from those who add their work to version control (or use pandoc/multimarkdown and have ideas on how to do it better) would be GREATLY appreciated!
P.S. Thanks for all the support you guys do, your product is second-to-none.