Still not happy with psql's multiline history behavior

I'm getting grudgingly more used to CVS HEAD's behavior of stuffing a
multiline command into the history buffer as a single item, but there's
still something bothering me about it. I've finally put my finger on
what. I think it should not combine SQL text and backslash commands
into a single history entry. The example that seriously sucks is:

regression=# select foo ...
regression-# \r
Query buffer reset (cleared).
now control-P brings back:
regression=# select foo ...
\r

In the case where I type SQL and backslash on one line, of course it
can't break them apart, but I think there should be a general rule that
a line starting with a backslash is always a separate history entry.

Also, \e is seriously broken: after you edit the text and exit the
editor, the text is not reloaded into the visible display (although it
does seem to still be "behind the scenes" somewhere).

regards, tom lane