Change History

However, what the ghci tickets are trying to achieve is that the user enters a single line of text, ghci notices via layout rules that the line is incomplete, and continues it in a multi-line input. If you used getInputLine followed by getMultiLine, the first row would be repeated, which is probably not the best UI. So getInputLine and getMultiLine would have to interact, and I'm not sure how that could work without making things much more complicated.

This would help with an issue with GHC #4316 in that we might want to merge the strings into one history entry. That also introduces the issue of haskeline presenting multiline commands (those containing "\n") from the history.