[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#21147: readline history is stifled early so (readline-set! history-l
From: |
Daniel Llorens |
Subject: |
bug#21147: readline history is stifled early so (readline-set! history-length nn) has no effect |
Date: |
Tue, 28 Jul 2015 10:06:06 +0200 |
The default history-length is 200. When one imports (ice-9 readline), history
is stifled to this value, so it doesn't matter if you set history-length to a
larger value later on. I'm surprised that this has gone unnoticed up to now,
since 200 is really small. I may be missing something...
The patch changes scm_readline_options() so that history is only stiffled when
the options are actually set. This is rather clumsy since it means that if one
doesn't set the options, history will never be stifled.
An alternative would be to add an optional readline-options argument to
activate-readline. That way one would be able to increase history-length before
the first time history is stifled, and otherwise things would work as they do
now.
Regards
Daniel
0001-Avoid-stifling-readline-history-when-looking-up-opti.patch
Description: Binary data
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#21147: readline history is stifled early so (readline-set! history-length nn) has no effect,
Daniel Llorens <=