Add code blocks as a single history entry.

This has the awesome side effect of hoisting commands used inside code block declarations so that the code block can be replayed more effectively.
We shouldn’t clear history, since we’re starting a new history file.
Revert "Add code blocks as a single history entry."

We'll bring it back, because it's a good idea, but the current
implementation doesn't play nice with codecleaners... We're a bit at
odds because we need to add the raw code block to the history, but
execute the cleaned code block.

This reverts commit e6bd6b306f5e6c86725b9084c61baaa0120a1a15.
Add code blocks as a single history entry.

This has the awesome side effect of hoisting commands used inside code block declarations so that the code block can be replayed more effectively.

This way done right :P

(Effectively re-reverting 535444c)
Revert "We shouldn’t clear history, since we’re starting a new history file."

Yeah. That was a brain fart. We absolutely should.

This reverts commit 939eec2127dd22534ccabc81d9411ad870176c4e.
Clear readline history before loading it.

Otherwise, things get all sorts of crazy.

Fixes #28

Problem: PHP 5.5.7 segfaults when clearing readline history. So basically you can choose between an exponentially expanding readline history and a version of PHP that actually runs. Hopefully this gets sorted soon :(
support histsize & erasedups (closes gh-29), pure php implementation of libedit::readline_list_history
fixed bad copy&paste in docstring
properly handle comments& line seps in Libedit::listHistory().
new test tool for String::unvis, PSR1/2 validation