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: non-breaking hyphens Date: Tue, 18 Oct 2011 09:11:08 -0400 Message-ID: References: <87d3dvg1r5.fsf@gnu.org> <87ehybm0i0.fsf@gnu.org> <83r52buey8.fsf@gnu.org> <87pqhuwli7.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1318943493 14493 80.91.229.12 (18 Oct 2011 13:11:33 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 18 Oct 2011 13:11:33 +0000 (UTC) Cc: Eli Zaretskii , emacs-devel@gnu.org To: Chong Yidong Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Oct 18 15:11:29 2011 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([140.186.70.17]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1RG9S4-0004RM-Fy for ged-emacs-devel@m.gmane.org; Tue, 18 Oct 2011 15:11:28 +0200 Original-Received: from localhost ([::1]:51515 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RG9S3-0008TO-Tq for ged-emacs-devel@m.gmane.org; Tue, 18 Oct 2011 09:11:27 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:50203) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RG9Rx-0008TJ-6Z for emacs-devel@gnu.org; Tue, 18 Oct 2011 09:11:26 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RG9Rw-0005vS-74 for emacs-devel@gnu.org; Tue, 18 Oct 2011 09:11:21 -0400 Original-Received: from ironport2-out.teksavvy.com ([206.248.154.181]:27116 helo=ironport2-out.pppoe.ca) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RG9Rl-0005u8-PT; Tue, 18 Oct 2011 09:11:09 -0400 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: Av0EACx6nU5MCqLO/2dsb2JhbABEqGSBBoFuAQEEAVYjBQsLDiYSFBgNJC6HZbZxiBsEoSqERQ X-IronPort-AV: E=Sophos;i="4.69,365,1315195200"; d="scan'208";a="142684102" Original-Received: from 76-10-162-206.dsl.teksavvy.com (HELO ceviche.home) ([76.10.162.206]) by ironport2-out.pppoe.ca with ESMTP/TLS/ADH-AES256-SHA; 18 Oct 2011 09:11:08 -0400 Original-Received: by ceviche.home (Postfix, from userid 20848) id 72DD5660B6; Tue, 18 Oct 2011 09:11:08 -0400 (EDT) In-Reply-To: <87pqhuwli7.fsf@gnu.org> (Chong Yidong's message of "Tue, 18 Oct 2011 08:08:00 -0400") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 206.248.154.181 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:145298 Archived-At: >>> I'm not sure I understand the goal of `nobreak-char-display'. Is it for >>> warning the user when there is an ASCII look-alike character that isn't >>> really ASCII? I guess that's mainly to avoid issues with source code? >> Yes, probably. But I'm only guessing here. Can you find any traces >> of discussing this in the archives? I do remember it being the result (through various discussions, as you can imagine) of bug reports where a NBSP was accidentally inserted in source code instead of a SPC, which can be difficult to track down. > The right way to implement this feature, as brought up in the 2004 > thread, would be to specify the affected characters with a char-table > rather than hardcoding them. But we should probably leave such a change > till after 24.1. I believe the general solution is along the lines of what the GNU ELPA packae "markchars" does. The current solution was a simple solution for the sub-cases that can happen commonly in programming languages. The reason why it's important to handle programming languages is that visual similarity is not understood by compilers ;-) In contrast for text buffers (or even LaTeX and HTML), it's much less problematic. Also the significant cases are the ones where the similarity is between a "plain ASCII" char and some other one. Stefan