Zenburn color scheme with PuTTY

If you’ve been having trouble finding the awesome zenburn color scheme settings for PuTTY, like I was, then look no further!

Well, it’s not official or anything, and I tweaked it to suite my needs, but give it a shot. It’s working for me.

Save the following text to a file named “zenburn_putty.reg” using notepad! It’s important that you use notepad since it seems to be one of the only programs out there that saves files in the right encoding for windows registry files. Change the token “PUTTY_PROFILE_NAME” to the name of the PuTTY profile you want to apply the zenburn color scheme to.

Once you have changed the PuTTY profile name and the file is saved (using notepad!), right click the file and select “merge” from the context menu. If all went according to plan, zenburn will now be your PuTTY color scheme.

Windows Registry Editor Version 5.00



Much easier on the eyes than the default PuTTY color scheme in my opinion.

JSLint Validation with Vim

Here’s a topic that has been done over and over, but I wanted to share this method of using the popular JSLint javascript validation tool within my favourite text editor, Vim. I had tried a few methods previously that didn’t satisfy me because the interface from Vim to JSLint required the use of Vim’s make command and it was just sloppy.

My key requirements were:

  • Some form of persistent visual line differentiation on lines with error(s)
  • Error message text displayed within Vim command line when line under cursor contains error(s)
  • Error lines are navigable using Vim custom hotkey commands

The solution that finally worked for me was to use an adapted implementation of a method implemented by Honza Porkorny. The method requires use of node.js (the node executable must be on your $PATH) and Vim plugin syntastic.

Directory structure of files:


My version of the method alters


(note: location of file may be different on your system) as such:


if !executable("jsl")


if !executable("runjslint.js")

runjslint.js is an executable (via node.js) javascript file that is somewhere on your $PATH.

Then replace:

function! SyntaxCheckers_javascript_GetLocList()
  let makeprg = "jsl -nologo -nofilelisting -nosummary -nocontext -process ".shellescape(expand('%'))
  let errorformat='%W%f(%l): lint warning: %m,%-Z%p^,%W%f(%l): warning: %m,%-Z%p^,%E%f(%l): SyntaxError: %m,%-Z%p^,%-G'
  return SyntasticMake({ 'makeprg': makeprg, 'errorformat': errorformat })


function! SyntaxCheckers_javascript_GetLocList()
  let makeprg = "runjslint.js ".shellescape(expand('%'))
  let errorformat='%W%f(%l:%c): lint warning: %m,%-Z%p^,%W%f(%l:%c): warning: %m,%-Z%p^,%E%f(%l:%c): SyntaxError: %m,%-Z%p^,%-G'
  return SyntasticMake({ 'makeprg': makeprg, 'errorformat': errorformat })

The contents of the runjslint.js file I mentioned earlier are a bit involved in order to string this whole method together.

(function () {
  // Node-specific stuff
  // Notice that JSLINT is defined here as well
  var fs, sys, filename, input, errors, warning, JSLINT;

  fs = require('fs');
  sys = require('sys');

  // JSLINT object included here
  JSLINT = require('./jslint').JSLINT;

  // capture the command line argument
  filename = process.argv[2];

  // bail if no argument was specified
  if (!filename) {
    sys.puts('Usage: node runjslint.js file.js');

  // read the file specified
  input = fs.readFileSync(filename);
  input = input.toString("utf-8");

  // run jslint on the file
  JSLINT(input, {
    evil:    true,
    onevar:  true,
    undef:   true,
    devel:   true,
    browser: true,
    indent:  4

  errors = JSLINT.errors;

  // if we have errors, print them out
  if (errors.length > 0) {

    for (var i = 0; i < errors.length; i++) {
      warning = errors[i];

      if (warning) {
        // format: filename.js(3): lint warning: reason
        // e.g.: main.js(12): lint warning: Weird assignment
        var r = filename + "(" + warning.line + ":";
            r += warning.character+"):";
            r += "SyntaxError: " + warning.reason;


Now if you followed Hanzo Porkorny’s method, you’ll notice that he added similar code above to the bottom of the jslint file, which is fine, but I didn’t want to have to do too much work to refit JSLint with the runjslint.js contents every time a new version of JSLint was introduced.

Here is the only addition I made to the jslint file (at the very bottom):

// for running with node.js
exports.JSLINT = JSLINT;

This allows for the inclusion of the JSLINT object into the executable runjslint.js file. Now, when a new version of JSLint is released, I only need to replace one line of code at the very bottom of the file. Easy.

So far this method satisfies the first base requirement of mine, persistent visual line differentiation on error lines, but not the second or third. Well, syntastic does allow navigation using location list hopping, but this was not intuitive for me since the location list would always pop up and I’d have to close it again. So I rolled my own function for navigation, building off of syntastics error storage within Vim’s location list.

Unfortunately, the Google pretty print plugin does not understand Vim script syntax so the code listing is sans colour. The Vim script code is as follows (I just stuck it in my .vimrc file for now):

" navigate syntastic errors without opening the location list
nnoremap <leader>n :call GotoError(1)
nnoremap <leader>p :call GotoError(-1)

fun! GotoError(dir)
  " if current file is javascript
  if matchstr(expand('%'),'\.js$') == '.js'

    " if syntastic location list is not active, bug out!
    if !exists('b:syntastic_loclist')

    " if location list is empty
    if len(b:syntastic_loclist)  upperBound
        let b:cur_error = upperBound

    " move cursor to line AND column of error
    call cursor(loclist[b:cur_error]['lnum'], loclist[b:cur_error]['col'])

    " display error text in Vim command line
    echo loclist[b:cur_error]['text']
    echo 'Current file is not a javascript file. JSLint validation disabled.'

Now you can use whatever custom key bindings you want to bind to the function GotoError(). Just pass 1 as the argument to cycle forward through the errors and -1 to cycle backwards.

That about does it. Let me know if this post was useful to you. Would love to hear feedback… well, constructive feedback anyway.

Handling Captured Groups with JavaScript

Accessing captured groups within JavaScript can be a bit clunky:

var result = selector.match(/^((?:[~+>] )?.*?)(?: |$)(.*)$/i).slice(1);
var token = result[0];
var remainder = result[1];

I prefer to capture groups by converting them to named properties of an anonymous object. Below is an example of a function I put together as part of a CSS selection engine I am working on. Leveraging the Function object’s ‘apply’ method, it’s possible to pass the elements of the resulting captured groups array to an interim anonymous function. The arguments of said function get packaged up in an object, as named properties. Ultimately, the anonymous object is returned through to the original calling client code.

var getToken = function(selector) {
  return function(token, remainder) { 
    return {token: token, remainder: remainder};
      // (?: ) non capturing group
      // slice the first element out of the array 
      // which is the original subject string
  }.apply(null, selector.match(/^((?:[~+>] )?.*?)(?: |$)(.*)$/i).slice(1)); 

// this is a much cleaner way to get at the pertinent data:
var result = getToken('#someId .someClass > li');
console.log(result.token); // #someId
console.log(result.remainder); // .someClass > li

However, this is really only applicable in cases where you know ahead of time what your regular expression is going to be and you know how you want your captured groups named. For a more reusable solution, consider the following:

var namedGroups = function(regex, callback) {
  return function(subject) {
    return callback.apply(null, subject.match(regex).slice(1));

// usage:
var regex = /^((?:[~+>] )?.*?)(?: |$)(.*)$/i;
var getToken = namedGroups(regex, function(token, remainder) {
  return {token: token, remainder: remainder};

The beauty of this reusable method is that you can decide what you want to do with the captured groups before returning to the original client code. Anyway, let me know what you think and share your techniques with the rest of us!