GNU bug report logs - #9270
`Non-printable characters found'

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 9270 in the body.
You can then email your comments to 9270 AT debbugs.gnu.org in the normal way.

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

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

From: Dave Abrahams <dave <at> boostpro.com>
To: submit <at> debbugs.gnu.org (The Gnus Bugfixing Girls + Boys)
Subject: `Non-printable characters found'
Date: Tue, 09 Aug 2011 11:59:25 -0400

I've recently discovered that messages sent out containing NUL (0)
characters (which are common in emacs backtraces) are often truncated at
the point of the NUL.  I don't think the warning about "non-printable
characters" is adequate to that danger.  When I see it, I normally
think, "who cares?  I don't expect anyone to print this!"

I suggest either:

  force-replacing NUL or

  issuing a different warning about NUL characters and their possible effects.
  




No Gnus v0.18
GNU Emacs 23.3.1 (x86_64-apple-darwin10.8.0, Carbon Version 1.6.0 AppKit 1038.36)
 of 2011-08-01 on vulcan
200 news.gmane.org InterNetNews NNRP server INN 2.5.1 ready (posting ok)
101 Capability list:
VERSION 2
IMPLEMENTATION INN 2.5.1
AUTHINFO USER
HDR
LIST ACTIVE ACTIVE.TIMES DISTRIB.PATS HEADERS NEWSGROUPS OVERVIEW.FMT
OVER
POST
READER
STARTTLS
.

-- 
Dave Abrahams
BoostPro Computing
http://www.boostpro.com

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

From: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
To: Dave Abrahams <dave <at> boostpro.com>
Cc: 9270 <at> debbugs.gnu.org
Subject: Re: `Non-printable characters found'
Date: Thu, 18 Aug 2011 01:50:33 +0200

Dave Abrahams <dave <at> boostpro.com> writes:

> I've recently discovered that messages sent out containing NUL (0)
> characters (which are common in emacs backtraces) are often truncated at
> the point of the NUL.

It would be interesting to find out why, by the way.  I thought most
SMTP servers were pretty 8-bit clean these days...

> I don't think the warning about "non-printable
> characters" is adequate to that danger.  When I see it, I normally
> think, "who cares?  I don't expect anyone to print this!"
>
> I suggest either:
>
>   force-replacing NUL or
>
>   issuing a different warning about NUL characters and their possible effects.

I've made the warning different.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/

Previous Next

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