Weeknotes 2024 W41: Acquired taste

October 7​–​13, 2024
1400 words

Quick bits:


Shower thoughts:


Last week, I said that I probably wouldn’t pick up the work on my interpreter book,1 but I’ve poured all the material I had into a new Scrivener project, which means I might continue with it after all.

Before I can genuinely start writing the book, though, I need to finish the programming language that the book is built around. And frankly, I don’t know how far I want (or need) to go with this. At which point do I say that the language is good enough to start writing the book?

A big open question is whether Ruby is a good choice as an implementation language. It’s quite easy to get started with Ruby, but at some point, it becomes quite clear that writing an interpreter in an already interpreted language is not a great idea.

Perhaps I need to limit the scope: rather than a full-fledged programming language, I could limit myself to an (extensive) external DSL. I am not sure how well that’d sell as a concept, though.


I published a new short story: The Gap. At 700 words, it might fit more in the flash fiction classification rather than short story, but I’m happy with the outcome regardless.

I drafted it (at my regular Shut Up & Write meetup), did a quick revision on my laptop, and then printed it out for a final edit I planned for the day after. Strangely, after printing it out, I was afraid to even look at the printout, in fear of the writing being horrible on second look, as if either I had been entirely delusional about the quality of my writing, or the writing had somehow transformed itself into something grotesque overnight.

Truly, my primary struggle with fiction writing is psychological at this point.


Scrivener remains a bit of an acquired taste. I limit myself to writing Markdown in it, because it makes exporting content so much easier. However, Scrivener really isn’t a Markdown editor: it is a rich-text editor in which you can also write Markdown.

In fact, you can combine rich text formatting (like different typefaces, font sizes, and font styles like bold and italic), pure Markdown (like headings, emphasis, or Pandoc-style citation markup), and Scrivener styles. But if you were to combine all three approaches in a single document, you’d end up with an unmaintainable mess.

I think Scrivener would be better with a distinct split between rich-text and markup modes. In rich-text mode, you’d have rich text formatting and Scrivener styles, while in markup mode you’d be able to use pure Markdown and Scrivener styles.

Scrivener styles are great, and I use them extensively in my writing. Those styles translate to pure Markdown on compilation, so I don’t lose anything, and in Scrivener they show up in a visually distinct way. Here is an example of what that looks like (cobbled together from various unrelated bits of writing):

A screenshot of a Scrivener document. The text is mostly black on white, but some words and sentence parts are colored differently.

Not having to deal with raw Markdown markup is a benefit in my book: it is distracting visual noise.2 Highlighting semantically meaningful elements, like in the example above, is, I believe, a more sensible approach.

If only there were a dedicated Markdown mode that disabled all regular formatting options, like typefaces and font sizes and styles. I don’t need any of those, and I fear that I run the risk of using rich text formatting by accident that won’t export/compile properly.

But, you know… there is nothing else quite like Scrivener. Is it not amazing that there is a piece of software that is essentially irreplaceable, filling a niche so well?


Entertainment:


Toots and tweets:

Links:

Berlin links:

Tech links:


  1. I wrote about the interpreter book for the first time in Week­notes 2023 W05: Fridge cleaning↩︎

  2. My own markup language, D★Mark, has the same issue. As I mentioned a while ago, I might from now on be doing all my technical writing in Scrivener rather than with D★Mark. ↩︎

  3. Rick Burroughs, Alan Wake (New York: Tor, 2013). ↩︎

  4. Voyage of Time, written and directed by Terrence Malick (Sophisticated Films, Broad Green Pictures, IMAX, 2016). ↩︎

  5. Satisfactory (Coffee Stain Studios, 2024), published by Coffee Stain Publishing. ↩︎

You can reply to this weeknotes entry by email. I’d love to hear your thoughts!
If you like what I write, stick your email address below and subscribe. I send out my weeknotes every Sunday morning. Alternatively, subscribe to the web feed.