From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#15925: 24.3.50; error when customizing whitespace-display-mappings Date: Fri, 25 Sep 2020 14:06:24 +0300 Message-ID: <83v9g2ru8f.fsf@gnu.org> References: <87mwl0vo36.wl%claudio.bley@gmail.com> <87a6xgd2rw.fsf@gnus.org> <871rirb5ot.fsf@gnus.org> <87ft76rxaw.fsf@gnus.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="3519"; mail-complaints-to="usenet@ciao.gmane.io" Cc: rgm@gnu.org, 15925@debbugs.gnu.org, maurooaranda@gmail.com, claudio.bley@googlemail.com To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Sep 25 13:07:14 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kLlZJ-0000oT-UQ for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 25 Sep 2020 13:07:13 +0200 Original-Received: from localhost ([::1]:48088 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kLlZJ-0004fl-1H for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 25 Sep 2020 07:07:13 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54054) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kLlZ8-0004eQ-PF for bug-gnu-emacs@gnu.org; Fri, 25 Sep 2020 07:07:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:59522) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kLlZ8-0005La-FS for bug-gnu-emacs@gnu.org; Fri, 25 Sep 2020 07:07:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kLlZ8-00011q-AI for bug-gnu-emacs@gnu.org; Fri, 25 Sep 2020 07:07:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 25 Sep 2020 11:07:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 15925 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 15925-submit@debbugs.gnu.org id=B15925.16010319833905 (code B ref 15925); Fri, 25 Sep 2020 11:07:02 +0000 Original-Received: (at 15925) by debbugs.gnu.org; 25 Sep 2020 11:06:23 +0000 Original-Received: from localhost ([127.0.0.1]:42835 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kLlYV-00010v-AD for submit@debbugs.gnu.org; Fri, 25 Sep 2020 07:06:23 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:47128) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kLlYS-00010h-WD for 15925@debbugs.gnu.org; Fri, 25 Sep 2020 07:06:21 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:58547) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kLlYN-0005Jf-C9; Fri, 25 Sep 2020 07:06:15 -0400 Original-Received: from [176.228.60.248] (port=2840 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1kLlYL-0007HW-HB; Fri, 25 Sep 2020 07:06:14 -0400 In-Reply-To: <87ft76rxaw.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 25 Sep 2020 12:00:07 +0200) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:188950 Archived-At: > From: Lars Ingebrigtsen > Date: Fri, 25 Sep 2020 12:00:07 +0200 > Cc: Glenn Morris , 15925@debbugs.gnu.org, > claudio.bley@googlemail.com > > > - What do we do with the other escape sequences, like ?\r and ?\f? > > > > Right now, we display those as ^M and ^L respectively. If we keep this > > representation, maybe somebody will feel there is some inconsistency, > > because some characters we display as ^M, while others as \n. Perhaps > > is not a big deal, though. > > We should definitely strive for consistency here... \r and \f for ^M > and ^L is fine by me (although I guess more people are familiar with ^L > than \f). I very much hope we leave the ^M and ^L display alone. This is what we did since day one (and yes, \n is a special case), and I'd rather we didn't change that just in the name of consistency.