I manually applied tag filters to keep task listings relevent in my previous Taskwarrior posts, but Taskwarrior provides contexts to apply filters automatically. Let's use those instead.

I found Wellington, a Sass compiler written in Go.

My macOS iTunes music library includes over 21,000 songs. Some of those tracks contain the wrong information. Wrong title, wrong album, wrong artist, wrong year.

beets and AppleScript helped me fix my incorrect track information.

Hugo defaults to filling your RSS file with the summary of every post. I prefer the full content of the most recent posts. Today I make my RSS feed reflect my preferences.

Notes on saving screenshots in OS X, so I don’t have to look it up again.

All right fine. Some visitor may want to leave a comment about one or another of my posts. I can do that with Hugo.

I spent a little time this weekend creating yearly post archives for my Hugo site.

Note to self: use the Bob Ross CSS that Thomas Park conveniently worked out.

Hey it has been a while since I shuffled the site around completely. I’ll just redo the whole thing in Hugo.

I started writing about PNWPHP but got distracted and added “Suggested Reading” to my posts instead.

I can write Jekyll posts with reStructuredText now.

I nearly wrote a script that transfers my iTunes ratings to Rhythmbox. Instead I used Edgar Salgado’s version of iTunesToRhythm.

I could use Pandoc to build HTML from my site sources.

Use site.show_drafts in templates if the local and live versions of your Jekyll site need to be different.

Jekyll currently generates the HTML for my site. I am curious about the experimental collections feature, and whether it could be useful for me.

I am slowly learning more about how to use Atom for real work. First requirement: my “real work” almost exclusively takes place on a virtual machine. Atom alone cannot handle editing those files. remote-atom to the rescue!

Octopress is “an obsessively designed toolkit for writing and deploying Jekyll blogs.” A blog post earlier this year by author Brandon Mathis described frustrations with Octopress 2, along with plans for Octopress 3. I didn’t use Octopress before, so I can’t tell you anything about how much better or worse the newest Octopress is. This release feels like a straightforward and useful extension to Jekyll. Apparently the older releases did not.

Thought I’d share TOKUHIROM’s cpan-outdated tool, which simplifies the task of keeping your installed Perl 5 modules up to date. It simply lists available updates to Perl modules you have installed. That functionality is available in the CPAN shell with the r command, but it is hard to beat the convenience of the cpan-outdated command line tool.

I don’t know about you, but I had a pleasant Saturday. It started with an hour or so of the Coursera Programming Languages videos. I learned a little bit about SML, and have been trying to remember the instructor’s caution about comparing what’s learned in class to other languages. It’s supposed to be a fresh perspective on programming.

I installed Ubuntu 14.04 on a partition of my laptop today. This is not a novelty. What is unusual is the fact that today I decided to track what I installed before I felt like I had a “Minimum Viable Linux.” Turns out there was quite a bit.

TL;DR Install Vagrant & VirtualBox. mkdir my-box && cd my-box && vagrant init brianwisti/trusty-mongo-mojo. Be aware that this is my first packaged Vagrant box, and it is probably not great.

I have been spending much of my coding time in Python recently. This site is built in Pelican. Many lines of Python have been written for work. I have even been poking at Google App Engine in what spare time is available. The only disappointment is that all of these have been in Python 2. I would prefer to be using Python 3. There is a little free time today, so I will set up a nice Python 3 workspace.

TL;DR devel_basis

TL;DR Set GREP_OPTIONS='-RI --color=auto'. Or install ack.

I have been curious about the Emacs Client for a long time. Because Emacs can have a long startup time, it can be made to run in a persistent mode. All buffers are handled by a central process. Your editor interface connects to that central process rather than managing its own buffers. Thinking about the Emacs client is what started me down the path of studying Emacs as a client/server Lisp environment. Anyways, I looked up some blog posts to tell me what to do.

TL;DR? git branch -r to list remote branches. git checkout --track -b <local-branch> <remote>/<branch> to check your branch out.

Today I got to take part in a User Experience Research interview with some fine folks from GitHub. It was straightforward. We chatted for about half an hour, mostly discussing GitHub. Makes sense. They learned how I used it. Since there is so little of GitHub that I use, they got to show me some nifty things.

The other day I talked some sort of nonsense about organizing my notes into some sort of coherent blog post. Heck with that. Life is too short. Instead I will just dump them here and hope somebody finds them useful. Maybe later I can do something with it. For now it’s just supplemental material for the official Emacs tutorial

I am trying to really learn how to use GNU Emacs. One thing that strikes me is how the Emacs user interface can be thought of as a client application to an Emacs Lisp API. This is not a revolutionary thought, but it really stuck in my head. I reread the official tutorial, focusing on the functions rather than the keybindings that invoke them.

TL;DR? C-h v org-export-backends to ensure that Markdown export is available. C-c C-e m m invokes org-md-export-to-markdown. You may need to update Org Mode, which could be a fussy process.

Ember.js is an impressive piece of work. It can also be painfully verbose. A little syntactic sugar would make that go down easier. EmberScript is CoffeeScript with fine-tuning specifically for Ember.js. Fine-tuning includes bits like replacing class and extends with Ember.class and Ember.extends.