From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: highlighting non-ASCII characters Date: Tue, 23 Mar 2010 20:45:48 -0400 Message-ID: References: <87sk7vllgj.fsf@mail.jurta.org> <87hbo81onq.fsf@lifelogs.com> <87k4t4zb5l.fsf@lifelogs.com> <87r5ncxp4z.fsf@lifelogs.com> <87hbo8tf4i.fsf@turtle.gmx.de> <87hbo8xis5.fsf@lifelogs.com> <87aau0t7uy.fsf@turtle.gmx.de> <87sk7svyam.fsf@lifelogs.com> <87vdcngws4.fsf@mail.jurta.org> <8739zryv6l.fsf_-_@lifelogs.com> <6932BBFEB09A4BA09156ED7F598569CE@us.oracle.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: dough.gmane.org 1269391575 29665 80.91.229.12 (24 Mar 2010 00:46:15 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 24 Mar 2010 00:46:15 +0000 (UTC) Cc: 'Ted Zlatanov' , emacs-devel@gnu.org To: "Drew Adams" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Mar 24 01:46:11 2010 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1NuEjS-0000In-NI for ged-emacs-devel@m.gmane.org; Wed, 24 Mar 2010 01:46:10 +0100 Original-Received: from localhost ([127.0.0.1]:45235 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NuEjR-0006WY-Jq for ged-emacs-devel@m.gmane.org; Tue, 23 Mar 2010 20:46:01 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NuEjM-0006WT-Mh for emacs-devel@gnu.org; Tue, 23 Mar 2010 20:45:56 -0400 Original-Received: from [140.186.70.92] (port=35357 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NuEjK-0006WI-Si for emacs-devel@gnu.org; Tue, 23 Mar 2010 20:45:55 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1NuEjJ-0002Gv-3U for emacs-devel@gnu.org; Tue, 23 Mar 2010 20:45:54 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:11651 helo=ironport2-out.pppoe.ca) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1NuEjJ-0002Gn-1F for emacs-devel@gnu.org; Tue, 23 Mar 2010 20:45:53 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AvsEAGr9qEvO+IPa/2dsb2JhbACbJnS/GIR9BIsZ X-IronPort-AV: E=Sophos;i="4.51,298,1267419600"; d="scan'208";a="58929683" Original-Received: from 206-248-131-218.dsl.teksavvy.com (HELO ceviche.home) ([206.248.131.218]) by ironport2-out.pppoe.ca with ESMTP; 23 Mar 2010 20:45:48 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id 02A0B660BF; Tue, 23 Mar 2010 20:45:49 -0400 (EDT) In-Reply-To: <6932BBFEB09A4BA09156ED7F598569CE@us.oracle.com> (Drew Adams's message of "Tue, 23 Mar 2010 14:53:17 -0700") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:122581 Archived-At: >> > In my case, I customize `escape-glyph' to be something very >> > noticeable (orange background, with blue foreground and >> > 1-pixel blue box). I want to see something like ^G really >> > stand out. I don't want to see >> > non-ascii chars handled the same way. >> Actually, in the original case (a weird non-ASCII K in the middle of >> ASCII text), I would want it to stand out. The problem there >> is how to define "weird". > Whether you want non-ASCII chars to also stand out is a separate > question. My point is that I don't want to see them handled _the same > way_ as ^G et compagnie. What I'm saying is that there are two issues: non-ASCII chars in general (which I personally don't want to display in any special manner: they're just as normal as ASCII chars), and then there are "chars that are out of place or that may not be what they look like", such as the weird "K" in the other message's "OK" (which to me, is similar to the NBSP char in that it is meant to be displayed in the same way as some other char, so we want to call the attention of the user to the difference). > Having separate faces lets users get the behavior they want. If you > then want to customize the two faces to look the same, no problem. I don't insist on using escape-glyph for those chars, indeed (I don't really care which face is used for them). What I care about is figuring out how to define programmatically "chars that are out of place or that may not be what they look like". Stefan