From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Marcin Borkowski Newsgroups: gmane.emacs.help Subject: Re: Making a non-ASCII space character visible Date: Sun, 17 Jun 2018 06:31:40 +0200 Message-ID: <87602ighjn.fsf@mbork.pl> References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: blaine.gmane.org 1529209923 17199 195.159.176.226 (17 Jun 2018 04:32:03 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 17 Jun 2018 04:32:03 +0000 (UTC) User-Agent: mu4e 1.1.0; emacs 27.0.50 Cc: help-gnu-emacs@gnu.org To: gyliamos@gmail.com Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sun Jun 17 06:31:58 2018 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fUPM5-0004Jr-E8 for geh-help-gnu-emacs@m.gmane.org; Sun, 17 Jun 2018 06:31:57 +0200 Original-Received: from localhost ([::1]:53749 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fUPOC-0004vB-9L for geh-help-gnu-emacs@m.gmane.org; Sun, 17 Jun 2018 00:34:08 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46931) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fUPNc-0004v5-Rg for help-gnu-emacs@gnu.org; Sun, 17 Jun 2018 00:33:33 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fUPNZ-0004Bh-Lv for help-gnu-emacs@gnu.org; Sun, 17 Jun 2018 00:33:32 -0400 Original-Received: from mail.mojserwer.eu ([195.110.48.8]:49301) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fUPNZ-0004A6-Eh for help-gnu-emacs@gnu.org; Sun, 17 Jun 2018 00:33:29 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by mail.mojserwer.eu (Postfix) with ESMTP id 393AEE6884; Sun, 17 Jun 2018 06:33:22 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mail.mojserwer.eu Original-Received: from mail.mojserwer.eu ([127.0.0.1]) by localhost (mail.mojserwer.eu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id W99HAM3y_CZe; Sun, 17 Jun 2018 06:33:17 +0200 (CEST) Original-Received: from localhost (static-dwadziewiec-jedenpiec7.echostar.pl [109.232.29.157]) by mail.mojserwer.eu (Postfix) with ESMTPSA id 3CCCDE680E; Sun, 17 Jun 2018 06:33:17 +0200 (CEST) In-reply-to: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 195.110.48.8 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.org gmane.emacs.help:117177 Archived-At: On 2018-06-16, at 23:37, Will Parsons wrote: > On Saturday, 16 Jun 2018 4:15 PM -0400, Will Parsons wrote: >> 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.) > > Correction: FIGURE SPACE is actually 0x2007, not 0xA007, but that's > simply a mistake in my post, not the actual code. (Sorry for not > being more careful.) How about good old M-s h r (highlight-regexp)? Hth, -- Marcin Borkowski http://mbork.pl