From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Mauro Aranda Newsgroups: gmane.emacs.bugs Subject: bug#15925: 24.3.50; error when customizing whitespace-display-mappings Date: Thu, 24 Sep 2020 12:29:12 -0300 Message-ID: References: <87mwl0vo36.wl%claudio.bley@gmail.com> <87a6xgd2rw.fsf@gnus.org> <871rirb5ot.fsf@gnus.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="0000000000006f1f5405b010ddb5" Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32031"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Glenn Morris , 15925@debbugs.gnu.org, claudio.bley@googlemail.com To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Thu Sep 24 18:07:53 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 1kLTmi-0008D1-Ev for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 24 Sep 2020 18:07:52 +0200 Original-Received: from localhost ([::1]:42888 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kLTmh-00043g-FU for geb-bug-gnu-emacs@m.gmane-mx.org; Thu, 24 Sep 2020 12:07:51 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49878) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kLTC6-0003YF-Rw for bug-gnu-emacs@gnu.org; Thu, 24 Sep 2020 11:30:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:58017) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kLTC6-0005v0-Cg for bug-gnu-emacs@gnu.org; Thu, 24 Sep 2020 11:30:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1kLTC6-0005o6-8y for bug-gnu-emacs@gnu.org; Thu, 24 Sep 2020 11:30:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Mauro Aranda Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Thu, 24 Sep 2020 15:30: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.160096137522270 (code B ref 15925); Thu, 24 Sep 2020 15:30:02 +0000 Original-Received: (at 15925) by debbugs.gnu.org; 24 Sep 2020 15:29:35 +0000 Original-Received: from localhost ([127.0.0.1]:41330 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kLTBe-0005n7-Pn for submit@debbugs.gnu.org; Thu, 24 Sep 2020 11:29:35 -0400 Original-Received: from mail-wr1-f41.google.com ([209.85.221.41]:41560) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1kLTBb-0005mq-Ql for 15925@debbugs.gnu.org; Thu, 24 Sep 2020 11:29:32 -0400 Original-Received: by mail-wr1-f41.google.com with SMTP id w5so4284051wrp.8 for <15925@debbugs.gnu.org>; Thu, 24 Sep 2020 08:29:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GVhshDFRy3bH64qSagqTGm0L5UwqccwKwrw/Ltk+mbU=; b=qr6ClOS6ocVOcW0hYA5xh/BN2RXDFW4UAGaPKqq1P9rqpn/DwisGmHOXlnS+1pp5Nx Cz71+VOYdpCdYSdnG0dq1wYVMvL3GxJT0A70tv2CmJ5Sh01yn73Tvytx6rE10Pr9/NoC tLIcFYwLdUZTFjFr0Mr+aIgvmes8pplRa3GMo1N29rfmumfmgwrpXCWNNgx7//yOumnc YGSNm4r53+qfIOLjHiJB6AoDgYPV7WIf+4pxp3dyTeJCSXJkdoUV9/Qc9R7ZfKQZEEZP 8s2FG74W/CWzyfvUO72E+jZO6crr1+EilX1FKCdud1Z7W+81jhmEFhn9jPGwB3b2pcpr /AIA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GVhshDFRy3bH64qSagqTGm0L5UwqccwKwrw/Ltk+mbU=; b=e+TcD0X0m7nkpKhPLbwYITwKOfRMYN+hTEArYYGYUhSyC+5wWKuICIxOqWhqWzlOod 9KDt3NjeCGEpqUA3acngm+gwBLFSPQ8w1iKem4H/xAG59Qs2KgeCGFNdapjdYrA8Bex0 3hlAN1ORVvHjHedrQU4P/OxqJ+wuoT9In8bui1len3ssO18w3ZSUDcgQmoBBM+YOKh8s L7UAqp0Rs8Pz5M9Q3v4O+u1yIvqlo6/RwkudWybCZ8Bsf2Z/mNpnCawetFJCmn1jX4Jy 1or4XV3q1NIkjzEyXtxXvQgh0rRpjOPsOZOKIYajxDsAefVYW/v1rXXNtvRVuYzLtxQL xkSA== X-Gm-Message-State: AOAM5309xbN0+haGNAi4WA6IK76ezSN1N7XiarO+XMuwlls/PComV1li Zd8PhkqKW0nrxKCkcv7LkItJcUuU1lqntFfykbs= X-Google-Smtp-Source: ABdhPJwFbHSR6k42sGhQoGPbiTv9Lkf52zXPXDSmDN8l8acmMs4/tw2V2CCLvl2TQ5b6QwLZ7YnvEds1KbnJGtbrFVM= X-Received: by 2002:adf:f290:: with SMTP id k16mr385067wro.124.1600961364564; Thu, 24 Sep 2020 08:29:24 -0700 (PDT) In-Reply-To: <871rirb5ot.fsf@gnus.org> 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:188873 Archived-At: --0000000000006f1f5405b010ddb5 Content-Type: text/plain; charset="UTF-8" Lars Ingebrigtsen writes: > Mauro Aranda writes: > >> Yes. I think there were two suggestions, which if I'm not mistaken can >> be summarized as: >> - Display newline as \n, tab as \t, etc. >> - Display newline as C-j (or ?\\C-j, or \\C-j, etc), tab as C-i, etc. >> >> To those suggestions, I add one of mine: >> - Display newline as ^J, tab as ^I, etc. >> >> That is what Isearch does, and I think it would not be much of a >> trouble to implement that. Furthermore, we already display other >> non-printable characters like that, so my suggestion would just >> change newline and tab, I think. > > Isearch is a bit special here (being interactive)... > > My guess is that more people understand that \n is newline than people > remember that ^J is newline. (The same goes for \t/^I, but probably to > a lesser degree.) Those are good points. A couple of questions: - Do we change the display for the space character as well? We could display it as ?\s, or leave it as " ", which makes the character widget appear empty, when it's not. - 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. --0000000000006f1f5405b010ddb5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Lars Ingebrigtsen <la= rsi@gnus.org> writes:

> Mauro Aranda <maurooaranda@gmail.com> writes:
>
= >> Yes.=C2=A0 I think there were two suggestions, which if I'm no= t mistaken can
>> be summarized as:
>> - Display newline = as \n, tab as \t, etc.
>> - Display newline as C-j (or ?\\C-j, or = \\C-j, etc), tab as C-i, etc.
>>
>> To those suggestions,= I add one of mine:
>> - Display newline as ^J, tab as ^I, etc.>>
>> That is what Isearch does, and I think it would not b= e much of a
>> trouble to implement that.=C2=A0 Furthermore, we al= ready display other
>> non-printable characters like that, so my s= uggestion would just
>> change newline and tab, I think.
>> Isearch is a bit special here (being interactive)...
>
>= My guess is that more people understand that \n is newline than people
= > remember that ^J is newline. =C2=A0(The same goes for \t/^I, but proba= bly to
> a lesser degree.)

Those are good points.=C2=A0 A coup= le of questions:
- Do we change the display for the space character as w= ell?

We could display it as ?\s, or leave it as " ", which= makes the
character widget appear empty, when it's not.

- Wh= at do we do with the other escape sequences, like ?\r and ?\f?

Right= now, we display those as ^M and ^L respectively.=C2=A0 If we keep this
= representation, maybe somebody will feel there is some inconsistency,
be= cause some characters we display as ^M, while others as \n.=C2=A0 Perhapsis not a big deal, though.
--0000000000006f1f5405b010ddb5--