Language Selection

English French German Italian Portuguese Spanish

Scrivener Writing Software has a Linux Version

Filed under

In some ways, Scrivener is the very embodiment of anti-Linux, philosophically. Scrivener is a writing program, used by authors. In Linux, one strings together well developed and intensely tested tools on data streams to produce a result. So, to author a complex project, create files and edit them in a simple text editor, using some markdown. Keep the files organized in the file system and use file names carefully chosen to keep them in order in their respective directories. when it comes time to make project-wide modifications, use grep and sed to process all of the files at once or selected files. Eventually, run the files through LaTeX to produce beautiful output. Then, put the final product in a directory where people can find it on Gopher.

Gopher? Anyway …

On the other hand, emacs is the ultimate linux program. Emacs is a text editor that is so powerful and has so many community-contributed “modes” (like add-ins) that it can be used as a word processor, an email client, a calendar, a PIM, a web browser, an operating system, to make coffee, or to stop that table with the short leg from rocking back and forth. So, in this sense, a piece of software that does everything is also linux, philosophically.

And so, Scrivener, despite what I said above, is in a way the very embodiment of Linux, philosophically.

I’ve been using Scrivener on a Mac for some time now, and a while back I tried it on Linux. Scrivener for the Mac is a commercial product you must pay money for, though it is not expensive, but the Linux version, being highly experimental and probably unsafe, is free. But then again, this is Linux. We eat unsafe experimental free software for breakfast. So much that we usually skip lunch. Because we’re still fixing breakfast. As it were.

Details with Screen Shots Here

Anyway, here’s what Scrivener does. It does everything. The full blown Mac version has more features than the Linux version, but both are feature rich. To me, the most important things are:
A document is organised in “scenes” which can be willy nilly moved around in relation to each other in a linear or hierarchical system. The documents are recursive, so a document can hold other documents, and the default is to have only the text in the lower level document as part of the final product (though this is entirely optional). A document can be defined as a “folder” which is really just a document that has a file folder icon representing it to make you feel like it is a folder.

Associated with the project, and with each separate document, is a note taking area. So, you can jot notes project-wide as you work, like “Don’t forget to write the chapter where everyone dies at the end,” or you can write notes on a given document like “Is this where I should use the joke about the slushy in the bathroom at Target?”
Each scene also has a number of attributes such as a “label” and a “status” and keywords. I think keywords may not be implemented in the Linux version yet.

Typically a project has one major folder that has all the actual writing distributed among scenes in it, and one or more additional folders in which you put stuff that is not in the product you are working on, but could be, or was but you pulled it out, or that includes research material.

You can work on one scene at a time. Scenes have meta-data and document notes.

The scenes, folders, and everything are all held together with a binder typically displayed on the left side of the Scrivener application window, showing the hierarchy. A number of templates come with the program to create pre-organized binder paradigms, or you can just create one from scratch. You can change the icons on the folders/scenes to remind you of what they are. When a scene is active in the central editing window, you can display an “inspector” on the right side, showing the card (I’ll get to that later) on top the meta data, and the document or project notes. In the Mac version you can create additional meta-data categories.

An individual scene can be displayed in the editing window. Or, scenes can be shown as a collection of scenes in what is known as “Scrivenings mode.” Scrivenings mode is more or less standard word processing mode where all the text is simply there to scroll through, though scene titles may or may not be shown (optional).
A lot of people love the corkboard option. I remember when PZ Myers discovered Scrivener he raved about it. The corkboard is a corkboard (as you may have guessed) with 3 x 5 inch virtual index cards, one per scene, that you can move around and organize as though that was going to help you get your thoughts together. The corkboard has the scene title and some notes on what the scene is, which is yet another form of meta-data. I like the corkboard mode, but really, I don’t think it is the most useful features. Come for the corkboard, stay for the binder and the document and project notes!

More in Tux Machines

OSS Leftovers

  • Libjpeg-Turbo 2.0 Beta Brings More AVX2 SIMD, Improved CMake Build System
    A Phoronix reader recently pointed out that LibJPEG 2.0 Beta quietly shipped last month as working towards the next big update for this speed-focused JPEG library. Libjpeg-Turbo 2.0 beta is available for testing and it brings AVX2 SIMD support for colorspace conversion, chroma downsampling/upsampling, integer quantization and sample conversion, and integer DCT/IDCT algorithms. These AVX2 SIMD accelerated paths are generally bringing gains anywhere from 9% to 36% faster depending upon the operation. This version is also bringing SIMD acceleration for Huffman encoding on SSE2 CPUs and Loongson MMI SIMD implementations for more functions.
  • A look at Rancher 2.0
    Last December, we announced a Kubernetes Cloud Native Platform in partnership with Rancher Labs. Built on Canonical’s Distribution of Kubernetes and Rancher 2.0, the Cloud Native Platform will simplify enterprise usage of Kubernetes with seamless user management, access control, and cluster administration. Join our webinar to get a tour of the platform!
  • Mozilla's Common Voice Project, Red Hat Announces Vault Operator, VirtualBox 5.2.10 Released and More
    Participate in Mozilla's open-source Common Voice Project, an initiative to help teach machines how real people speak: "Now you can donate your voice to help us build an open-source voice database that anyone can use to make innovative apps for devices and the web."
  • Collabora Online 3.2 Supports Chart Creation, Other Features
    A new version of Collabora Online is now available, the web-based open-source office suite derived from the cloud version of LibreOffice.
  • DragonFlyBSD Kernel Gets Some SMP Improvements
    It looks like the DragonFlyBSD 5.4 release will be delivering at least a few kernel-level performance improvements. It turns out just hours after wrapping up the latest BSD vs. Linux benchmarks, Matthew Dillon pushed a few performance tweaks to the Git tree for DragonFly.
  • Best Open Source 3D Printers
    In simplest terms, an open source 3D printer refers to a 3D printer whose hardware and software information are available to the public, typically under a license. The information can be used by anyone to build, modify, or improve the 3D printer. If you’re looking for real open source 3D printers, then you’ve come to the right place. In this guide, we introduce you to completely open source 3D printers. The hardware and software information of all the products listed here can be easily found on the internet.

Microsoft Linuxwashing and Research Openwashing

today's howtos

Why Everyone should know vim

Vim is an improved version of Vi, a known text editor available by default in UNIX distributions. Another alternative for modal editors is Emacs but they’re so different that I kind of feel they serve different purposes. Both are great, regardless. I don’t feel vim is necessarily a geeky kind of taste or not. Vim introduced modal editing to me and that has changed my life, really. If you have ever tried vim, you may have noticed you have to press “I” or “A” (lower case) to start writing (note: I’m aware there are more ways to start editing but the purpose is not to cover Vim’s functionalities.). The fun part starts once you realize you can associate Insert and Append commands to something. And then editing text is like thinking of what you want the computer to show on the computer instead of struggling where you at before writing. The same goes for other commands which are easily converted to mnemonics and this is what helped getting comfortable with Vim. Note that Emacs does not have this kind of keybindings but they do have a Vim-like mode - Evil (Extensive Vi Layer). More often than not, I just need to think of what I want to accomplish and type the first letters. Like Replace, Visual, Delete, and so on. It is a modal editor after all, meaning it has modes for everything. This is also what increases my productivity when writing files. I just think of my intentions and Vim does the things for me. Read more