[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
master 032969e: Don't have nntp-report signal an error
From: |
Eric Abrahamsen |
Subject: |
master 032969e: Don't have nntp-report signal an error |
Date: |
Mon, 8 Nov 2021 14:31:32 -0500 (EST) |
branch: master
commit 032969e8c65ba1ccda8466f6c61f20e0c7293ebf
Author: Eric Abrahamsen <eric@ericabrahamsen.net>
Commit: Eric Abrahamsen <eric@ericabrahamsen.net>
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 615a3c9..2528965 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."
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- master 032969e: Don't have nntp-report signal an error,
Eric Abrahamsen <=