I give up on OSX’s terminal.app

Lets face it. If you rely on vim locally, vim remotely on non debian based systems, and vim remotely on Debian based systems. ESPECIALLY in an environment where you don’t get to put in your own .vimrc (such as when logged in as root, and other people log in as root as well.) You’re pretty much screwed. Now I tried all the hacks. The custom strings in preferences. I tried replacement terminals (terminator, iterm, and one or two others) And I could get things to work locally but not remotely, or remotely but not locally… So… I… Well… I gave up. I:

  • Installed X11 from my Install DVD
  • Ran X11Update2006.pkg
  • Launched X11
  • Selected Applications –> Customize Menu
  • Changed my “Terminal” command to “xterm -fa Monaco -fs 12 -bg black -fg grey -sb -sl 99999 -cr green -bc”
  • symlinked my .profile to .bashrc

And… “the dishes are done, dude” This takes care of *basically* everything.. with two minor exceptions… forward delete doesn’t work well on the command line, and pasting is somewhat awkward. but everything else… home, end, pgup, pgdn, l,r,u,d, all work everywhere I’ve tried so far. I can put up with some things to work around… as long as they are consistent things to ALWAYS work around… not things that work one way here, another over there, and differently in a third place… That bites.

And in case you’re curious… here’s my .profile (.bashrc)… without all the personal aliases…

function tranquil_thoughts_prompt
{
local WHITE="\[\033[1;37m\]"
local BRIGHTGREEN="\[\033[1;32m\]"
local GREEN="\[\033[0;32m\]"
local CYAN="\[\033[0;36m\]"
local GRAY="\[\033[0;37m\]"
local BRIGHTCYAN="\[\033[1;36m\]"
export PS1="${GRAY}.o${WHITE}O(${BRIGHTCYAN}\u${GRAY}@${BRIGHTGREEN}\H ${CYAN}\w${WHITE})${GRAY} "
}

export EDITOR="vim";
export PROMPT_COMMAND='echo -ne "\033]0;${USER}@localhost - ${PWD}\007"'
tranquil_thoughts_prompt
export PATH=/opt/local/bin:/opt/local/sbin:$PATH:$EC2_HOME/bin:~/bin

(The export PS1 line above is all one line from export to } “

Whoa, talk about neglecting your weblog! Bad Form!

I know, I know, I’ve been silent for quite some time. Well Let me assure you that I’m quite all right! Are you less worried about me now? Oh good. (Yes I’m a cynical bastage sometimes.)

So life has, as it tends to do, come at me pretty fast. I’ve left my previous employer, Ookles, and I wish them all the best in accomplishing everything that they’ve been working towards. So I’ve Joined up with the very smart, very cool guys at Automattic. I have to tell you I’m excited to be working with these guys, they’re truly a great group.

I guess that means I’m… kind of… like… obligated to keep up on my blog now, eh?  I’m also kind of, like, ehausted. Jumping feet first into large projects has a tendency to do that to a guy though.  And truth be told I would have it any other way…

😀

Cheers

DK

ruby-Mapquest

Changelog (Click Version To View/Download)

  • Version 0.005
    • Addition: thumb_height, thumb_width, thumb_style, thumb_type, thumb_url to route rval when available (per turn)
  • Version 0.004
    • Addition: apistatus to geocode rval
    • Addition: geocode status to geocode rval
    • Addition: geocode quality to geocode rval
    • Documentation: Added commas to geocoding example… oops
  • Version 0.003
    • bugfix: added apikey to overviewmap
    • bugfix: distance is now a float value
    • change: overview metrics renamed from maneuver_foo to maneuvers_foo
    • Addition: [:debugurl] for manual inspection of values returned from mapquest’s api
  • Version 0.002
    • Addition: Routing Support
  • Version 0.001
    • Initial Release

Warranty: None, at all, whatsoever, use at your own risk, may burn down your house and knock over your garbage cans and return the car with the gas level on “E” and refuse to return your lawnmower even though it’s now 7 months later and you’re growing a small rainforest out back… might fall asleep while watching your children, forget to pay the electric bill, and run up massive credit card debt. In other words. You’re on your own. Dont come crying to me!

To use this client you have to first apply for a mapquest openapi key here Then you must add “*” as a referrer under “my account” for your openapi ke

Example usage:

mq = Mapquest.new(“foobazbazbooblah”)

#Geocoding
myLocation = {
:address => “555 17th Street, Suite 1600”,
:city => “Denver”,
:state => “Colorado”,
:zip => 80202,
}
puts mq.geocode(myLocation).inspect

#Routing
route_request = {
:addressOrigin => {
:name => “Yahoo!”,
:address => “701 First Avenue”,
:city => “Sunnyvale”,
:stateProvince => “ca”,
},
:addressDestination => {
:name => “Google”,
:address => “1600 Amphitheatre Parkway”,
:city => ” Mountain View”,
:stateProvince => “ca”,
},
}
puts mq.route(route_request).inspect

As simple as it gets, no? Cheers!

Tag anything, anywhere?

I’ve not been able to find anything really high profile (good google page rank) but is there an API which allows you to tag *anything* anywhere? (not just URLS, but… any piece of data?) Being able to take one arbitrary identifier, optionally a type, and add arbitrary tags to it sounds like the stuff of web 2.0, yea? but seems people are just home-brewing their own. Now if I were able to go somewhere and /tags/people/demitrious or /tags/blogs/demitrious or /tags/*/demitrious or /tags/urls/apokalyptik.com /tags/foo/bar then we’d be getting somewhere

The quest for clean data

When you’re on the leading edge of things you always have a problem: dirty data. And the quest for clean data is always at the forefront of your mind. Last night while searching for a geocoding service which didn’t suck outside the US and major EU countries I cane upon this article which put into words the stormy mood that had been brewing whilst I struggled in my quest: Geocoding, Data Quality and ETL. I know geocoding is outside my normal sphere of writings, but the way technology is going some of you are going to eventually have to work with geocoding at some point.

And the bottom line is this: While we now have the tools and techniques necessary for getting the job done right, It’s going to be a long time until we actually get it right. It’s just one of those things that takes a lot of time, money, and manpower to accomplish.

That being said… I wonder how difficult it would be to mashup, say, Google Earth and current cartographic services to specifically draw attention to problem areas, and to setup as an automatic alert for new expansion (or demolition for that matter?!) Not being my area of expertise I’d be hard pressed to get that right, at least without some insider help anyhow. But I’d be willing to bet that it would prove a valuable tool for the geospacial community. And make no mistake about it: the better they are at doing what they do the easier it is for you to find the newest starbucks.