#72 non-existant history stalls w3juke

[Chris P. Ross]

When w3juke starts up, it looks for various things,
including the user's history file. If there is no
history file, it calls bad_bad_bad(404), but somehow
that ppipe still gets into a set of ppipe's that gtk
knows to look for input on. It eventually stalls in a
select call deep within gtk+ selcting on some fd's, the
one that would've otherwise been the history file being
fd -1.

Easy to reproduce (by deleting or moving your history
file), but I don't know as much about how all the ppipe
stuff works, and gets handed to gtk, as Josh does. So,
I'll punt to him...