From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: 54324@debbugs.gnu.org
Cc: michael.albinus@gmx.de
Subject: bug#54324: 29.0.50; Don't error during debbugs-gnu-rescan
Date: Wed, 09 Mar 2022 16:19:15 -0800 [thread overview]
Message-ID: <8735jqlkvw.fsf@ericabrahamsen.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 178 bytes --]
`debbugs-gnu-rescan' will error if point isn't on a current bug id,
which isn't necessary. This patch avoids that by passing the NOERROR arg
to `debbugs-gnu-current-id'.
Eric
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-Pass-NOERROR-arg-to-debbugs-gnu-current-id-when-resc.patch --]
[-- Type: text/x-patch, Size: 1010 bytes --]
From 81ba1905bcb6c8a8fc927df92e9fc525ab71ce74 Mon Sep 17 00:00:00 2001
From: Eric Abrahamsen <eric@ericabrahamsen.net>
Date: Wed, 9 Mar 2022 16:14:59 -0800
Subject: [PATCH] Pass NOERROR arg to debbugs-gnu-current-id when rescanning
* debbugs-gnu.el (debbugs-gnu-rescan): There's no need for the rescan
process to require point to be on a bug id.
---
debbugs-gnu.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/debbugs-gnu.el b/debbugs-gnu.el
index 770a832cb3..ef946fc90f 100644
--- a/debbugs-gnu.el
+++ b/debbugs-gnu.el
@@ -1201,7 +1201,7 @@ If NOCACHE is non-nil, bug information is retrieved from the debbugs server.
Interactively, it is non-nil with the prefix argument."
(interactive
(list current-prefix-arg))
- (let ((id (debbugs-gnu-current-id))
+ (let ((id (debbugs-gnu-current-id t))
(debbugs-gnu-current-query debbugs-gnu-local-query)
(debbugs-gnu-current-filter debbugs-gnu-local-filter)
(debbugs-gnu-current-suppress debbugs-gnu-local-suppress)
--
2.35.1
next reply other threads:[~2022-03-10 0:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 0:19 Eric Abrahamsen [this message]
2022-03-10 8:02 ` bug#54324: 29.0.50; Don't error during debbugs-gnu-rescan Michael Albinus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735jqlkvw.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=54324@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).