A quick update. I made a pull request to https://atom.io/packages/script . It now has pandoc support. It requires the panzer pandoc wrapper https://github.com/msprev/panzer and the pandoc-flavored-markdown language package in Atom https://atom.io/packages/language-pfm . You also need to launch Atom from the terminal unless you’ve set up your GUI to see your shell bin.
I opted to use the panzer wrapper rather than vanilla pandoc because I use pandoc for a variety of tasks, writing articles, CVs, letters, syllabi etc. These have different sets of settings, custom templates etc etc. Panzer allows you to easily define what a document is in the YAML metadata block, eg:
title: "title here"
This saves you having to construct a lengthy pandoc command (and then store it somewhere so that you can reproduce the article at a later date).
If you don’t want to use panzer you can override this by selecting “Configure Script”, then in the dialogue that opens entering “pandoc” in the command field.
One limitation: I set it to only outputs pdfs, because this is mainly what I use pandoc for. This is because, annoyingly, pandoc doesn’t accept pdf as an output format, that is,
-t pdf is not an option. You can only produce a pdf in pandoc by setting the output filename to pdf, eg
-o myDocument.pdf. However, this would mean that you would lose the automatic naming of the output file on the same path as the input file, which is kind of the point of using a feature like this, saving you typing a lengthy pandoc command into terminal.
The owner of the script package suggested that a custom pandoc package might be the way to go in order to conveniently access the various output formats that pandoc offers.
But, if you mainly use pandoc for outputting pdfs, the script package is a good solution.