#613 ~% introduces an extra line break

closed-invalid
Sam Steingold
clisp (525)
5
2011-10-04
2011-10-01
Mirko
No

The following unexpectedly inserts a line-break after `A' :
[2]> (format t "A~aB~%"
(format nil "5~%~a" 3))
A
5
3B
NIL

But this works:
(format t "A~?B~%"
"5~%~a" '(3))
A5
3B
NIL

*pretty-print* effects: The came clisp produces correct input if I set *pretty-print* to nil in SLIME, but if I do the same from within clisp, I get the erroneous output.

clisp was started as > clisp -norc

Other info:
>uname -a
CYGWIN_NT-5.1 WTTCA1068 1.7.8(0.236/5/3) 2011-03-01 09:36 i686 Cygwin
/home/977315
>clisp --version
GNU CLISP 2.48 (2009-07-28) (built on ATGRZWN502840.avl01.avlcorp.lan [157.247.26.41])
Software: GNU C 4.3.4 20090804 (release) 1
gcc-4 -O2 -pipe -g -W -Wswitch -Wcomment -Wpointer-arith -Wimplicit -Wreturn-type -Wmissing-declarations -Wno-sign-compare -Wno-format-nonliteral -O2 -fexpensive-optimizations -falign-functions=4 -DUNICODE -DDYNAMIC_FFI -I. -Wl,--stack,8388608 -Wl,--enable-auto-import /usr/lib/libintl.dll.a /usr/lib/libiconv.dll.a /usr/lib/libreadline.dll.a -lncurses /usr/lib/libavcall.a /usr/lib/libcallback.a /usr/lib/libiconv.dll.a -L/usr/lib -lsigsegv
SAFETY=0 HEAPCODES STANDARD_HEAPCODES SPVW_PAGES SPVW_MIXED
libsigsegv 2.8
libiconv 1.13
libreadline 6.0
Features:
(READLINE REGEXP SYSCALLS I18N LOOP COMPILER CLOS MOP CLISP ANSI-CL COMMON-LISP
LISP=CL INTERPRETER SOCKETS GENERIC-STREAMS LOGICAL-PATHNAMES SCREEN FFI
GETTEXT UNICODE BASE-CHAR=CHARACTER PC386 UNIX CYGWIN)
C Modules: (clisp i18n syscalls regexp readline)
Installation directory: /usr/lib/clisp-2.48/
User language: ENGLISH
Machine: I686 (I686) WTTCA1068.us.tel.com [172.17.56.65]
/home/977315

Discussion

  • Sam Steingold
    Sam Steingold
    2011-10-01

    • assigned_to: haible --> sds
    • status: open --> pending-invalid
     
  • Sam Steingold
    Sam Steingold
    2011-10-01

    This bug report is now marked as "pending"/"invalid".
    This means that we think that the problem you report is not a problem with CLISP.
    Unless you - the reporter - act within 2 weeks, the bug will be permanently closed.
    Sorry about the inconvenience - we hope your silence means that you agree that this is not a bug in CLISP.

     
  • Mirko
    Mirko
    2011-10-03

    I just saw the *pretty-printer-newline* variable. This is not a bug in clisp.

    Sorry about the false alarm.

    Thank you,

    Mirko

     
  • Mirko
    Mirko
    2011-10-03

    • status: pending-invalid --> open-invalid
     
  • Sam Steingold
    Sam Steingold
    2011-10-04

    • status: open-invalid --> closed-invalid