From 032969e8c65ba1ccda8466f6c61f20e0c7293ebf Mon Sep 17 00:00:00 2001 From: Eric Abrahamsen Date: Sun, 31 Oct 2021 18:01:15 -0700 Subject: [PATCH] Don't have nntp-report signal an error * lisp/gnus/nntp.el (nntp-report): This should behave as much as possible like nnheader-report, which only logs the error and returns nil. --- lisp/gnus/nntp.el | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/lisp/gnus/nntp.el b/lisp/gnus/nntp.el index 615a3c931bf..25289655bf2 100644 --- a/lisp/gnus/nntp.el +++ b/lisp/gnus/nntp.el @@ -331,9 +331,7 @@ retried once before actually displaying the error report." (when nntp-record-commands (nntp-record-command "*** CALLED nntp-report ***")) - (nnheader-report 'nntp args) - - (apply #'error args))) + (nnheader-report 'nntp args))) (defsubst nntp-copy-to-buffer (buffer start end) "Copy string from unibyte current buffer to multibyte buffer." -- 2.39.2