using guile's readline module

using guile's readline module

[Gene Pavlovsky]

Hi

When I use guile's readline module (guile 1.6.7), I can't set bounce-parens option:
guile> (readline-options 'full)
bounce-parens	500	Time (ms) to show matching opening parenthesis (0 = off).
history-length	200	History length.
history-file	yes	Use history file.
guile> (readline-disable 'history-file)
(bounce-parens 500 history-length 200)
guile> (readline-enable 'history-file)
(bounce-parens 500 history-length 200 history-file)
guile> (readline-set! 'bounce-parens 50)
<unnamed port>: In expression (readline-options-interface (append # #)):
<unnamed port>: Unbound variable: readline-options-interface
ABORT: (unbound-variable)

Maybe I'm doing it wrong, but I think that I follow the manual.

The second issue is that when I type something, during the time when the matching paren is highlighted (and that is 500 ms by default), 
guile doesn't accept any input, so every time I close a paren, I get to wait 500 ms to type more. Both gauche and csi with readline
modules installed don't hang like this, so I think it's a guile-specific bug.

Hope this will be fixed :).

Best regards,
Gene.

-- 
The human knowledge belongs to the world


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: using guile's readline module

[Neil Jerram]

Gene Pavlovsky <heilong@bluebottle.com> writes:

> guile> (readline-set! 'bounce-parens 50)
> <unnamed port>: In expression (readline-options-interface (append # #)):
> <unnamed port>: Unbound variable: readline-options-interface
> ABORT: (unbound-variable)

Does it work if you omit the quote?  In other words, like this:

(readline-set! bounce-parens 50)

(For some reason, possibly analogy with set!, the xxx-enable and
xxx-disable procedures of the options interface take a quoted option
name, but xxx-set! takes its option name unquoted.)

> Maybe I'm doing it wrong, but I think that I follow the manual.

The manual has examples which show this, but it isn't explicit on the
point.

> The second issue is that when I type something, during the time when
> the matching paren is highlighted (and that is 500 ms by default),
> guile doesn't accept any input, so every time I close a paren, I get
> to wait 500 ms to type more. Both gauche and csi with readline
> modules installed don't hang like this, so I think it's a
> guile-specific bug.

I probably can't help here, but what OS and Guile version are you
using?

        Neil



_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: using guile's readline module

[Gene Pavlovsky]

guile> (readline-set! bounce-parens 50)
<unnamed port>: In expression (readline-options-interface (append # #)):
<unnamed port>: Unbound variable: readline-options-interface
ABORT: (unbound-variable)

Type "(backtrace)" to get more information or "(debug)" to enter the debugger.


I'm using guile 1.6.7 on gentoo linux (kernel 2.6.12), readline 5.0

Neil Jerram wrote:
> Gene Pavlovsky <heilong@bluebottle.com> writes:
> 
> 
>>guile> (readline-set! 'bounce-parens 50)
>><unnamed port>: In expression (readline-options-interface (append # #)):
>><unnamed port>: Unbound variable: readline-options-interface
>>ABORT: (unbound-variable)
> 
> 
> Does it work if you omit the quote?  In other words, like this:
> 
> (readline-set! bounce-parens 50)
> 
> (For some reason, possibly analogy with set!, the xxx-enable and
> xxx-disable procedures of the options interface take a quoted option
> name, but xxx-set! takes its option name unquoted.)
> 
> 
>>Maybe I'm doing it wrong, but I think that I follow the manual.
> 
> 
> The manual has examples which show this, but it isn't explicit on the
> point.
> 
> 
>>The second issue is that when I type something, during the time when
>>the matching paren is highlighted (and that is 500 ms by default),
>>guile doesn't accept any input, so every time I close a paren, I get
>>to wait 500 ms to type more. Both gauche and csi with readline
>>modules installed don't hang like this, so I think it's a
>>guile-specific bug.
> 
> 
> I probably can't help here, but what OS and Guile version are you
> using?
> 
>         Neil
> 
> 

-- 
The human knowledge belongs to the world


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: using guile's readline module

[Kevin Ryde]

Gene Pavlovsky <heilong@bluebottle.com> writes:
>
> guile> (readline-set! bounce-parens 50)
> <unnamed port>: In expression (readline-options-interface (append # #)):
> <unnamed port>: Unbound variable: readline-options-interface
> ABORT: (unbound-variable)

Fixed in the cvs, only waiting for the 1.6.8 release.

(readline-options-interface needs to be exported from
guile-readline/ice-9/readline.scm for use by the macros.)


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: using guile's readline module

[Kevin Ryde]

Gene Pavlovsky <heilong@bluebottle.com> writes:
>
> The second issue is that when I type something, during the time when the matching paren is highlighted (and that is 500 ms by default), 
> guile doesn't accept any input,

The delay is supposed to stop when you press a key, done by guile
using a `select' on the stdin.  You might be able to see if select is
working properly.


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile

Re: using guile's readline module

[Gene Pavlovsky]

My /etc/inputrc has:
set blink-matching-paren on

The delay has disappeared when I changed it to
$if guile
$else
  set blink-matching-paren on 
$endif

So I guess readline's forced blink-matching-paren somehow overrided guile's own code. Dunno why the delay, cause
chicken's interpreter (which doesn't have any special match_paren code - the reason I turned it on in inputrc) doesn't
have that delay. So maybe it is still a bug to be fixed.

Kevin Ryde wrote:
> Gene Pavlovsky <heilong@bluebottle.com> writes:
> 
>>The second issue is that when I type something, during the time when the matching paren is highlighted (and that is 500 ms by default), 
>>guile doesn't accept any input,
> 
> 
> The delay is supposed to stop when you press a key, done by guile
> using a `select' on the stdin.  You might be able to see if select is
> working properly.
> 

-- 
The human knowledge belongs to the world


_______________________________________________
Bug-guile mailing list
Bug-guile@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-guile