GNU bug report logs - #34950
27.0.50; Silently and unexpectedly falling back to `no-conversion`

Message received at submit <at> debbugs.gnu.org:

Received: (at submit) by debbugs.gnu.org; 22 Mar 2019 19:41:46 +0000
From debbugs-submit-bounces <at> debbugs.gnu.org Fri Mar 22 15:41:46 2019
Received: from localhost ([127.0.0.1]:54697 helo=debbugs.gnu.org)
	by debbugs.gnu.org with esmtp (Exim 4.84_2)
	(envelope-from <debbugs-submit-bounces <at> debbugs.gnu.org>)
	id 1h7Q30-0004iq-3M
	for submit <at> debbugs.gnu.org; Fri, 22 Mar 2019 15:41:46 -0400
Received: from eggs.gnu.org ([209.51.188.92]:40445)
 by debbugs.gnu.org with esmtp (Exim 4.84_2)
 (envelope-from <monnier@HIDDEN>) id 1h7Q2w-0004ib-EC
 for submit <at> debbugs.gnu.org; Fri, 22 Mar 2019 15:41:44 -0400
Received: from lists.gnu.org ([209.51.188.17]:47344)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
 (Exim 4.71) (envelope-from <monnier@HIDDEN>)
 id 1h7Q2o-0004Tl-D2
 for submit <at> debbugs.gnu.org; Fri, 22 Mar 2019 15:41:35 -0400
Received: from eggs.gnu.org ([209.51.188.92]:54462)
 by lists.gnu.org with esmtp (Exim 4.71)
 (envelope-from <monnier@HIDDEN>) id 1h7Q2n-0000V5-8C
 for bug-gnu-emacs@HIDDEN; Fri, 22 Mar 2019 15:41:34 -0400
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on eggs.gnu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.1 required=5.0 tests=BAYES_50,RCVD_IN_DNSWL_LOW
 autolearn=disabled version=3.3.2
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <monnier@HIDDEN>) id 1h7Pvz-0002Le-6B
 for bug-gnu-emacs@HIDDEN; Fri, 22 Mar 2019 15:34:32 -0400
Received: from alt24.smtp-out.videotron.ca ([70.80.0.75]:25390)
 by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
 (Exim 4.71) (envelope-from <monnier@HIDDEN>)
 id 1h7Pvv-0002B4-0J
 for bug-gnu-emacs@HIDDEN; Fri, 22 Mar 2019 15:34:29 -0400
Received: from fmsmemgm.homelinux.net ([24.203.163.157]) by Videotron with SMTP
 id 7PhKhSpVfHTT37PhLhtOIU; Fri, 22 Mar 2019 15:19:23 -0400
X-Authority-Analysis: v=2.3 cv=ZegzyPdA c=1 sm=1 tr=0
 a=271BjrAMcq2W4n6OKK/JJg==:117 a=271BjrAMcq2W4n6OKK/JJg==:17
 a=NTGMnVQrEZIA:10 a=eUg5rSCazj0qEhIMMlIA:9
Received: by fmsmemgm.homelinux.net (Postfix, from userid 20848)
 id 8908EAEC22; Fri, 22 Mar 2019 15:19:22 -0400 (EDT)
From: Stefan Monnier <monnier@HIDDEN>
To: bug-gnu-emacs@HIDDEN
Subject: 27.0.50; Silently and unexpectedly falling back to `no-conversion`
Date: Fri, 22 Mar 2019 15:19:22 -0400
Message-ID: <jwvsgveg1j9.fsf@HIDDEN>
MIME-Version: 1.0
Content-Type: text/plain
X-CMAE-Envelope: MS4wfCH89FXt5Z+/5dyd301jFlDgvL8X4QozTh5G7uolxEnLwIZR0od1gtLMGoqBVbo9ANo8gzgS1Ll/cqmtumOGqW+9dm5+2zNSnoSOTxH7XiIDdd04jKP+
 fvRLgyo3dBN4LeeP81rg0Xb9Eg2xRzz/4wbEFriYnN1DrJnDrJWNEDcRH3Kiy3xVxjjLuyKyyp5wZg==
X-detected-operating-system: by eggs.gnu.org: Genre and OS details not
 recognized.
X-Received-From: 70.80.0.75
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x
X-Spam-Score: 1.0 (+)
X-Debbugs-Envelope-To: submit
X-BeenThere: debbugs-submit <at> debbugs.gnu.org
X-Mailman-Version: 2.1.18
Precedence: list
List-Id: <debbugs-submit.debbugs.gnu.org>
List-Unsubscribe: <https://debbugs.gnu.org/cgi-bin/mailman/options/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=unsubscribe>
List-Archive: <https://debbugs.gnu.org/cgi-bin/mailman/private/debbugs-submit/>
List-Post: <mailto:debbugs-submit <at> debbugs.gnu.org>
List-Help: <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=help>
List-Subscribe: <https://debbugs.gnu.org/cgi-bin/mailman/listinfo/debbugs-submit>, 
 <mailto:debbugs-submit-request <at> debbugs.gnu.org?subject=subscribe>
Errors-To: debbugs-submit-bounces <at> debbugs.gnu.org
Sender: "Debbugs-submit" <debbugs-submit-bounces <at> debbugs.gnu.org>
X-Spam-Score: -0.0 (/)

Package: Emacs
Version: 27.0.50


I've seen a few reports now where users are puzzled by \NNN thingies in
their buffers (typically because Emacs ended up deciding that the file
should be opened with `no-conversion` instead of utf-8) and have no idea
where they come from or how to fix them.

I think we should try and change the auto-detection of the
coding-system, so as to keep track of the reason for the choice (where
possible), and then offer a command that uses this info to explain
what happened (e.g. "inhibit-nul-byte-detection set
and found a NUL char at position <foo>").

For extra bonus points we could change some major modes (e.g. prog-mode
and text-mode) to automatically warn the user when the buffer is in
unibyte mode and suggest running that new command.


        Stefan