[00:12] <snap-l> btw: OMC is on http://metalinjection.fm
[00:28] <jrwren> ugh, I think the old baracuda 7200.11 is failing :(
[00:52] <jcastro__> rick_h_, hey
[00:54] <greg-g> rick_h_: before you respond to jcastro__ , please build me one of these: http://i.imgur.com/OCxwL.gif
[01:40] <rick_h_> jcastro_: what's up?
[01:40] <rick_h_> greg-g: hah! There is a metal working subgroup of my woodworking group
[02:04] <jjesse-home> evening
[02:04] <jjesse-home> hey jcastro__
[12:14] <rick_h_> TGIF!
[13:13] <brousch> rick_h_: Rough week?
[13:15] <brousch> First call of the morning: Help! My printer's not working!
[13:15] <brousch> Solution: Push the power button to turn it on
[13:17] <rick_h_> lol
[13:17] <rick_h_> good answer
[13:17] <rick_h_> supposed to be the last day working on this private projects feature on LP so yea
[13:17] <rick_h_> been rough week closing out the last issues
[13:17] <rick_h_> and feeling sick today. THink my wife gave me her bug
[13:19] <brousch> You keep getting infected via contact from this person. Perhaps you should avoid her.
[13:19] <rick_h_> yea, keep thinking of that
[13:19] <rick_h_> then she makes a pie and I'm suckered back in
[13:19] <brousch> mmmmm, pie
[13:54] <snap-l> Good morning
[14:27] <dzho> don't be so sure
[14:37] <jjesse> morning snap-l
[14:41] <jjesse> wow said good morning to snap-l  and got kicked
[14:41] <jjesse> apparently freenode doesn't think its a good morning
[15:18] <dzho> kicked?  messages I saw called it a quit
[16:12] <snap-l> Heh
[16:16] <jjesse> all of my channels dropped after saying good morning :)
[16:16] <snap-l> Maybe it's not a good morning after all? :)
[16:32] <snap-l> http://theoatmeal.com/comics/spines_speech
[17:08] <greg-g> I didn't expect I needed to start drinking so early today.
[17:08] <greg-g> btw, g'morning
[17:10] <snap-l> Nobody expects the porta-bar
[17:11] <snap-l> But nobody can find the porta-john
[17:26] <snap-l> http://www.bbc.co.uk/news/technology-20554441
[17:26] <snap-l> I hope you all sold your ZYnga stock
[17:42] <greg-g> newb question: was does "{}" mean in bash (without the quotes)
[17:43] <snap-l> http://stackoverflow.com/questions/2188199/bash-double-or-single-bracket-parentheses-curly-braces
[17:44] <greg-g> so, in this case:
[17:44] <greg-g> find -type l -exec git annex reinject ~/mail.old/archive/{} {} \;
[17:45] <snap-l> find's {} is different
[17:45] <greg-g> ah, well then
[17:45] <snap-l> that means take the result and put it in as a vairable
[17:45] <rick_h_> it's magic!
[17:45] <snap-l> er, not variable, vur rather put it in the results
[17:46]  * greg-g nods
[17:46] <greg-g> thanks snap-l
[17:46] <snap-l> np
[17:46] <greg-g> that's what I thought/assumed, but I rarely run one-liners I don't understand fully
[17:46] <snap-l> greg-g: You'll never be a Ruby develoepr, then. ;)
[17:46] <greg-g> haha, glad to hear it
[17:51] <greg-g> hmm, that find gives file names like "./something" the dot is confusing the git-annex reinject command....
[17:52] <greg-g> http://paste.mitechie.com/show/845/
[17:54] <snap-l> Give it a directory. I think that'll clear that up
[17:54] <snap-l> find . -type ...
[17:54] <greg-g> same :/
[17:54] <snap-l> er, rather /home/greg/
[17:54] <greg-g> ah
[17:56] <snap-l> Otherwise it defaults to ./
[17:59] <rick_h_> I will not commit murder over code...I will not commit murder over code...
[18:00] <snap-l> rick_h_: I'm not sure that's a mantra you'll stick to
[18:00]  * snap-l votes rick_h_ most likely to cause bodily harm over a commit message
[18:02] <greg-g> I can't get rid of that dot :/
[18:02] <snap-l> That's strange
[18:03] <snap-l> are you using a dot anywhere in there/
[18:03] <snap-l> ?
[18:03] <rick_h_> greg-g: http://blog.ergatides.com/2012/01/13/relative-path-to-absolute-path-in-a-bash-shell/
[18:03] <rick_h_> try that
[18:03] <rick_h_> make sure to get that -n flag in there
[18:04] <rick_h_> http://wiredrevolution.com/bash-programming/convert-a-relative-path-to-absolute-path-in-bash says to use realpath in ubuntu/debian distros
[18:10] <greg-g> so, my issue was that I didn't trust that a filename like:
[18:11] <greg-g> /home/greg/Dropbox/./Something/else.txt would work
[18:11] <greg-g> the /./ in the middle, uh, was interpreted "correctly" in that the file at /home/greg/Dropbox/Something/else.txt was used
[18:11] <rick_h_> ah cool
[18:11] <rick_h_> yea
[18:21] <greg-g> crazy unix
[18:26] <rick_h_> dammit, wtf is with Java devs not happy until each variable and method name can be nearly a complete sentence?
[18:27] <snap-l> LordKnowsWhyButIAssumeItIsBecauseJavaIsVerboseFactory
[18:30] <snap-l> http://arstechnica.com/tech-policy/2012/11/666-chip-why-a-texas-student-thinks-her-school-id-is-the-mark-of-the-beast/ <- and this is why I subscribe to Ars
[18:34] <Blazeix> rick_h_: i'm dealing with some java code that's generated from a COBOL module right now.
[18:35] <Blazeix> every single class name is like 50 characters wrong
[18:35] <Blazeix> er, s/wrong/long/
[18:36] <rick_h_> Blazeix: my sympothies. I've got JS code written by a Java dev turned Python dev and taking all will power not to hit the nuke button
[18:37] <Blazeix> sad times
[18:37] <rick_h_> yea, especially because this is supposed to be done EOD :/
[18:38] <brousch> If you'd use a proper IDE that autocompletes for you it wouldn't be such a problem
[18:38] <rick_h_> then I'd have two problems :P
[18:40] <brousch> Let me help you set up PyDev
[18:41]  * rick_h_ runs away
[18:44] <brousch> You've done so much to help me use vim. I must return the favor
[18:44] <greg-g> such a nice guy you are
[18:45] <brousch> Talking like Yoda are we?
[21:24] <brousch> I have a fork of something on github and want to bring it up to speed with the current version. How do I do that?
[21:29] <brousch> I think I got it http://share.ez.no/blogs/virgil-ciobanu/how-to-syncronize-your-github-fork-with-original-repository
[23:05] <jrwren> how can i use pyvenv-3.3 and have it install pip by default?
[23:05] <jrwren> i think answer is use virtualenv not venv.
[23:53] <brousch> jrwren: python3.3?
[23:53] <jrwren> y
[23:53] <jrwren> django-admin.py in my virtualenv says ImportError: no module named django
[23:55] <jrwren> i wanted to play with 3.3 and django 1.5
[23:55] <jrwren> i'm not aware enough to do so.
[23:55] <jrwren> going back to 2.7 and 1.4
[23:56] <brousch> 1.5 supports python3, but are you sure 3.3?
[23:56] <brousch> I would assume 3.2
[23:56] <jrwren> shouldn't matter much
[23:56] <jrwren> 3.3 shouldn't break anything from 3.2