Over the past couple of days I have been toying with the idea of formally continuing my academic studies and writing a PhD dissertation. As I have using “org-mode” for a little while now, I was curious about setting it up for an extended humanities project ¹. Briefly, org-mode is an extension for the multipurpose software GNU Emacs, based around plain text markup. Among other features, it hosts a convenient way to write and outline text, that one can then export to other intermediary formats, such as LATEX. Additionally, it is a powerful productivity tool for activity planning and scheduling (including to-do lists and an agenda), all in plain text². While it can be a useful way to write extensive prose documents, its use is not too apparent within the Arts and Humanities academic community. The purpose of this post is therefore to explore my experiences with GNU Emacs and org-mode, within the backdrop of humanities writing tasks. This includes sharing some of the my own choices in terms of setup, with appropriate addons for, for example, reference management and note taking ³.

Regarding GNU Emacs, it is mainly associated with the software development and systems administration world, but I have come across configurations for humanities research as well. In my area of interest this includes, for example, Christian Wittern’s Mandoku, designed for research into pre-modern Chinese texts [2]. Briefly, Mandoku hosts a suite of tools for philological analysis, translation and annotation of primary literature. And it includes integration to Kanseki Repository, an online database of texts in computer readable format compiled by Wittern and his team. Other related examples include that of Jay Dixit, a New York based science writer, who has honed his GNU Emacs configuration for professional writing tasks [3]. Through his demonstration, Dixit displays the modularity of the software beyond its applicability in computing and Unix administration. Lastly, one can find further related examples within the GNU Emacs “emacs-humanities” mailing-list, and its archives.

As highlighted above, org-mode is a GNU Emacs mode for a variety of text based tasks, including notes, authoring documents, and maintaining to-do lists. Being analogues to other markup languages, it involves utilising a predefined syntax to manipulate a document in plain text. Everything being plain text means that one can open and edit an org-mode document in any conventional text editor. Additionally, as with other markup systems, one can easily export org-mode files to different intermediate formats such as HTML and LATEX. This means that one can simply write without needing to think about formatting, essentially making it a feature rich distraction-free writing environment. Its defining feature for me, as it is for others, is its highly flexible structured text formatting allowing one to easily outline and plan documents. It uses marks (by default an asterisk) to indicate nested levels of a hierarchy (trees) that the user can fold to hide their respective contents. This, combined with GNU Emacs use of buffers, allows one to have a document outline always visible, while simultaneously writing content within any section.

Apart from org-mode, I have also been using other modes to enhance my writing experience within GNU Emacs. This includes, for example, writegood-mode that is helpful for me as a non-native English speaker, as it can highlight problematic uses of language. These include pointing out weasel words, passive structures, any unwanted idiosyncrasies, and also duplicate words. Other modes include synosaurus-mode for a thesaurus, wc-mode for wordcounting, olivetti-mode for helpful visual formatting within GNU Emacs, and engine-mode for quick web searches. Additionally, I grown to heavily rely on palimpsest-mode, which is a simple addon through which one can quickly highlight a text portion and archive it. This means that nothing gets deleted, and I can later refer to any text snippet (that did not initially fit into a section) without hassle.

While I am comfortable working with the above setup, it is difficult to integrate it into a conventional work flow that stresses software conformity and collaboration. Org-mode is not (readily) designed for web based interaction, relying on the user to install an Emacs client to fully engage with a file. Due to the required time investment, it is understandably difficult to convince someone to learn Emacs simply to open a single file. While org-mode does host a number of export options, these also have some limitations worth considering in terms of collaboration. This issue became apparent during my MA thesis, which I also wrote in org-mode using roughly the same tools as above. For example, reference links do not carry over to the exported “.odt” format utilised by LibreOffice. This was problematic as I needed to send my supervisor my project in a Microsoft Word readable format (converted from LibreOffice). However, I will be able to iron out these kinds of issues in the future as my familiarity with GNU Emacs and Emacs Lisp increases.

This post sought to share my experiences using GNU Emacs org-mode for humanities writing tasks, in this case with a future dissertation in mind. I believe I have settled for the basic writing environment in terms of completing a multi-year writing project, however, I still expect some tinkering to be had. This is especially due to not having first-hand experience writing or editing a 100,000+ word document, meaning some adjustment is inevitable. At this stage the main issue, I feel, concerns the smooth collaboration between author, supervisors, and any collaborators. Future posts here concerning org-mode for humanities research will likely discuss these issues further, together with trying to establish some feasible strategies to overcome them.