Custom Query (1030 matches)
Results (598 - 600 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #227 | fixed | Hemlock shouldn't crash CCL if it runs into an attribute line it doesn't understand | ||
| Description |
(From GB e-mail response to Ron Garret) All that I can tell is that it's trying to write a warning to the echo area to the effect that it doesn't understand the "Syntax:" file option; I'm not sure that the echo area even exists at this point. (It's dying in the method #/readFromURL:ofType:error: on hemlock-editor-document; this code is running on the event thread, and whatever its notion of "the echo area" is, it probably isn't correct.) If it's going to try to parse the attribute line and if it's going to do someting other than silently ignore attributes that it doesn't understand, it should probably do that parsing a little later (and, in the current model, it should do that on the right thread.) On Thu, 3 Jan 2008, Ron Garret wrote: Correction: It's (apparently) not CFFI. The problem seems to be trying to open a file containing the following modeline: ;;; -*- Mode: LISP; Syntax: ANSI-Common-Lisp; Package: CL-USER; -*- Trying to open a file with this modeline dumps a whole bunch of error messages to the console and results in a broken Lisp. |
|||
| #228 | fixed | Once exhausted, process becomes uninterruptable | ||
| Description |
Once a process is allowed to run to exhaustion, it never again responds to process-interrupt: (let ((p (make-process "Test")))
;; Let it run through once
(process-preset p #'(lambda () nil))
(process-enable p)
(process-wait "exhaust" #'(lambda () (process-exhausted-p p)))
;; Now revive it and try to interrupt it
(process-preset p #'(lambda () (sleep 10)))
(process-reset p)
(process-enable p)
(sleep 1)
(let ((test :never))
(process-interrupt p #'(lambda () (setq test :interrupt)))
(process-wait "exhaust" #'(lambda () (process-exhausted-p p)))
test))
|
|||
| #237 | fixed | IDE wedges trying to navigate within string | ||
| Description |
In a new buffer, enter (foo "bar then place the insertion point after the quotes and press, e.g., c-m-f. IDE will wedge and has to be killed. I think the problem is that generally, hemlock code isn't prepared to navigate inside strings (valid-spot is nil), but much of the time it doesn't actually check for it so in some cases it just goes into infinite loops. |
|||
