![]() ![]() In Zotero, I use a plugin called Better BibTeX, which can export my entire library in a database file with the extension. I keep all my citations in Zotero, which I resisted for a long time but then just took a week to make it happen and I can’t imagine life without it. The real clincher for me is adding in citations. But I think the good thing about this system is it can accommodate whatever you want to design, and isn’t limited by whatever the main program (Word, Scrivener, etc.) expects your workflow to be. Mine is writing by constantly rewriting and iterating new drafts, which you can tell from my directory structure. ![]() The actual writing itself is fairly uninteresting and honestly you’ve got your own style that works for you. I also wrote a small script to automate starting new projects with that structure. I use a project manager plugin there to make switching between various projects easier. You can see that it’s mirrored in VS Code. I have no particular affection or dislike for this text editor it just seems like the one that’s getting the most development attention at this present juncture, and doesn’t drain down my laptop’s battery. I’ve cycled through most of the major ones-Notepad, Sublime Text, Atom, and even tried my hand at emacs and vim-and have finally settled, for now on VS Code. I do basically all my writing and coding and general living in a text editor. These lessons are honestly better and more schematic than my post, but since this space changes so frequently I thought it’d be worth having my contribution for 2020. It’s also one that strongly draws from a few others’: in particular Scott Selisker’s “Plain Text Workflow for Writing with Atom” and Grant Wythoff’s and Dennis Tenen’s “Sustainable Authorship in Plain Text using Pandoc and Markdown”. There’s definitely stuff in it that only works for me because I’m willing to tolerate. My workflow is one that I developed early on in my graduate studies with the intention of maximizing flexibility and minimizing the temptation to fiddle with it further. Since they’re not the first to ask this, and since I went ahead and wrote it up for them, I thought I might as well post it on here for anyone else interested in workflows that incorporate plain text, citation integrations, and open-source software. Not like, existentially or anything (although it’s a challenge these days!), more my workflows for writing. Earlier today, a friend asked me how I write. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |