emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#9664: closed ((format #t "~3tX") fails in the REPL


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#9664: closed ((format #t "~3tX") fails in the REPL)
Date: Wed, 16 Nov 2011 22:16:02 +0000

Your message dated Wed, 16 Nov 2011 23:15:00 +0100
with message-id <address@hidden>
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
address@hidden)


-- 
9664: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=9664
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: (format #t "~3tX") fails in the REPL Date: Mon, 3 Oct 2011 21:59:48 +0200 User-agent: Mutt/1.5.21 (2010-09-15)
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.




--- End Message ---
--- Begin Message --- Subject: Re: bug#9664: (format #t "~3tX") fails in the REPL Date: Wed, 16 Nov 2011 23:15:00 +0100 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)
On Wed 05 Oct 2011 20:18, Andy Wingo <address@hidden> 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/


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]