From: Juri Linkov <juri@linkov.net>
To: Artur Malabarba <bruce.connor.am@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: On the masking of undisplayable characters
Date: Tue, 07 Jul 2015 02:07:36 +0300 [thread overview]
Message-ID: <87381051hj.fsf@mail.linkov.net> (raw)
In-Reply-To: <CAAdUY-L+RkaP1KMhZgb+EZbqd5_aSZDRVKgvAfPacwLo=ce4Kw@mail.gmail.com> (Artur Malabarba's message of "Mon, 6 Jul 2015 20:57:08 +0100")
>> Emacs always
>> displayed special characters specially. Think about the ^X control
>> characters,
>
> That's fine. When I see a blue ^X, I know that's a control character, it's
> very clear that it's not a ^ with an X.
Highlighted using the ‘escape-glyph’ face.
>> the glyphless-char-display feature,
The ‘glyphless-char’ face.
>> composed characters,
>
> You mean like a non-spacing ` and a looking like an à? The non-spacing
> characters are specifically designed to do that, it's not the same as
> displaying one quote as another quote.
Another face intended to highlight confusable characters is ‘nobreak-space’.
But note how ‘gnus-article-mode’ uses
(set (make-local-variable 'nobreak-char-display) nil)
to prevent Gnus from displaying non-break space with `nobreak-space' face
because usually in view modes users don't want displaying special characters
specially.
>> even the newline.
>
> You mean that \n and \r\n are displayed the same way? Yeah, I've been bit
> several times by it, but at least it's indicated in the mode line.
I've been bit more by indicating different codings in the mode line
with the same code letter, e.g. using the same letter ‘U’ for
utf-8, utf-16le, utf-16be, etc. Better would be to display coding systems
as full names but this makes the mode line wider.
next prev parent reply other threads:[~2015-07-06 23:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 17:38 On the masking of undisplayable characters bruce.connor.am
2015-07-06 18:16 ` Eli Zaretskii
2015-07-06 19:57 ` Artur Malabarba
2015-07-06 23:07 ` Juri Linkov [this message]
2015-07-07 2:44 ` Eli Zaretskii
2015-07-07 14:53 ` Eli Zaretskii
2015-07-07 2:43 ` Eli Zaretskii
2015-07-07 9:32 ` Artur Malabarba
2015-07-07 12:17 ` Yuri Khan
2015-07-07 12:29 ` Artur Malabarba
2015-07-07 13:14 ` Yuri Khan
2015-07-07 13:23 ` Artur Malabarba
2015-07-20 11:02 ` N. Jackson
2015-07-07 15:51 ` Stefan Monnier
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=87381051hj.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=bruce.connor.am@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).