GNU bug report logs - #70166
debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’

Previous Next

To reply to this bug, email your comments to 70166 AT debbugs.gnu.org.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: bug-gnu-emacs <at> gnu.org
Subject: debbugs 0.40; Empty *Group* buffer remains after quitting
 ‘debbugs’
Date: Wed, 03 Apr 2024 19:34:56 +0200

[Message part 1 (text/plain, inline)]

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.

[Message part 2 (message/rfc822, inline)]

From: tpeplt <tpeplt <at> gmail.com>
To: Michael Albinus <michael.albinus <at> 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.

--

Message #10 received at 70166 <at> debbugs.gnu.org (full text, mbox):

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Eric Abrahamsen <eric <at> ericabrahamsen.net>
Cc: tpeplt <tpeplt <at> gmail.com>, 70166 <at> debbugs.gnu.org
Subject: Re: bug#70166: debbugs 0.40; Empty *Group* buffer remains after
 quitting ‘debbugs’
Date: Wed, 03 Apr 2024 19:47:13 +0200

Hi Eric,

could you, pls, have a look on this?

Thanks, and best regards, Michael.

Michael Albinus <michael.albinus <at> gmx.de> writes:

> 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.
>
> From: tpeplt <tpeplt <at> gmail.com>
> Subject: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’
> To:  Michael Albinus <michael.albinus <at> gmx.de>
> Date: Wed, 03 Apr 2024 13:08:13 -0400 (36 minutes, 34 seconds ago)
>
> 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.
>
> --
> ----------

Message #13 received at 70166 <at> debbugs.gnu.org (full text, mbox):

From: tpeplt <tpeplt <at> gmail.com>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: 70166 <at> debbugs.gnu.org
Subject: Re: bug#70166: debbugs 0.40; Empty *Group* buffer remains after
 quitting ‘debbugs’
Date: Wed, 03 Apr 2024 14:19:38 -0400

Michael Albinus <michael.albinus <at> gmx.de> writes:

> 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.

Thank you.  I will use the Emacs bug-report process in the future for
reporting problems with GNU ELPA packages.

This explains why I wasn’t able to find a method in the ‘debbugs-ug’
Info manual on how to create a new problem report.

--

Message #16 received at 70166 <at> debbugs.gnu.org (full text, mbox):

From: Eric Abrahamsen <eric <at> ericabrahamsen.net>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: tpeplt <tpeplt <at> gmail.com>, 70166 <at> debbugs.gnu.org
Subject: Re: bug#70166: debbugs 0.40; Empty *Group* buffer remains after
 quitting ‘debbugs’
Date: Wed, 03 Apr 2024 14:14:13 -0700

Michael Albinus <michael.albinus <at> gmx.de> writes:

> Hi Eric,
>
> could you, pls, have a look on this?

Will do, thanks for the report.

Message #19 received at 70166 <at> debbugs.gnu.org (full text, mbox):

From: Björn Bidar <bjorn.bidar <at> thaodan.de>
To: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of
 text editors" <bug-gnu-emacs <at> gnu.org>
Cc: tpeplt <tpeplt <at> gmail.com>, Michael Albinus <michael.albinus <at> gmx.de>,
 70166 <at> debbugs.gnu.org
Subject: Re: bug#70166: debbugs 0.40; Empty *Group* buffer remains after
 quitting ‘debbugs’
Date: Thu, 04 Apr 2024 03:53:38 +0300

I hope my comments fits to this bug.
I wonder if this bug is a side effect of Debbugs not opening it's own
Group buffer?

I noticed calling debbugs can mess with an existing Gnus session.

Message #22 received at 70166 <at> debbugs.gnu.org (full text, mbox):

From: Björn Bidar <bjorn.bidar <at> thaodan.de>
To: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of
 text editors" <bug-gnu-emacs <at> gnu.org>
Cc: tpeplt <tpeplt <at> gmail.com>, Michael Albinus <michael.albinus <at> gmx.de>,
 70166 <at> debbugs.gnu.org
Subject: Re: bug#70166: debbugs 0.40; Empty *Group* buffer remains after
 quitting ‘debbugs’
Date: Thu, 04 Apr 2024 03:53:47 +0300

I hope my comments fits to this bug.
I wonder if this bug is a side effect of Debbugs not opening it's own
Group buffer?

I noticed calling debbugs can mess with an existing Gnus session.

Message #31 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Björn Bidar <bjorn.bidar <at> thaodan.de>
To: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of
 text editors" <bug-gnu-emacs <at> gnu.org>
Cc: tpeplt <tpeplt <at> gmail.com>, Michael Albinus <michael.albinus <at> gmx.de>,
 70166 <at> debbugs.gnu.org
Subject: Re: bug#70166: debbugs 0.40; Empty *Group* buffer remains after
 quitting ‘debbugs’
Date: Thu, 04 Apr 2024 03:54:02 +0300

I hope my comments fits to this bug.
I wonder if this bug is a side effect of Debbugs not opening it's own
Group buffer?

I noticed calling debbugs can mess with an existing Gnus session.

Message #34 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Björn Bidar <bjorn.bidar <at> thaodan.de>
To: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of
 text editors" <bug-gnu-emacs <at> gnu.org>
Cc: tpeplt <tpeplt <at> gmail.com>, Michael Albinus <michael.albinus <at> gmx.de>,
 70166 <at> debbugs.gnu.org
Subject: Re: bug#70166: debbugs 0.40; Empty *Group* buffer remains after
 quitting ‘debbugs’
Date: Thu, 04 Apr 2024 03:54:18 +0300

I hope my comments fits to this bug.
I wonder if this bug is a side effect of Debbugs not opening it's own
Group buffer?

I noticed calling debbugs can mess with an existing Gnus session.

Message #37 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Björn Bidar <bjorn.bidar <at> thaodan.de>
To: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of
 text editors" <bug-gnu-emacs <at> gnu.org>
Cc: tpeplt <tpeplt <at> gmail.com>, Michael Albinus <michael.albinus <at> gmx.de>,
 70166 <at> debbugs.gnu.org
Subject: Re: bug#70166: debbugs 0.40; Empty *Group* buffer remains after
 quitting ‘debbugs’
Date: Thu, 04 Apr 2024 03:54:44 +0300

I hope my comments fits to this bug.
I wonder if this bug is a side effect of Debbugs not opening it's own
Group buffer?

I noticed calling debbugs can mess with an existing Gnus session.

Message #49 received at 70166 <at> debbugs.gnu.org (full text, mbox):

From: Björn Bidar <bjorn.bidar <at> thaodan.de>
To: Michael Albinus via "Bug reports for GNU Emacs, the Swiss army knife of
 text editors" <bug-gnu-emacs <at> gnu.org>
Cc: tpeplt <tpeplt <at> gmail.com>, Michael Albinus <michael.albinus <at> gmx.de>,
 70166 <at> debbugs.gnu.org
Subject: Re: bug#70166: debbugs 0.40; Empty *Group* buffer remains after
 quitting ‘debbugs’
Date: Thu, 04 Apr 2024 03:57:46 +0300

I hope my comments fits to this bug.
I wonder if this bug is a side effect of Debbugs not opening it's own
Group buffer?

I noticed calling debbugs can mess with an existing Gnus session.

Message #55 received at 70166 <at> debbugs.gnu.org (full text, mbox):

From: Björn Bidar <bjorn.bidar <at> thaodan.de>
To: 70166 <at> debbugs.gnu.org
Cc: michael.albinus <at> gmx.de, tpeplt <at> gmail.com
Subject: Re: bug#70166: debbugs 0.40; Empty *Group* buffer remains after
 quitting ‘debbugs’
Date: Thu, 04 Apr 2024 04:00:08 +0300

Sorry for the spam I've caused. I did appeared as if my message didn't go
out as `message-send` failed with:
split-string-and-unquote: End of file during parsing

Message #60 received at 70166 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Kangas <stefankangas <at> gmail.com>
To: Eric Abrahamsen <eric <at> ericabrahamsen.net>
Cc: tpeplt <tpeplt <at> gmail.com>, Michael Albinus <michael.albinus <at> gmx.de>,
 70166 <at> debbugs.gnu.org
Subject: Re: bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’
Date: Fri, 28 Feb 2025 18:54:10 -0800

Eric Abrahamsen <eric <at> ericabrahamsen.net> writes:

> Michael Albinus <michael.albinus <at> gmx.de> writes:
>
>> Hi Eric,
>>
>> could you, pls, have a look on this?
>
> Will do, thanks for the report.

Eric, were you able to make any progress here?

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.