bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’

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]

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

--

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]

Hi Eric,

could you, pls, have a look on this?

Thanks, and best regards, Michael.

Michael Albinus <michael.albinus@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@gmail.com>
> Subject: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’
> To:  Michael Albinus <michael.albinus@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.
>
> --
> ----------

bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’

[Eric Abrahamsen]

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

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

Will do, thanks for the report.

bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’

[tpeplt]

Michael Albinus <michael.albinus@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.

--

bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’

[Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors]

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.

bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’

[Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors]

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.

bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’

[Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors]

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.

bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’

[Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors]

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.

bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’

[Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors]

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.

bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’

[Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors]

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.

bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’

[Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors]

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.

bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’

[Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors]

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.

bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’

[Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors]

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.

bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’

[Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors]

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.

bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’

[Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors]

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.

bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’

[Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors]

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.

bug#70166: debbugs 0.40; Empty *Group* buffer remains after quitting ‘debbugs’

[Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors]

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