[debbugs-tracker] bug#6991: closed (Please keep bytecode out of *Backtrace* buffers)

[GNU bug Tracking System]

Your message dated Wed, 22 Feb 2012 18:01:53 +0100
with message-id <address@hidden>
and subject line Re: bug#6991: Please keep bytecode out of *Backtrace* buffers
has caused the debbugs.gnu.org bug report #6991,
regarding Please keep bytecode out of *Backtrace* buffers
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
6991: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=6991
GNU Bug Tracking System
Contact address@hidden with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> Please keep bytecode out of *Backtrace* buffers
>
>
>
>
> Date: 
>
> Tue, 07 Sep 2010 09:35:10 +0800
>
>
>
>
> 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
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#6991: Please keep bytecode out of *Backtrace* buffers
>
>
>
>
> Date: 
>
> Wed, 22 Feb 2012 18:01:53 +0100
>
>
>
>
> On Wed, Feb 22, 2012 at 17:43, Drew Adams <address@hidden> 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
>
>
> --- End Message ---