From: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 70166@debbugs.gnu.org
Cc: tpeplt <tpeplt@gmail.com>
Subject: bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’
Date: Wed, 03 Apr 2024 19:34:56 +0200 [thread overview]
Message-ID: <87il0y2vun.fsf@gmx.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 231 bytes --]
Hi,
Debbugs is a GNU ELPA package. As such, an ordinary bug report for Emacs
is preferred.
Contacting me as the author isn't wrong; I'm forwarding your message in
order to get it registered as Emacs bug.
Best regards, Michael.
[-- Attachment #2: Type: message/rfc822, Size: 1971 bytes --]
From: tpeplt <tpeplt@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
Subject: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’
Date: Wed, 03 Apr 2024 13:08:13 -0400
Michael Albinus,
Thank you for providing and maintaining the ‘debbugs’ package.
After searching the Info manuals for ‘debbugs’ and
‘debbugs-ug’ for instructions on where or how to report a
problem with ‘debbugs’ and not finding any information, I am
writing to your email address as the only contact
information that I could find (via ‘list-packages’ for ‘debbugs’).
The problem that I am reporting below is occurring with
Emacs version 29.3 and debbugs 0.40. Here are the steps to
reproduce this problem:
1. Enter the command ‘debbugs-gnu-bugs’:
M-x debbugs-gnu-bugs RET
2. At the prompt, enter a random bug number:
Bug numbers (default -10): 123 RET
3. The *Bugs* buffer is displayed with messages for the
corresponding bug number. Type RET to run the command
‘debbugs-gnu-select-report’ for one of the messages.
The buffer *ephemeral:bug#123* is displayed, where "123"
is whichever bug number you chose.
4. Type q to run the command ‘gnus-summary-exit’.
‘debbugs’ returns to the *Bugs* buffer
5. Type q to run the command ‘quit-window’.
A buffer named *Group* remains.
If you repeat the steps above, but skip step 3 (that is, do
not select a report), then ‘q’ exits debbugs and does not
leave behind a stray *Group* buffer.
It appears that ‘debbugs-gnu-select-report’ creates a
*Group* buffer, but neglects to delete it when
‘gnus-summary-exit’ is run.
--
next reply other threads:[~2024-04-03 17:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 17:34 Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-04-03 17:47 ` bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’ Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-03 21:14 ` Eric Abrahamsen
2024-04-03 18:19 ` tpeplt
2024-04-04 0:53 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-04 0:53 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-04 0:53 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-04 0:53 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-04 0:54 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-04 0:54 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-04 0:54 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-04 0:54 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-04 0:54 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-04 0:54 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-04 0:57 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-04 0:57 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87v84yc5il.fsf@>
2024-04-04 1:00 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=87il0y2vun.fsf@gmx.de \
--to=bug-gnu-emacs@gnu.org \
--cc=70166@debbugs.gnu.org \
--cc=michael.albinus@gmx.de \
--cc=tpeplt@gmail.com \
/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).