Subject: bug#9664: closed (Re: bug#9664: (format #t "~3tX") fails in the REPL)

From: [email-masked] (GNU bug Tracking System)
Date: Wed, 16 Nov 2011 22:16:02 +0000

Your bug report

#9664: (format #t "~3tX") fails in the REPL

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 [email-masked].

-- 
9664: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9664
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#9664: (format #t "~3tX") fails in the REPL
From: Andy Wingo <[email-masked]>
To: [email-masked]
Cc: [email-masked]
Date: Wed, 16 Nov 2011 23:15:00 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

On Wed 05 Oct 2011 20:18, Andy Wingo <[email-masked]> writes:

> It appears that there is some difference between the readline-enabled
> reader and the normal one.
>
>     $ meta/guile -q
>     scheme@(guile-user)> (port-column (current-output-port))
>     $1 = 21
>
> It is 0 with the readline reader.
>
> I don't think the set-port-column! fix is right.  Why is the newline not
> being chomped after the `(read)', I wonder?

That isn't the right question, it turns out.  21 is the length of the
`scheme@(guile-user)> ' prompt.  We need to set the output port column
to 0 after printing a prompt.  In the readline case it's different
because readline is the part that prints the prompt.

Fixed in stable-2.0.

Thanks for the report,

Andy
-- 
http://wingolog.org/

Subject: (format #t "~3tX") fails in the REPL
From: [email-masked]
To: [email-masked]
Date: Mon, 3 Oct 2011 21:59:48 +0200
List-Id: <debbugs-submit.debbugs.gnu.org>

The ~t formater is not working according to spec in the REPL.
Try this for instance:

(format #t "~10tA~20tB~30tC~40tD")

will print:

AB       C         D

Although it works from a script or when outputing to a sting.

Also, it works after a newline.