#17 closed defect (invalid)
SLIME: Invoking TOP-LEVEL restart always terminates connection
| Reported by: | Mark Evenson | Owned by: | somebody |
|---|---|---|---|
| Priority: | minor | Milestone: | 0.22 |
| Component: | other | Version: | |
| Keywords: | Cc: | trittweiler | |
| Parent Tickets: |
Description
When using ABCL from SLIME, invoking the very tempting TOP-LEVEL restart always causes the connection to terminate.
Change History (5)
comment:1 Changed 15 years ago by
comment:2 Changed 14 years ago by
I'd say the assessment is correct. That being so, what should be the remaining issue?
comment:3 Changed 14 years ago by
| Cc: | trittweiler added |
|---|---|
| Resolution: | → invalid |
| Status: | new → closed |
The TOP-LEVEL restart can be circumvented by starting ABCL with an --eval or --load argument instead of piping the SWANK startup commands into it.
I don't really think there's an issue here. Please reopen if there actually is - detailing the exact error condition or reason why SLIME can't use the --eval or --load route.
comment:4 Changed 14 years ago by
Verified that this problem is no longer occurring with contemporary ABCL/SLIME versions, with the TOP-LEVEL restart having been renamed to appear as "*ABORT". Probably this was more a problem on the SLIME end of things that has changed.
comment:5 Changed 14 years ago by
| Milestone: | unscheduled → 0.22 |
|---|
closed is not 'unscheduled'; moving to the most recently closed milestone.
This is presumably occurring. because the TOP-LEVEL restart is established (top-level.lisp:408) before the SWANK-LOADER code starts up the connection to SLIME.