Lars Ingebrigtsen <[email protected]> writes: > Lars-Johan Liman <[email protected]> writes: > >> My question: how is my answer (yes/no) used? (Which are the consequences >> of responding yes or no, respectively?) > > Answering "no" should beep an error, say "Cannot get new mail" and then > stop. Hm... but I see that the caller (in `nnmail-get-new-mail-1' just > ignores that, and carries on as if nothing happened), so it doesn't > matter whatever you respond. > > Hm... I'm not sure how to fix this, or what the right fix would be > here. Anybody got an opinion?
I have an opinion :) We create a few custom error symbols for backend errors, including mail source failures, open-server failures, etc, and we put some condition-cases handling those errors in `gnus-get-unread-articles'. They collect the errors, continue with the next server, and at the end of the process display a nice tidy message indicating which servers failed to connect. It's always been a bit annoying that an nntp connection failure hoses the entire update process. WDYT? Eric
