Kyle Isom kisom

This is my workflow for automatically building and testing Go code. It uses steeloverseer to watch for changes to the tree and run the standard Go tools (vet, build, test) on the package as well as golint on any changed files.

Install steeloverseer with

cabal install steeloverseer &amp;&amp; cp ~/.cabal/bin/sos ~/bin

	(This post is a Literate Haskell file that was run through pandoc to
	produce markdown).

	It seems customary in the Haskell space to write an introduction to
	monads; my attempt in this exposition is not to outdo anyone else, but
	to make the topic clear enough that I can write about it. My hope is
	that by doing so, it becomes more clear to me.

	> module Perhaps where

	Purity is a useful construct that forces programmers to consider that the
	environment that they are operating in is unclean, and this introduces
	barriers to formally defining the behaviour of the system comprising
	the program and its environment.

	This file is a [literate Haskell
	file](https://gist.github.com/kisom/3863f17636d99b4f8401) run through
	[pandoc](http://johnmacfarlane.net/pandoc/) to produce a Markdown
	post. There might be a few glitches as I'm still developing a workflow
	in this style.

	(defun count-macroexpansions (form)
	(labels ((count-expansions (form n)
	(multiple-value-bind
	(expansion expanded)
	(macroexpand-1 form)
	(if expanded
	(count-expansions expansion (+ n 1))
	n))))
	(count-expansions form 0)))

	#!/bin/sh
	# convert Nikon NEF RAW images to FITS.
	#
	# depends on dcraw and imagemagick:
	# apt-get install dcraw imagemagick

	IMAGE_LIST="$1"

	if [ -z "$IMAGE_LIST" ]
	then

	;; --lisp--

	;; Load swank.
	;; prefix-key ; swank will kick this off
	(ql:quickload :swank)
	(ql:quickload :manifest)

	(defvar manifest-url
	(manifest:start))

	> import Control.Applicative

	This post is a [literate
	Haskell](https://gist.github.com/kisom/09e471e145bf1eca9124) file,
	converted to org-mode with [Pandoc](http://pandoc.org).

	Time to explore the `Applicative` type.

	First, `fmap`:

	Written as a demo of how a shell would implement this, and why it needs
	to be a shell builtin.

	This won't actually work as a standalone program; chdir(3) only changes
	the directory of the current process. As soon as the program exits, it
	returns control to the parent process (the shell). If this is executed
	as a shell builtin, the shell process's working directory is changed.

	~/code/perl
	(0) <tessier:kyle> $ perl scan-elvi.pl
	w3link doesn't match.
	l1sp doesn't match.
	w3rdf doesn't match.
	w3html doesn't match.
	worldwidescience doesn't match.
	searx doesn't match.
	w3css doesn't match.
	f5 doesn't match.