Thanks,
Zach
He can't -- Control-C on Windows will just take down the process, unfortunately.
The best (pretty lame) bet is probably to (TRACE "QL") or something like that.
Cheers,
-- Nikodemus
--
Makarov Alexey <alex...@yandex.ru>
Original posted mentioned dmitryvk's threaded build of SBCL for windows.
I'm going to implement Control-C handling for threaded builds (as part
of a larger win32 I/O improvement effort, currently restricted mostly to
thread-related issues: http://github.com/akovalenko/sbcl-win32-threads ).
There is a problem with Control-C, however: what thread should receive a signal?
(on Windows, "console control handlers" are invoked in entirely separate
system thread, so it has to be turned into interrupt_lisp_thread, and
some existing lisp thread has to be selected as a recipient).
--
Regards, Anton Kovalenko
+7(916)345-34-02 | Elektrostal' MO, Russia
> Original posted mentioned dmitryvk's threaded build of SBCL for windows.
> I'm going to implement Control-C handling for threaded builds (as part
> of a larger win32 I/O improvement effort, currently restricted mostly to
> thread-related issues: http://github.com/akovalenko/sbcl-win32-threads ).
>
> There is a problem with Control-C, however: what thread should receive a signal?
> (on Windows, "console control handlers" are invoked in entirely separate
> system thread, so it has to be turned into interrupt_lisp_thread, and
> some existing lisp thread has to be selected as a recipient).
This is probably best take to sbcl-devel. :)
Cheers,
-- Nikodemus
(defun fetch (url file &key (follow-redirects t) quietly
(maximum-redirects *maximum-redirects *))
"Request URL and write the body of the response to FILE."
....
(if quietly
(save-response file header cbuf)
(call-with-progress-bar (content-length header)
(lambda ()
(save-response file header cbuf))))))
....)
It is noticed that the problem appears not constantly, but anyhow is present at least for one file at (quicklisp-quickstart:install).