Hello, I have found a workaround that no longer needs to programmatically cancel the capture in a hook (in a nutshell, I wrote my own org-protocol handler that checks the url before initiating the capture process). So I’m not sure this is actually a bug or something that does not need fixing (in the sense: should it be possible to cancel a capture from a capture hook?). Please feel free to cancel or won’t fix this if you think it is not a bug.
Best, Alan
signature.asc
Description: PGP signature
