From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Miles Bader Newsgroups: gmane.emacs.devel Subject: Re: non-break-space in tutorial Date: Tue, 7 Jun 2005 09:17:45 +0900 Message-ID: References: <87y8a1o9u0.fsf-monnier+emacs@gnu.org> <87acmgubin.fsf@jurta.org> <87ll5yqbya.fsf@jurta.org> <87mzq3r70q.fsf@jurta.org> Reply-To: snogglethorpe@gmail.com, miles@gnu.org NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1118103402 17508 80.91.229.2 (7 Jun 2005 00:16:42 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 7 Jun 2005 00:16:42 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Jun 07 02:16:40 2005 Return-path: Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1DfRlI-0007ZC-Mt for ged-emacs-devel@m.gmane.org; Tue, 07 Jun 2005 02:16:09 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DfRrh-0001TO-Tk for ged-emacs-devel@m.gmane.org; Mon, 06 Jun 2005 20:22:45 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DfRqL-0000zf-FD for emacs-devel@gnu.org; Mon, 06 Jun 2005 20:21:22 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DfRqK-0000yx-EO for emacs-devel@gnu.org; Mon, 06 Jun 2005 20:21:20 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DfRqK-0000ym-81 for emacs-devel@gnu.org; Mon, 06 Jun 2005 20:21:20 -0400 Original-Received: from [64.233.184.196] (helo=wproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DfRq6-0003om-Dx for emacs-devel@gnu.org; Mon, 06 Jun 2005 20:21:06 -0400 Original-Received: by wproxy.gmail.com with SMTP id 40so498117wri for ; Mon, 06 Jun 2005 17:17:45 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Z94Fu4HSmXk40v7rI1jpJpq7QyzVVf5zNCHOXW7FN2oaaicGfOjmWkndlXYMw9MGcPPUZ4UX7PJhJN6amsTEgl72bqRFHSymYGP/yPbsQu47v8qOOsIrcHS6hc2JeyfRrZlSIbEiRyTC9CupGGJ2po4AHZ3f2nKulKSgqOUjo0Y= Original-Received: by 10.54.20.7 with SMTP id 7mr171555wrt; Mon, 06 Jun 2005 17:17:45 -0700 (PDT) Original-Received: by 10.54.19.31 with HTTP; Mon, 6 Jun 2005 17:17:45 -0700 (PDT) Original-To: Juri Linkov In-Reply-To: <87mzq3r70q.fsf@jurta.org> Content-Disposition: inline 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:38208 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:38208 On 6/6/05, Juri Linkov wrote: > After a testing period (say, 1 week) I could remove the variable > `show-non-break'. There seems to be no need for this variable since > highlighting can be disabled by inheriting `no-break-space' face > from the default face. No. This is wrong for several reasons 1) Faces are global, but it's extremely desirable to disable special treatment of NBSP (etc) on a per-buffer basis. So we can't get rid of `show-nonbreak-escape'. 2) The original treatment of NBSP -- displaying it like a normal escape character, with backslash prefix and in the normal escape character face -- is IMO better than your method, so _at the least_ it should be user selectable, but it seems that your patch makes this impossible. [And I personally think it should be the default.] 3) Your patch treats "soft hyphens" in the same way as NBSP, and I'm not sure this is desirable; it at least seems worthy of discussion. Furthermore, we're supposed to be in some sort of pre-release state, so please don't just install changes you _know_ to be controversial without at least mentioning what you're going to do on the mailing list first BTW, something funny I noticed while testing, though I'm not sure whether it is caused by your patch or not, is that when displaying on a tty with `terminal-coding-system' set to nil, both NBSP and soft-hyphen are show as "?". Since most fonts simply display these character in the same way as their non-special brothers, wouldn't be good for emacs to do the translation itself so that they show up ok on simple ascii terminals? -Miles --=20 Do not taunt Happy Fun Ball.