From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gregory Heytings Newsgroups: gmane.emacs.devel Subject: Re: Unicode confusables and reordering characters considered harmful Date: Wed, 03 Nov 2021 17:53:36 +0000 Message-ID: <11d5fecb440de07f9d30@heytings.org> References: <875ytag0hb.fsf@yahoo.com> <87zgqmd5np.fsf@mat.ucm.es> <83wnlqk3rn.fsf@gnu.org> <72dd5c2a-42c7-b12e-05ed-e93adbd89727@gmail.com> <83ilxajyhw.fsf@gnu.org> <83fssejxf8.fsf@gnu.org> <835ytajsv2.fsf@gnu.org> <11d5fecb44af1d388b7f@heytings.org> <11d5fecb449846dc0851@heytings.org> <837ddpicbb.fsf@gnu.org> <11d5fecb442f6eb9e9e3@heytings.org> <83v919gv9a.fsf@gnu.org> <11d5fecb4476ff938838@heytings.org> <83mtmlgmml.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="16439"; mail-complaints-to="usenet@ciao.gmane.io" Cc: cpitclaudel@gmail.com, stefan@marxist.se, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Nov 03 18:54:58 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1miKTR-00042U-M7 for ged-emacs-devel@m.gmane-mx.org; Wed, 03 Nov 2021 18:54:57 +0100 Original-Received: from localhost ([::1]:54992 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1miKTQ-0000Ie-0m for ged-emacs-devel@m.gmane-mx.org; Wed, 03 Nov 2021 13:54:56 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48552) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1miKSE-000662-A3 for emacs-devel@gnu.org; Wed, 03 Nov 2021 13:53:42 -0400 Original-Received: from heytings.org ([95.142.160.155]:51398) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1miKSC-0001mr-43; Wed, 03 Nov 2021 13:53:41 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heytings.org; s=20210101; t=1635962017; bh=Hji4gWtBqkmt9iK3dWvd3Oz+lwVepkwk7OA9OglNQ08=; h=Date:From:To:cc:Subject:In-Reply-To:Message-ID:References:From; b=ZKM7jR1FExDjQaRE2RaN2iC7/R8RkaF8ZCUrA+Cz265y7eueW1m3NGr6ATsawuwt4 ASM/WhGUvQwh5gkXU7722ClcGCuDRXaqCQBpHQ9qTNryvkiw8kKNQyz2BZhpX9BCP6 7OvwEbARYmxpbeiT2tC/z6+FRSvTcbUYhN48YI1e6Yx0kJcK4dQ2zGFHwh8MZR0xFO EIb+Ml3sU20t1QAG8GFRnQWlkIn0CJxhansV9O+BP2ikkI2+4H4zK0Mh/+XNmA5sq5 yI2o+BXumAW14pUqUdBiwrOJlQIl+JEzPlNdLip3QIUiGMYN6xGwoSfZi9aoe968Kp VYT3dZNiIIhsw== In-Reply-To: <83mtmlgmml.fsf@gnu.org> Received-SPF: pass client-ip=95.142.160.155; envelope-from=gregory@heytings.org; helo=heytings.org X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:278595 Archived-At: >>> It could, but I don't think we should install such features. >> >> Why not? > > Because it doesn't pass my quality-control tests. > That's a reason ;-) >> Is this not simply an improved (and built-in) version of your initial >> suggestion to use glyphless-char-display? > > glyphless-char-display already exists and is built-in. People who want > to have these characters stand out for some reason can use it, that's > why it is open to customization. What you propose is "yet another > mechanism similar to glyphless-char-display", and I don't see why we > should have this for a small group of characters. We already have a > small mess because display-tables and glyphless-char-display produce a > race; I certainly don't think we should introduce yet another, third > mechanism for a similar purpose. > I don't really see why this is a third mechanism, buffer-display-table already exists and is built-in, too. Both are char tables. I always thought that glyphless-char-display was more or less the global equivalent of buffer-display-table, but apparently I'm missing something. > I could consider adding an additional METHOD to those we already support > there, if someone thinks the existing ones are insufficient. Not sure if > this is needed, but it at least makes some sense, assuming the proposal > would be reasonable and not limited to a small group of codepoints. > >> Except that glyphless-char-display is global (whereas >> buffer-display-table is buffer-local), and that a tofu is not as >> visible as a character highlighted with the font-lock-warning-face. > > Patches to allow glyphless display to be controlled on a buffer-local > basis would be welcome, I think this would be a good enhancement. >