From: Mauro Aranda <maurooaranda@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Glenn Morris <rgm@gnu.org>,
15925@debbugs.gnu.org, claudio.bley@googlemail.com
Subject: bug#15925: 24.3.50; error when customizing whitespace-display-mappings
Date: Wed, 23 Sep 2020 12:26:39 -0300 [thread overview]
Message-ID: <CABczVweQk+Jiiix62mS49n1zoHNn-6uifOEB1H4==EKNSV970g@mail.gmail.com> (raw)
In-Reply-To: <87a6xgd2rw.fsf@gnus.org>
[-- Attachment #1: Type: text/plain, Size: 941 bytes --]
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Mauro Aranda <maurooaranda@gmail.com> writes:
>
>> I attach a patch that should fix this (but that does not change the
>> way the characters are displayed) and that doesn't introduce the
>> breakage of Bug#3136 (for which I added a test).
>
> Thanks; applied to Emacs 28.
Thank you.
> The bits that remains to be fixed here is the display of the TAB/newline
> (etc.) characters?
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.
[-- Attachment #2: Type: text/html, Size: 1183 bytes --]
next prev parent reply other threads:[~2020-09-23 15:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 7:37 bug#15925: 24.3.50; error when customizing whitespace-display-mappings Claudio Bley
2013-11-19 8:24 ` Glenn Morris
2013-11-20 10:35 ` Claudio Bley
2013-11-20 19:28 ` Stefan Monnier
2020-09-22 15:42 ` Mauro Aranda
2020-09-23 13:46 ` Lars Ingebrigtsen
2020-09-23 15:26 ` Mauro Aranda [this message]
2020-09-24 14:38 ` Lars Ingebrigtsen
2020-09-24 15:29 ` Mauro Aranda
2020-09-24 15:36 ` Mauro Aranda
2020-09-25 10:00 ` Lars Ingebrigtsen
2020-09-25 11:06 ` Eli Zaretskii
2020-09-25 11:10 ` Mauro Aranda
2020-09-25 14:32 ` Mauro Aranda
2020-09-26 13:24 ` Lars Ingebrigtsen
2020-09-26 13:26 ` Lars Ingebrigtsen
2020-09-26 13:45 ` Mauro Aranda
2020-09-26 15:10 ` Lars Ingebrigtsen
[not found] <<87mwl0vo36.wl%claudio.bley@gmail.com>
[not found] ` <<CABczVwdS5QJkQh1+GBBoDB4WDtSCCOJRF48whp+it0TyJ1x23Q@mail.gmail.com>
[not found] ` <<87a6xgd2rw.fsf@gnus.org>
[not found] ` <<CABczVweQk+Jiiix62mS49n1zoHNn-6uifOEB1H4==EKNSV970g@mail.gmail.com>
[not found] ` <<871rirb5ot.fsf@gnus.org>
[not found] ` <<CABczVweW=gbepHOLzBQZbAxS9yX-Fo3h2_hPDL7FwmhfjAdk6w@mail.gmail.com>
[not found] ` <<87ft76rxaw.fsf@gnus.org>
[not found] ` <<83v9g2ru8f.fsf@gnu.org>
2020-09-25 16:07 ` Drew Adams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABczVweQk+Jiiix62mS49n1zoHNn-6uifOEB1H4==EKNSV970g@mail.gmail.com' \
--to=maurooaranda@gmail.com \
--cc=15925@debbugs.gnu.org \
--cc=claudio.bley@googlemail.com \
--cc=larsi@gnus.org \
--cc=rgm@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).