Freelance technical communicator to the stars. Podcaster, video maker, writer of interactive fiction
So far, I have written how to customize Atom and Visual Studio Code for writers. Those posts have proven popular, and people keep asking me about my favorite text editor. This series continues now with Sublime Text, an editor I used to use when I worked as a developer, and then fell out of love with, mostly because development stopped for some time. There was much confusion between versions 2 and 3, and then I discovered Atom, and then kind of forget about it. However, Sublime Text is experiencing something of a resurgence, and I thought it was time I revisited it to see how suited it is for writers. One caveat: while Sublime core development has re-awoken, many packages haven’t. As it’s an old and stable codebase, this may not matter, and packages probably still work. I have tried only to include packages that are compatible with Sublime version 3 and have some recent development activity.
To install packages, open up the control palette and use package control to search for and add packages.
Sublime has a handful of packages to make markdown editing better, again, finding them requires searching in package control, and again, I had mixed experiences with figuring out how to get them to work. For example, MarkdownEditing adds a light theme and centralizes the editor body, which I have always found better for writing work. It also adds a variety of shortcuts, linting, and convenience functions. Also, more useful for technical writers, MarkdownExtended adds support for YAML front matter and code block highlighting.
Of course, the venerable Pandoc has a package too.
Sublime has spell checking available by default, but you need to enable it by adding the following to your user settings file:
Under the hood, Sublime uses Hunspell, and you need to download any dictionaries in addition to US and GB English. It’s a shame it doesn’t tap into the in-built Hunspell that many operating systems have.
For a word count, use the WordCount package, which also has settings for calculating read times and some advanced features.
Sublime has the extensive SublimeLinter package that has a long list of official and contributed extensions (This is the best option). It’s hard to find a comprehensive list, but here’s some I found that may interest writers.
Though I must admit, I struggled to get a lot of them to work properly, the configuration isn’t always clear, and the display of linter messages isn’t as well integrated as with Atom and VSC.
If you want to lint code snippets included in your documentation, then there are options available for pretty much every language, but again, your mileage may vary using them.
Hmm, frankly, I would say no. If you are already using Sublime and understand how to get it to work in a more user-friendly way, then adding some writer focused packages enhances your experience. But for writers looking for new options, then Atom and Visual Studio Code are far better and more modern, and so are the packages available for them.
Originally published at dzone.com.
Create your free account to unlock your custom reading experience.