[20:44] <snail> morning
[20:49] <ajmitch> morning
[20:51] <ibeardslee> morning
[20:52] <snail> ibeardslee: https://secure.wikimedia.org/wikipedia/en/wiki/Halting_problem / https://secure.wikimedia.org/wikipedia/en/wiki/Church%E2%80%93Turing_thesis
[20:52] <ajmitch> been discussing cs theory on the bus? :)
[20:52] <snail> and finally http://csunplugged.org/
[20:52] <snail> ajmitch: indeed we were
[20:53] <ibeardslee> well I was trying to keep up
[20:53] <snail> the second of those urls isn't very readable
[20:53] <ibeardslee> having not done cs .. and only ever did one uni paper
[21:01] <snail> in both of those cases, I 100% guarantee that you already understand the concepts, if not the language they're expressed in.
[21:54] <snail> what's the linux command for split long command lines, to deal with errors like 'bash: /bin/grep: Argument list too long' ? I've used it before but forgotten the name
[21:56] <ajmitch> xargs?
[21:57] <mwhudson> morning
[21:57] <ajmitch> or you run things from find -exec
[22:20] <snail> ajmitch: thanks, yes, that's the program I was thinking of
[22:22] <snail> in the interim I rewrite the command as: find . -name 'log.*' -exec grep ERROR \{\} \; > all.log
[23:13] <thumper> morning