GNU bug report logs - #21147
readline history is stifled early so (readline-set! history-length nn) has no effect

Previous Next

Full log

View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Daniel Llorens <daniel.llorens <at> bluewin.ch>
Subject: bug#21147: closed (Re: bug#21147: readline history is stifled
 early so (readline-set! history-length nn) has no effect)
Date: Fri, 24 Jun 2016 08:24:02 +0000

[Message part 1 (text/plain, inline)]

Your bug report

#21147: readline history is stifled early so (readline-set! history-length nn) has no effect

which was filed against the guile package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to 21147 <at> debbugs.gnu.org.

-- 
21147: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21147
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems

[Message part 2 (message/rfc822, inline)]

From: Andy Wingo <wingo <at> pobox.com>
To: 21147-done <at> debbugs.gnu.org
Subject: Re: bug#21147: readline history is stifled early so (readline-set!
 history-length nn) has no effect
Date: Fri, 24 Jun 2016 10:23:36 +0200

thanks

[Message part 3 (message/rfc822, inline)]

From: Daniel Llorens <daniel.llorens <at> bluewin.ch>
To: bug-guile <at> gnu.org
Subject: readline history is stifled early so (readline-set! history-length
 nn) has no effect
Date: Tue, 28 Jul 2015 10:06:06 +0200

[Message part 4 (text/plain, inline)]

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 (application/octet-stream, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.