![]() Markdown, for those who aren’t familiar, is a plain text format with very lightweight markup for things like bold/italics, links, and the like. So my workflow has the following elements: I want to use git for version control so that I can recover prior versions if something gets horribly screwed up. I like being able to relatively seamlessly switch between writing on my MacBook and on my iPad.Į. I also hate manually formatting my citations.ĭ. Most of the major alternatives to word (OpenOffice, Google Docs, Pages) are crap.Ĭ. Word “features” like styled paste, auto-conversion of URLS to links, bizarre dictatorial bullet point numbering, etc. I also want something that doesn’t impose involuntary formatting on me. My writing needs to be scriptable-I need to be able to read my writing into an ordinary programming language as a string, run code on it, and spit it back out again as a string. If I want to do something weird or automated with my content, I want to be able to do so. It takes longer to start than XCODE, which, for those of you who program, you’re probably screaming in horror at the very idea.) I have a brand new souped up 16-inch Macbook Pro with an i9 and 32 gigs of ram. (It’s utterly mind-blowing how badly Word performs. I want something that doesn’t crash or hang all the time, unlike Word. Yet I recognize that many people that publish things I write need Word format, so I need to do something that converts to Word fairly readily. Subconsiderations: ![]() I won’t use it if it can be helped at all. I’m incredibly paranoid about losing work.ī. Here are the considerations, in rough order of priority, that drive me:Ī. This is a work in progress document I’ve promised to share my toolkit with a couple people, so, as those people say to me “hey, this makes no sense,” I’ll probably edit to clarify. ![]() I have an unusual and complicated academic writing workflow/toolkit, but one that might be of use to some other people, so I thought I’d share it here. This one is for academics rather than practitioners, though some of the details are applicable to practitioners as well. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |