From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Kenichi Handa Newsgroups: gmane.emacs.devel Subject: Re: Latin-1 non breaking space not highlighted Date: Mon, 22 Apr 2002 10:53:17 +0900 (JST) Sender: emacs-devel-admin@gnu.org Message-ID: <200204220153.KAA13494@etlken.m17n.org> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII X-Trace: main.gmane.org 1019441002 6115 127.0.0.1 (22 Apr 2002 02:03:22 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 22 Apr 2002 02:03:22 +0000 (UTC) Cc: monnier+gnu/emacs@RUM.cs.yale.edu, eliz@is.elta.co.il, rms@gnu.org, ulrich@a0.complang.tuwien.ac.at, emacs-devel@gnu.org Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 16zTAo-0001aW-00 for ; Mon, 22 Apr 2002 04:03:22 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 16zTBI-0006qB-00 for ; Mon, 22 Apr 2002 04:03:53 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16zTAc-0000OG-00; Sun, 21 Apr 2002 22:03:10 -0400 Original-Received: from delysid.gnu.org ([158.121.106.20]) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 16zTA7-0000Nb-00; Sun, 21 Apr 2002 22:02:39 -0400 Original-Received: from tsukuba.m17n.org ([192.47.44.130]) by delysid.gnu.org with smtp (Exim 3.34 #2) id 16zTA4-0005Kz-00; Sun, 21 Apr 2002 22:02:36 -0400 Original-Received: from fs.m17n.org (fs.m17n.org [192.47.44.2]) by tsukuba.m17n.org (8.11.6/3.7W-20010518204228) with ESMTP id g3M1rHw15533; Mon, 22 Apr 2002 10:53:18 +0900 (JST) (envelope-from handa@m17n.org) Original-Received: from etlken.m17n.org (etlken.m17n.org [192.47.44.125]) by fs.m17n.org (8.11.3/3.7W-20010823150639) with ESMTP id g3M1rHM14238; Mon, 22 Apr 2002 10:53:17 +0900 (JST) Original-Received: (from handa@localhost) by etlken.m17n.org (8.8.8+Sun/3.7W-2001040620) id KAA13494; Mon, 22 Apr 2002 10:53:17 +0900 (JST) Original-To: monnier+gnu/emacs@RUM.cs.yale.edu In-Reply-To: "monnier+gnu/emacs@RUM.cs.yale.edu"'s message of Fri, 19 Apr 2002 09:55:11 -0400 User-Agent: SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.2 Emacs/21.1.30 (sparc-sun-solaris2.6) MULE/5.0 (SAKAKI) Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:2970 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:2970 "Stefan Monnier" writes: >> My point is: >> show-trailing-whitespace should not mean highlighting such >> charactes that have "whitespace" SYNTAX, but should mean >> highlighting sucn characters that have "whitespace" GLYPH. > That's a separate issue. Related to whether or not we should > take the display-table into account. In my understanding, the purpose of show-trailing-whitespace is to tell users that there are characters that has space glyphs (thus invisible) at end of line. So, yes, if some characters are displayed by SPCs because of display-table, it is better that we take that info account (although it may require a rather big change in the display engine). Anyway, we should not decide if a character should be highlighted or not simply by its syntax. >> Both sets of characters mostly overlap but not necessarily >> be the same. >> >> For instance, even if I set syntax of NBSP to "word >> constitute", > When would you do that and why (considering that we're specifically > talking about the global standard-syntax-table) ? The above is just an example. I don't mean it's useful. But, hmmm, perhaps, it may be useful for filling. >> show-trailing-whitespace should highlight it. > Really ? I think this very much depends on the answer to the > previous question. I really think NBSP should be highlighted also in such a (hypothetical) situation. What do the other people think? > We really just need a table somewhere that tells us what is whitespace > and what isn't. Currently I think there are two such tables, one is > the standard-syntax-table, the other is the ` ' category. Actually, > I [:space:] and [:blank:] are two more, but [:space:] relies on the > buffer-local syntax-table (i.e. not good, although it's not that bad > since it only uses it for non-ASCII chars, IIRC) and [:blank:] only > matches ASCII chars (i.e. not good either). I have forgotten about ` ' category. Do you know which character has this category and how is that category used? --- Ken'ichi HANDA handa@etl.go.jp