Re: 3 readline bugs: source positions, readline-options, endless loop on error

[Dirk Herrmann]

On Thu, 25 Jan 2001, Martin Grabmueller wrote:

> - Is scm-error the right way to report the error?  The output is
>     guile> (set-readline-output-port! #t)
>     ERROR: In procedure set-readline-output-port!:
>     ERROR: Not an open output port: #t
>     ABORT: (wrong-type-arg)
>   , which seems okay to me.

Should be OK.

> - How can I test whether a given port is a file port?  The problem is
>   that my patch works when you pass a stupid value like #t to the
>   procedures, but not for string ports, for example. They lead to the
>   same endless loop like before the patch.

Then the solution is not to only allow file ports, but rather to fix the
problem at its root:  Thinking more about it, I think set-readline-*-port
should only accept input ports, but since any port can be closed at any
time, it is better to be able to cope with closed ports.  When doing this,
we should also fix the code such that string ports are no problem any
more.

Could you try to find a solution for that problem?  That would be very
helpful.  Thanks a lot.

Best regards,
Dirk Herrmann