Subject: bug#6991: closed (Re: bug#6991: Please keep bytecode out of *Backtrace* buffers)

From: [email-masked] (GNU bug Tracking System)
Date: Wed, 22 Feb 2012 17:06:03 +0000

Your bug report

#6991: Please keep bytecode out of *Backtrace* buffers

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
6991: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6991
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#6991: Please keep bytecode out of *Backtrace* buffers
From: Juanma Barranquero <[email-masked]>
To: Drew Adams <[email-masked]>
Cc: Glenn Morris <[email-masked]>, [email-masked], [email-masked]
Date: Wed, 22 Feb 2012 18:01:53 +0100
List-Id: <debbugs-submit.debbugs.gnu.org>

On Wed, Feb 22, 2012 at 17:43, Drew Adams <[email-masked]> wrote:

> Why?  No reason given.  This is a reasonable request, which would improve
> correspondence about bugs and user difficulties.
>
> Users who are aware of the problem often have to manually excise such binary
> codes and replace them with `...' or nothing.

Yes. Not two days ago I had to do exactly that.

> This should at least be a wishlist item, IMO.  Or at least give a convincing
> argument why the request is not appropriate.

Agreed.

    Juanma

Subject: Please keep bytecode out of *Backtrace* buffers
From: [email-masked]
To: [email-masked]
Date: Tue, 07 Sep 2010 09:35:10 +0800
List-Id: <debbugs-submit.debbugs.gnu.org>

Please keep bytecode out of *Backtrace* buffers.
* It is unreadable.
* It will cause problems when sent via email. Even if one runs col(1)
and strings(1) on it, nobody can read it anyway.
* The mountain of gobbledygook makes people reading give up on trying to help.
E.g., http://article.gmane.org/gmane.emacs.w3m/8695