Trailing whitespace in input causes GCL to forget to
print the next input prompt.
E.g.
(%i1) a : 100; <-- there is a space character after
the semicolon here
(%o1) 100
a;
(%o2) 100
(%i3) a : 200$ <-- there is a space character after
the dollar sign here
a;
(%o4) 200
Same behavior for Maxima 5.9.3cvs / GCL 2.6.7 / Linux,
and Maxima 5.9.3 / GCL 2.6.7 / Win XP.
Behavior not observed with SBCL or Clisp.
Could be readline strangeness, although Clisp has
readline and it is OK (i.e., input prompts are printed
as expected).
Logged In: YES
user_id=501686
An attempt was made (see
http://maxima.cvs.sourceforge.net/maxima/maxima/src/nparse.lisp?view=log\)
to fix this problem by calling a local NEWLINE function
instead of GCL SI::NEWLINE. However, it appears that leads
to problems with GCL 2.8.0. See the message dated 2006/11/11
from Vadim Zhytnikov, "Re: Rev 1.31 of src/nparse.lisp
breaks windows build of CVS HEAD". (Might be able to find it
at: http://news.gmane.org/gmane.comp.mathematics.maxima.general\)
Not observed with GCL 2.6.12 (near 2.6.13) + post-5.46 Maxima. Closing this report as fixed.