GNU bug report logs - #9664
(format #t "~3tX") fails in the REPL

Previous Next

Package: guile;

Reported by: rixed <at> happyleptic.org

Date: Mon, 3 Oct 2011 20:05:02 UTC

Severity: normal

Done: Andy Wingo <wingo <at> pobox.com>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: help-debbugs <at> gnu.org (GNU bug Tracking System)
To: Andy Wingo <wingo <at> pobox.com>
Cc: tracker <at> debbugs.gnu.org
Subject: bug#9664: closed ((format #t "~3tX") fails in the REPL)
Date: Wed, 16 Nov 2011 22:16:02 +0000
[Message part 1 (text/plain, inline)]
Your message dated Wed, 16 Nov 2011 23:15:00 +0100
with message-id <87r517k93v.fsf <at> pobox.com>
and subject line Re: bug#9664: (format #t "~3tX") fails in the REPL
has caused the debbugs.gnu.org bug report #9664,
regarding (format #t "~3tX") fails in the REPL
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)


-- 
9664: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9664
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
From: rixed <at> happyleptic.org
To: bug-guile <at> gnu.org
Subject: (format #t "~3tX") fails in the REPL
Date: Mon, 3 Oct 2011 21:59:48 +0200
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.



[Message part 3 (message/rfc822, inline)]
From: Andy Wingo <wingo <at> pobox.com>
To: rixed <at> happyleptic.org
Cc: 9664-done <at> debbugs.gnu.org
Subject: Re: bug#9664: (format #t "~3tX") fails in the REPL
Date: Wed, 16 Nov 2011 23:15:00 +0100
On Wed 05 Oct 2011 20:18, Andy Wingo <wingo <at> pobox.com> 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/


This bug report was last modified 13 years and 248 days ago.

Previous Next


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