Failure to do this can cause screen corruption like:
<headerline> [X] filename.cc <several blank lines> <output from previous iteration of split that happened to be here>
I believe this might only happen in some terminals, and maybe only when using
the "alternate screen". Regardless of the exact conditions to reproduce, it
should be safe to always clear it when starting up and is probably the correct
thing to do anyway :)
I assume this patch was based on some local commit that we don't have in core (and don't want in core :)). Can you rebase it to @ and update?