Custom Query (1030 matches)
Results (595 - 597 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #560 | fixed | Return doesn't self-insert in listener | ||
| Description |
There have been some changes recently to the behavior of the RETURN key in the IDE. By and large these changes have been improvements, but there is a small lingering bug: when RETURN is pressed with the cursor at the end of a listener buffer and there's a form to evaluate, the return character does not self-insert. As a result, if you PRINC something instead of PRINTing it, it ends up on the same line as the form being evaluated, which is a little weird. The problem is particularly evident when doing an apropos: Welcome to Clozure Common Lisp Version 1.4-dev (DarwinX8664)!
? (apropos :foo) HI::FOO
GUI::FOO
CCL::FOO
:FOO, Value: :FOO
?
|
|||
| #559 | fixed | CCL hangs when loading cl+ssl with *load-print* set to T in IDE | ||
| Description |
Subject line pretty much says it all. Set *load-print* to T and try to asdf-load the CL+SSL package. It will hang when loading bio.dx*fsl. When *load-print* is NIL the problem goes away. I'm using the 2008-11-04 version of CL+SSL but I'm pretty sure the problem doesn't depend on that. The problem manifests itself only in the IDE. When run from the terminal it works fine even with *load-print* set to T. |
|||
| #558 | fixed | Printing long strings in the IDE is veeeerrrry sssllloooowwww | ||
| Description |
? (time (print (make-string 10000)))
""
(PRINT (MAKE-STRING 10000)) took 11,157,608 microseconds (11.157608 seconds) to run
with 2 available CPU cores.
During that period, 10,291,164 microseconds (10.291164 seconds) were spent in user mode
868,038 microseconds (0.868038 seconds) were spent in system mode
70,577 microseconds (0.070577 seconds) was spent in GC.
97,616 bytes of memory allocated.
120 minor page faults, 12,281 major page faults, 0 swaps.
""
Note that the above was run with string highlighting disabled. When it's enabled, things get even slower. (See ticket #540.) It would also be nice (and would be a resolution of this ticket as far as I'm concerned) to have something like *print-length* that applied to strings. I'm doing some database work that involves very long strings (megabytes) and it would be very nice not to have to manually kill the printing process whenever I accidentally print one of these monsters. I'm calling this a "minor enhancement" because I can work around it myself by defining a print-object method on strings. |
|||
