Received: by 10.66.74.10 with SMTP id p10mr1168960pav.17.1345990156684;
        Sun, 26 Aug 2012 07:09:16 -0700 (PDT)
Path: t10ni76269232pbh.0!nntp.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!news.snarked.org!newsfeed.news.ucla.edu!ihnp4.UCSD.Edu!nntp.ucr.edu!solaris.cc.vt.edu!news.vt.edu!news.glorb.com!npeer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post01.iad.highwinds-media.com!newsfe15.iad.POSTED!00000000!not-for-mail
From: Stefan Monnier <monn...@iro.umontreal.ca>
Newsgroups: gnu.emacs.help
Subject: Re: Single unrecognized character wrecks entire display
Message-ID: <jwv628bx9bs.fsf-monnier+gnu.emacs.help@gnu.org>
References: <op.wi8wcskadp0apa@eucalyptus>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux)
Cancel-Lock: sha1:dGBaiyemwphHZqbjxyQit0n5evs=
MIME-Version: 1.0
Lines: 14
X-Complaints-To: abuse@UsenetServer.com
NNTP-Posting-Date: Wed, 22 Aug 2012 15:01:04 UTC
Date: Wed, 22 Aug 2012 11:01:04 -0400
X-Received-Bytes: 1191
Bytes: 1470
Content-Type: text/plain

> Is there a way to quickly spot the offending character within Emacs in
> such cases?

Good question.  Please send it as a feature request via
M-x report-emacs-bug.

As for an answer, it might be that C-x RET r utf-8 RET might do the
trick (basically, the single offending byte caused Emacs to decide that
the file is not using utf-8 and read it as a binary file; so by
forcing the use of utf-8 you should get all the utf-8 encoded chars to
appear correctly and the invalid byte to appear as \234).


        Stefan