Sean Fern gsf

ed

rlwrap -c ed (and remember to set blink-matching-paren off in .inputrc)

For indenting lines 9 to EOF (note that 2 spaces follow the last slash): 9,$v/^$/s/^/

Manual for the GNU ed: http://www.gnu.org/software/ed/manual/ed_manual.html

The Definitive Guide (POSIX): http://pubs.opengroup.org/onlinepubs/009604599/utilities/ed.html

With etagres and streaming:

$ nab http://localhost:1041/about
REQ NUM: 100 RTN NUM: 100 QPS: 33 BODY TRAF: 517KB per second
REQ NUM: 300 RTN NUM: 290 QPS: 48 BODY TRAF: 750KB per second
$ ps aux | grep node                                                                          
gsf       8938 25.2  2.6 757788 104256 pts/8   Sl+  12:52   0:07 node server.js
$ node-tick-processor
...
   ticks parent  name

Dev script that does the following:

Restarts the server on changes (a la node-dev)
Bundles up browserify
Restarts and re-bundles on template changes
Compiles lesscss files
Reload browser on any change

[Originally posted in a comment at http://www.westphillylocal.com/2013/10/11/a-woman-critically-injured-in-hit-and-run-accident-near-38th-and-spruce/.]

I'm not kidding. Road-level trolley tracks and cyclists simply do not mix. I've been in accidents due to tracks in Philadelphia and San Francisco -- the two cities I've lived in with tracks in the streets. Nearly every cyclist I know in Philadelphia has been in at least one minor accident involving tracks, and several have real horror stories. A friend broke several bones in her face due to a slip on the tracks just weeks ago.

But you're right. I may be overestimating in my "thousands of injuries" claim. Unfortunately, we don't have solid data around this issue to reason from. No one keeps track of the number of bicycle accidents caused by trolley tracks, and cycling accidents in general are sorely under-reported. According to the 2012 PennDot Crash Facts & Statistics [1], there were 1,369 total bicycle accidents in Pennsylvania. Considering the estimated 36

	$ ps aux \| grep Iptab
	root 2487 0.0 0.0 1216 32 ? S 17:17 0:00 /boot/.IptabLes
	root 2489 0.0 0.0 50368 252 ? Sl 17:17 0:00 /boot/.IptabLes
	root 2493 0.0 0.0 852 32 ? S 17:17 0:00 /boot/.IptabLex
	root 4013 0.0 0.0 9040 188 ? Sl 18:04 0:00 /boot/.IptabLex
	root 4209 163 0.0 50952 604 ? Sl 18:19 0:01 /boot/.IptabLes
	gsf 4215 0.0 0.0 3428 772 pts/5 R+ 18:19 0:00 grep --color=auto Iptab
	$ ps aux \| grep Iptab
	root 2487 0.0 0.0 1216 32 ? S 17:17 0:00 /boot/.IptabLes
	root 2489 0.0 0.0 50368 256 ? Sl 17:17 0:00 /boot/.IptabLes

	#!/bin/sh
	# Attempt command, printing all output to stdout, catching errors
	# based on a regex, erroring out on all other errors
	if output=`some-command 2>&1`
	then
	echo "$output"
	else
	if echo "$output" \| grep 'regex string'
	then
	something --other --than bailing

	// ...

	/**
	* Updates UserEvents that are in the past and if the selection strategy of
	* first is used will update, but not mark as incomplete, encounters that are
	* ongoing. This method does not normally need to be modified.
	*/
	protected function updateUserEvents()
	{
	//$this->updateExpiredUserEvents();

	matchbox-window-manager -use_titlebar no &
	exec xterm