Unwanted interrupts about elfeed HOT 9 CLOSED

Unfortunately I don't think there's anything I can do about this. Emacs
is single-threaded and updates run asynchronously. As data arrives, the
handler takes control of the main thread at the next opportunity. If you
happen to hit C-g at this moment, you'll interrupt the thread and cancel
the update for that feed, hence the message.

The alternative would be to do updates synchronously, locking up Emacs
until all feeds have updated, so that when you hit C-g it's obvious
what's going to happen.

from elfeed.

I've successfully used inhibit-quit with project-explorer, which also does asynchronous processing.

from elfeed.

I've edited the original post, not sure if you've noticed.

from elfeed.

I was just going off the original e-mail so I didn't see your update. I didn't know about inhibit-quit until just now. It seems Emacs has a hack available for anything!

I just made a commit (53e9102) that uses inhibit-quit. This helps a little bit, but it's still possible (and likely) for C-g to interrupt before I'm able to set inhibit-quit in the callback. Is there a better way to do this?

from elfeed.

Interrupted while url-retrieve is active? I don't think it's affected by C-g.

from elfeed.

With this change in place, I was tapping C-g once every few seconds during an update and was getting errors like these:

error in process filter: Transfer interrupted!
error in process filter: url-http-mark-connection-as-busy: Transfer interrupted!
error in process filter: url-http-generic-filter: Transfer interrupted!
error in process filter: url-http-wait-for-headers-change-function: Transfer interrupted!

This is all outside the callback where I have control.

from elfeed.

I don't think you can. You can have a look at url-http-debug to see why.

from elfeed.

I guess you could wrap the process filter and sentinel, to at least prevent state corruption. Something along these lines

(let* (( process
         (get-buffer-process
          (url-retrieve url cb nil :silent)))
       ( filter (process-filter process)))
  (set-process-filter process
                      (lambda (&rest args)
                        (condition-case error
                            (apply filter args)
                          (error
                           (STUFF)
                           )))))

from elfeed.

This should mostly be fixed by the switch to the curl backend: Elfeed, cURL, and You

from elfeed.