January 23

Tough going writing

Well, we aren’t all smart.

There are going to be so many jokes made at my expense for this, but I have to be honest about it. I may have impaired my ability to write for the next week. All from cutting cheese.

Jarlsberg cheese

Jarlsberg cheese (Photo credit: Wikipedia)

All right, get it out, my juvenile friends.

I was cutting the rind off a nice piece of Jarlsberg swiss today with the closest instrument of destruction – a steak knife, of course – when it slipped. Nay, was repelled by the cheese. Sliced right into the pointer finger of my left hand.

That was six hours ago. Still stings. Even worse, it’s slowing down my typing pace. And it stings.

January 7

A Scrivener API?

Scrivener (software)

For those of you that have wandered this way because of Scrivener related shenanigans (like, pumping data into a Google spreadsheet analysis a la Jamie Rubin’s scripts), thought I’d share this tidbit. Rather than speculate and hope, I wandered over to the Literature and Latte forums tonight and just straight up asked whether there was or would be an API for querying scrivener for stats. The reply can be found here (http://www.literatureandlatte.com/forum/viewtopic.php?f=4&t=30065&p=191164#p191164), but to save you a hop

There isn’t an API right now, though. This is on the roadmap, but I must stress, the long-term roadmap. :)

Also confirmed of my approaches for pulling the number of words written in a day (for that you should follow the hop) wasn’t wrong, even if it isn’t necessarily going to be right forever. Oh well, back to staring at a zero word count for the day.

EDIT: Re-read this post, clarified words my sleep deprived mind left out. Now back to that zero word count.

Category: Writing | LEAVE A COMMENT
January 2

Finally getting into markdown

So, markdown and multimarkdown aren’t exactly new. They’ve been on my radar for a few years, mostly as something I acknowledge as I pass them by and move on. In a nutshell, they’re a way of writing rich text without actually writing rich text.

Make sense?

OK, let me try that again. There are a lot of programs (and plugins) that let you bring text in in markdown or multimarkdown (multimarkdown is just an extension of markdown, adding some additional features). Whether that’s Scrivener, which lets you import markdown, or wordpress, where there are plugins for writing posts in markdown (I’m playing with one of them right now – wp-markdown; meh, it does what it says, but I’m not sure it’s the right one for me, though apparently jetpack has a plugin too), or you just want to work in a “native” markdown application (like MMDC), there are a lot of options out there.

So why do it? Because ultimately these are all just interpreting a plain text file. And that means you can write anywhere. On your phone without a rich text editor? Done. Tablet? Done. It’s only in the final publication or import step that it matters whether the target supports markdown. And what’s the result?

HTML. Formatted, but just HTML, without knowing all of the tags ahead of time. My technical friends will scoff – there isn’t much to the tagging for basic formatting, right? Except in the heat of writing, which is easier to type – an asterisk, or a set of opening and closing tags? Remember, keystrokes count in this writing game.

Ultimately, for me at least, markdown formatting is about being able to include formatting options where you want using any text editor you have handy. It’s nice if the editor supports preview of the markdown – that warm fuzzy of seeing the finished product – but  in the end, the option to edit anywhere is wonderful.

It will be interesting to see how long my infatuation with this continues :)


Category: Personal, Writing | 1 Comment