Re: request for hack: readline fixes

[Neil Jerram]

Neil Jerram <address@hidden> writes:

> Subject: [PATCH] Expression-oriented readline history

A couple more thoughts occurred to me.

1. I should add a `sans-surrounding-whitespace' call to that code (when
appending to the history buffer).

2. An interesting different approach would be not to do the add-history
here (i.e. in make-readline-port) at all, but instead in
readline-repl-reader, by writing the expression that was read into a
string, and adding that string with add-history.  That would give a less
verbatim kind of history, e.g. (I guess) "'a" would appear in the
history as "(quote a)".  But it would cope better with multiple
expressions being entered at the same readline prompt.

(With the posted patch, if the lines of input were

(1
2) (3
4)

I think there would be one line added to the history:

(1 2) (3 4)

)

Perhaps we could provide both approaches, with a switch to choose
between them?  (Or even all three, if we wanted to keep the current
behaviour too.)

         Neil