Re: [clisp-list] command-oriented-history with readline in CLISP

[Peter W. <pet...@wo...>]

On Wed, Jun 27, 2001 at 03:23:12PM -0400, Sam Steingold wrote:
> bash has a variable, command_oriented_history, which controls whether
 ...<3 bash lines cut>
> is saved in history as one line or 3.
> CLISP always saved 3 lines, which was bad.
> now it will save one line.
> the question is: do we need a similar backwards-compatibility option?

It's a _big_ improvement to have the history saved as 1 line. Thanks.
I personally don't need the backwards-compatibility option.  Does
paren matching work after pressing return?

Peter