‘From Raw to Cooked to Sushi’

In iA Writer 5: From Raw to Cooked to Sushi – iA:

In every design iteration, our individual versions evolved from the raw, to the complex, to the simple. Overall, we have reached a point where our adventure now leads, not back to a raw app, not onward to a more complex app, but upwards to a simpler app.

An interesting look and preview of what’s to come in iA Writer. Especially the hint that a Windows version might be in the works is interesting.

but we are now more than ever focused on offering iA Writer on different platforms.

Check the post for more info.

I think PDF-view was about the final piece missing for solving my note-taking issue and building a Dropbox/Folder-based plain-text notes-app with Atom.io. Now I just have to get some automation to work.

Caret – A Markdown Editor

I was looking for a Markdown editor on Windows and found with ‘Caret’ a great cross-platform solution

Even though I have been getting more and more accustomed using WYSIWYG editors for writing and blogging1 over the course of the last few months, I somehow have missed my precious plain-text-workflows. Every now and then, like just-for-the-old-times-sake did some work on a plain-text file. Not sure why, but I missed it.
Continue reading

Setting up Atom.io as my Markdown Editor

I recently had to admit to myself that too many options are not good for the way I work. Once I have the chance to fiddle, I will do so and eventually not get much done. This happened when I realized that, even though I very much enjoy Ulysses.app, it ultimately doesn’t work well for me simply for the reason that I tend to tinker with themes and fonts and eventually not get much done. Hence I switched back to WriterPro, which allows to literally no customization.

Even though I was happy with it, I had the issue coming up that I needed to have a text-editor available on the computer at work. I have my own user account on the machine but I have no intention to sign in with my iCloud credentials into a machine which is also used by other users only to have access to Writer Pro, and with it my files1. I had to come up with a solution.

This led yet another time to a search for a nice editor that suits my needs. I (re-)tried a few which I knew, yet all either disappointed or simply where not what I was looking for. Since I at some point in the past have tried to set up Sublime for writing, it dawned me that I could look into how Atom.io would hold up. I have been using Atom.io for a couple of weeks to edit the code of this blog and it feels more user-friendly to me. Since you read this, you can guess that it didn’t took long before it was clear that I had a winner. It even swayed me over to use it a my go-to-editor on all my machines.

I was sure that somewhere someone must have done the same and eventually found a very useful introduction into how to Atom.io for Markdown Editing2 on a Microsoft blog.

One of the interesting things from the post:

If you’re working in a folder that contains a lot of Markdown files, don’t even try using the tree view. It’s 100x easier to use ctrl-t3 and then start typing the file name you want to open. This will search through the directory structure for files that match the text you’ve entered, and you can then click the one you want.

Perfect, just what I like.

Recommended Packages

In the aforementioned article are already a few nice packages listed for turning Atom.io into a really nice Markdown editor. But there are few more and for my purposes and needs I installed the following packages:

  • Markdown Writer
    Really excellent package and the heart of this setup. It does everything that I need. The only issue I had, was that Italics used the underscore and not the * asterisk which I prefer. Luckily this was easily adjusted in the Markdown-Writer Package ‘markdown-writer -> style-text.coffee line 8’ change the underscore to asteriks (even though I am on the brink of changing my mind on that matter).
  • Zen
    This is how I get the focused and clean editor that I am looking for. The options allow for some and customization which are helpful, such as activating showing wordcount (follows) and showing or hiding TABS.

  • Wordcount
    For word and character count, obviously.

  • Marked
    Well, preview with Marked. Of course this is Mac only.

  • Markdown Table Formatter
    This ones does the obvious and nicely formats Markdown tables. I surely don’t need this a lot, but it will come in handy from to time. This feature is already included in Markdown Writer but this script seems to work better for my liking.


Even though I enjoy all kinds of automation, I suck at actually doing the automation. Scripts are great when, well, you know how to script I guess. Something that I still have to learn.

One thing that I generally like to improve is my file naming. Of course I have a file-naming-system, I’m not an animal, but I’m not always good at actually sticking to it. The Markdown Writer package though takes the pain away from me. After setting up folders in the Markdown Writer package for Drafts and Posts everything just falls naturally into place.

Drafts are, as one would guess, automatically stored in the Drafts folder and once I am ready to publish (or already have done so) I invoke the Publish Draft command via CMD+SHIFT+P and the draft gets moved into the Post folder and renamed according to what I have specified. Just, what I always wanted. Bliss!


The amount of available themes both for the editor and the syntax is staggering and there surely is something for everyone. I have been trying a few, if not too many, only to realize that I prefer the included ones the most. The classic Solarized (both dark and light) and both One Dark and One Light are rather nice on the eye. One that I found to be rather well working for me is the Sepia Syntax theme, though I mostly use the Solarized themes.

Another very interesting one is the Pen, Paper, Coffee syntax theme which is specifically designed for text. It even supports Critic Markup, a markup language that I though, not take much advantage of.


Once pieces fell into it’s places and I started to get more familiar with the app and new workflows it has become very quickly a pleasant and very powerful app to work with. One that I look forward to spend a lot more time with.

Sure, figuring all this out, took some time, but in the process I also wrote this post and doing so learned a lot of new things. I sincerely hope that now, that I finally puzzled together the Markdown editor that I always wanted, that is not only Open Source but also Cross Platform, I will finally settle and stop this honestly very annoying switching.

In the meanwhile I have set the editor up with these packages on a few machines and it takes only a few minutes and it’s done. The only slightly annoying thing that I have encountered is that Finder Services and with it Brett’s Markdown Services don’t seem to work all the time. Also in an interesting side-note Folding Text is currently developed for Atom.io as well which is interesting as well. I haven’t looked into that though yet.

And yes, the font that I am using is of course Office Code Pro, which makes of course for an extra nice experience.

  1. As a matter of fact, the Mac still runs Maverick, so it wouldn’t work anyway 
  2. Considered that I haven’t been too familiar with the app I learned everything I need to feel comfortable using it from this post. 
  3. In fact it is CMD+t on the Mac 

My new favourite Writing Font

I have more than once been writing (not calling it whining for that matter) here about my weird obsession with the Nitti Font used by WriterPro and iA Writer. All attempts of getting used to another font more or less failed. Since moving all my typing over to Ulysses a void needed to be filled.

I was rather contempt with using Menlo since switching to Ulysses, yet every time I opened a file in WriterPro I was reminded how much I appreciated Nitti Light. Every now and then I considered purchasing it but the price-tag for all the weights I was interested somehow ticked me off. I’m not sure do I like the font that much.

I think I might have found the solution to this issue when I the other day learned about Office Code Pro, which is a modified version of Adobe’s SourceCodePro. I am familiar with Source Code Pro but always found the font a bit too technical for the lack of a better word. Turns out that I prefer Office Code Pro over SourceCodePro, even though I am not able to explain the difference between. It seems narrower and some of the characters have been modified. Overall the adjustments seem to make it a bit more Nitti-like. Which is a good thing.

Either way, it does, as does its origin Source Code Pro lack an italic version, which is somewhat of a bummer. Other than that, I really like the clean and crisp look of it. In fact even more so than Nitti Light. It is easily readable even in rather small sizes1 and it is even more beautiful with a dark theme. At times Nitti started to feel bit of grungy on the desktop and somehow didn’t really look sharp.

Since I was already at trying fonts again I started to fiddle around with a few more. I tried Fira Mono, Input and eventually Cousine, which I used to use a lot a few years ago.
I like all of them and all of them have something about them that I like, but overall I enjoyed Office Code Pro the most. It is the cleanest, feels light, is very easily readable in all sizes and looks good in both dark and light themes. Sounds almost too good.

The Test

Since I might have found a font that I like I thought the best test would be to stick with the font for a while and see if it sticks.

The plan, or challenge is to stick with Office Code Pro until the end of May and not try or switch to any other font. I actually went so far to remove all other custom monospaced fonts from my system to avoid the temptation. Also for the sake of a consistent experience, I installed the font in my editors on iOS (yeah Ulysses/Daedalus). This is in fact is a nice added feature in both apps.

At the end of May I will let you know, how the challenge worked out and if doesn’t feel right by then I will give another font a try. But not before June the 1st of course.

If you are intetested in the font as well, you can find it here on Github.

Note: I have no knowledge about typography whatsoever other than that I prefer some fonts over others just based on aestestics and personal preferences.

  1. I usually prefer not too small sizes, but still with this font it almost makes sense 

© 2017 Sven's.Blog

Theme by Anders NorénUp ↑