Eric Abrahamsen <e...@ericabrahamsen.net> writes: > In the meantime I got a backtrace on my stop-the-world nntp connection > error, which I've posted below. I guess there's nothing mysterious about > it -- the process dies (I can't tell if it's actually the timeout doing > it or not), and nntp-accept-process-output/nntp-report ends up raising > the error, and there's nothing up the line to catch it. Does this look > surprising or wrong for any reason? > > (if nntp--report-1 (progn (if nntp-record-commands (progn > (nntp-record-command "*** CONNECTION LOST ***"))) (throw
Network errors are common, so it shouldn't be throwing an error in the first place. But I can't recall ever seeing the `nntp-report' function before, so who knows what the logic is. :-/ That looks like a... debugging function? -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no
