unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Will Parsons <varro@nodomain.invalid>
To: help-gnu-emacs@gnu.org
Subject: Making a non-ASCII space character visible
Date: Sat, 16 Jun 2018 16:15:59 -0400	[thread overview]
Message-ID: <fol9fvF7uauU1@mid.individual.net> (raw)

I have a desire to use the Unicode character A007 (FIGURE SPACE) in a
document and to be able to distinguish it visually from a regular ASCII
space.  This seems to be already done in the case of 00A0 (NO-BREAK
SPACE) which appears as an underscore with a distinctive face.

It *looks* like I should be able to do this via the customization
option "Whitespace Display Mappings", but no matter what I do,
attempting to "Apply" the changes results in an error message, "This
field should contain a single character".  (This message occurs even
if I try to change one of the display characters of an existing entry
in the list and apply.)

Feeling desperate, I copied the existing value of
whitespace-display-mappings directly into my custom.el file, and
manually added a new entry for A007 (8199) on the model of the
existing entry for 00A0 (160), but this seems to have no effect on the
display.

(This is using Emacs 25, in case it should make a difference.)

-- 
Will


             reply	other threads:[~2018-06-16 20:15 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-16 20:15 Will Parsons [this message]
2018-06-16 21:37 ` Making a non-ASCII space character visible Will Parsons
2018-06-17  4:31   ` Marcin Borkowski
2018-06-17  5:07 ` Michael Heerdegen
2018-06-17  5:55   ` Eli Zaretskii
2018-06-17  6:24     ` Michael Heerdegen
2018-06-17  6:41       ` Eli Zaretskii
2018-06-17  6:41       ` Michael Heerdegen
     [not found]       ` <mailman.2115.1529217694.1292.help-gnu-emacs@gnu.org>
2018-06-19  0:45         ` Will Parsons
2018-06-19  1:01           ` Noam Postavsky
     [not found]           ` <mailman.2220.1529370113.1292.help-gnu-emacs@gnu.org>
2018-06-19  1:26             ` Will Parsons
     [not found]   ` <mailman.2110.1529214934.1292.help-gnu-emacs@gnu.org>
2018-06-17 18:54     ` Will Parsons
2018-06-17  6:00 ` Eli Zaretskii
     [not found] ` <mailman.2111.1529215267.1292.help-gnu-emacs@gnu.org>
2018-06-17 18:38   ` Will Parsons
2018-06-17 18:51     ` Eli Zaretskii
     [not found]     ` <mailman.2145.1529261474.1292.help-gnu-emacs@gnu.org>
2018-06-17 19:09       ` Will Parsons
2018-06-17 19:31         ` Eli Zaretskii
     [not found]         ` <mailman.2147.1529263896.1292.help-gnu-emacs@gnu.org>
2018-06-17 20:28           ` Will Parsons
2018-06-18  1:40             ` Nick Helm
     [not found]             ` <mailman.2154.1529286048.1292.help-gnu-emacs@gnu.org>
2018-06-19  0:12               ` Will Parsons
2018-06-19  2:30                 ` Nick Helm
     [not found]                 ` <mailman.2227.1529375463.1292.help-gnu-emacs@gnu.org>
2018-06-20 21:05                   ` Will Parsons
     [not found] ` <mailman.2107.1529212061.1292.help-gnu-emacs@gnu.org>
2018-06-17 18:45   ` Will Parsons
     [not found] <<fol9fvF7uauU1@mid.individual.net>
     [not found] ` <<fole90F986vU1@mid.individual.net>
2018-06-17  0:20   ` 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=fol9fvF7uauU1@mid.individual.net \
    --to=varro@nodomain.invalid \
    --cc=gyliamos@gmail.com \
    --cc=help-gnu-emacs@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.
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).