Custom Query (1030 matches)
Results (901 - 903 of 1030)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #905 | fixed | Apparent race condition in gui:background-process-run-function | ||
| Description |
This: (dotimes (i 3) (gui:background-process-run-function "foo" (lambda () (print 123)))) results in one successfully spawned process and one that reports:
(with one of the most horrifically long backtraces I have ever seen from a process that did not actually overflow the stack). But this: (dotimes (i 2) (gui:background-process-run-function "foo" (lambda () (print 123))) (sleep 0.01)) results in two successfully spawned processes. These results are repeatable for N>2. My guess is this is a race condition having to do with the naming of the windows that are created by the underlying deferred-cocoa-listener-output-streams but I have not been able to verify this. |
|||
| #1103 | fixed | Bounded STRING-EQUAL bug | ||
| Description |
? (string-equal :a :ba :start2 1)
It's a simple bug. There are two references to len1 in ccl::%bounded-string-equal that should be len2. |
|||
| #1151 | fixed | Text selection on cmd-F search does not move the cursor to the selection | ||
| Description |
This seems to be due to a change in behavior introduced in OS X somewhere between Snow Leopard and Mavericks (I can't tell you exactly where because I skipped the Lions). If you do a text search using cmd-F in a Hemlock window the cursor does not move to the selected text. So if you type something after a cmd-F search, you don't replace the selected text, but instead go back to the position in the file where you were before the search began. |
|||
