<purr\ec>
System/Master d3b7c6b elliottcable: (- fix tmux) Moving the status-line setting back into the main conf
<ELLIOTTCABLE>
kaplan: 'sup
<kaplan>
ELLIOTTCABLE, finally caught you
<ELLIOTTCABLE>
kaplan: good idea to tweet at me if you want my attention
<kaplan>
ELLIOTTCABLE, ok, I'll remember that
<kaplan>
ELLIOTTCABLE, the book arrived
<ELLIOTTCABLE>
I'm basically ignoring IRC notifications, right now, because it's impossible to stop this fucker from pummling me with SASL / nickserv notifications every hour of every day of every week of every month of every year ಠ_ಠ
<ELLIOTTCABLE>
kaplan: yes! :D
<kaplan>
ELLIOTTCABLE, so, what now?
<ELLIOTTCABLE>
what now about what?
<ELLIOTTCABLE>
sorry, really busy.
<kaplan>
ELLIOTTCABLE, I read it and it seems complicated
<ELLIOTTCABLE>
the dragon? sure is. worth it, though.
<kaplan>
ELLIOTTCABLE, how to actually use that information to start writing something?
<ELLIOTTCABLE>
er, that's not how a course works. You start reading, and working through the exercises, and work your way through it. :P
<kaplan>
ok
<kaplan>
I'll ask you when I get stuck
<ELLIOTTCABLE>
It may not be directly related to writing Something In Particular, but it will aid you overall. You won't get much of anywhere on some projects, until you've learned the material in that book (=
<ELLIOTTCABLE>
that doesn't mean you have to *start* with it.
<ELLIOTTCABLE>
Like I said: write a Scheme interpreter. Then, perhaps, take a break from actually implementing things, and start on that book.
<kaplan>
hmmn
<ELLIOTTCABLE>
sorry if I'm short; very busy. researching flights, and I'm really sick on top of that.
<kaplan>
Understandable
gozala has joined #elliottcable
<Cheery>
I'm wondering about the constraints in editing structured files
<Cheery>
the basic editing commands are defined slot-wise
<Cheery>
join causes |x|y| -> |xy|
<Cheery>
split causes: |xy| -> |x|y|
<Cheery>
collapse causes |x|y|z| -> |_|
<Cheery>
and put is inverse of collapse, inserting stuff given to it, into the file
<Cheery>
I defined them like this, because I want my operations to do things that are clear on intent.
<Cheery>
but in complex constructs defined by context free grammar, these editing operations nearly always rip the construct open
<Cheery>
considering to limit the 'damage' caused by these commands, by always allowing extensible fields to contain a trash field.
ELLIOTTCABLE has quit [Disconnected by services]
gq has quit [Ping timeout: 246 seconds]
ELLIOTTCABLE_ has joined #elliottcable
ELLIOTTCABLE_ is now known as ELLIOTTCABLE
eligrey has joined #elliottcable
<joelteon>
ugh
<joelteon>
I hate asking questions in #python
<joelteon>
it's so shit
<Cheery>
what's your question?
<joelteon>
how to disable linking with the Carbon framework while building 2.7
eligrey has quit [Read error: Connection reset by peer]