Re: Questions about throw-on-input

[Stefan Monnier]

>> Actually a better solution is often to run in a separate process
>> (e.g. via `async.el`). That also lets you use the various CPU cores
>> lying idle ;-)
> async.el starts slowly,

Right, but you were talking about a presumably longish-running
background job, so the startup should be "negligible".

> has no good way to read the current state like text properties or
> buffer content, has no knowledge about loaded libraries and incurs
> double serialization overhead.

Yes, it has its share of hurdles.

>> IOW if `thread-yield` doesn't do the trick, you should
>> likely `M-x report-emacs-bug`.
> Yielding doesn't work for me, my input is ignored most of the time. I
> will make my code emacs-q ready and open a bug report for it tomorrow.

Thanks,


        Stefan