-
-
Notifications
You must be signed in to change notification settings - Fork 70
Open
Description
The documentation for async-start says:
Note: Even when FINISH-FUNC is present, a future is still
returned except that it yields no value (since the value is
passed to FINISH-FUNC). Call ‘async-get’ on such a future always
returns nil. It can still be useful, however, as an argument to
‘async-ready’ or ‘async-wait’.
But I'm finding some errors when this is the case. As minimal examples:
(async-wait
(async-start
(lambda () (message "hello"))
'ignore))and
(async-wait
(async-start
(lambda () (message "hello"))
(lambda (result) (message "this %s" result))))
Both return the error selecting deleted buffer.
Metadata
Metadata
Assignees
Labels
No labels