From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.bugs Subject: bug#14574: prog-prettify-symbols breaks font-locking Date: Mon, 17 Jun 2013 18:24:11 +0200 Message-ID: References: <8338sjusds.fsf@gnu.org> <838v29tpz3.fsf@gnu.org> <837ghsu6it.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1371486371 3320 80.91.229.3 (17 Jun 2013 16:26:11 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 17 Jun 2013 16:26:11 +0000 (UTC) Cc: 14574@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Jun 17 18:26:09 2013 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1UocFr-0007eI-Bh for geb-bug-gnu-emacs@m.gmane.org; Mon, 17 Jun 2013 18:26:07 +0200 Original-Received: from localhost ([::1]:45874 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UocFq-0001hx-VA for geb-bug-gnu-emacs@m.gmane.org; Mon, 17 Jun 2013 12:26:06 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:55128) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UocFo-0001hq-Gp for bug-gnu-emacs@gnu.org; Mon, 17 Jun 2013 12:26:05 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1UocFn-0002YO-Ec for bug-gnu-emacs@gnu.org; Mon, 17 Jun 2013 12:26:04 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:56649) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1UocFn-0002YJ-AI for bug-gnu-emacs@gnu.org; Mon, 17 Jun 2013 12:26:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1UocFm-0006fb-Fu for bug-gnu-emacs@gnu.org; Mon, 17 Jun 2013 12:26:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Juanma Barranquero Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 17 Jun 2013 16:26:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 14574 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 14574-submit@debbugs.gnu.org id=B14574.137148630225488 (code B ref 14574); Mon, 17 Jun 2013 16:26:02 +0000 Original-Received: (at 14574) by debbugs.gnu.org; 17 Jun 2013 16:25:02 +0000 Original-Received: from localhost ([127.0.0.1]:50964 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1UocEm-0006co-Hf for submit@debbugs.gnu.org; Mon, 17 Jun 2013 12:25:01 -0400 Original-Received: from mail-ee0-f51.google.com ([74.125.83.51]:51530) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1UocEj-0006cE-Mg for 14574@debbugs.gnu.org; Mon, 17 Jun 2013 12:24:58 -0400 Original-Received: by mail-ee0-f51.google.com with SMTP id e52so1963203eek.10 for <14574@debbugs.gnu.org>; Mon, 17 Jun 2013 09:24:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=6GR44vzY8meT+gsR4kzkJz5utQff8QKdev/h16FIWnM=; b=vjdNA2c+oACMlcdUq2pxT7cLH41s7m49Gyxskp6FWEf0cwLRLwRV0TpSdC4Qpk7a0v JVUIoRvYxE+YYUJRVEqOlwjpNoxGcmKoUcspVUR3Qpjx4jzQAqiwMAsNflD4tm6R/Tt6 hrTVD91euJIw+Y7ZRTKkyo2lugyNU3OcoJohqhxnTQUtu0tTRFzxSpTZIhsjGsq9X4th bRebgm+cldOfi8uKGrYfC6QeZbOfrXx8JcUlQRP32avCOvDnBeNTvG1EmFR8ukLPFzQY uA/qFnV8pJWanXEaXvH9+nyB4HF4XW+w2zjCxOmhMxHkK6vvAaVmpkxFIzWKyWOXttcz ovCw== X-Received: by 10.14.213.135 with SMTP id a7mr16528202eep.152.1371486291990; Mon, 17 Jun 2013 09:24:51 -0700 (PDT) Original-Received: by 10.14.142.4 with HTTP; Mon, 17 Jun 2013 09:24:11 -0700 (PDT) In-Reply-To: <837ghsu6it.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:75257 Archived-At: On Mon, Jun 17, 2013 at 5:00 PM, Eli Zaretskii wrote: > Arabic uses automatic compositions, not static compositions produced > by text properties. If you want to see which scripts use the > 'composition' properties, search Lisp files for compose-region. Ethiopic, indian languages, Lao, Thai, Tibetan and Tai languages, currently. > Perhaps Handa-san could tell if having 'composition' properties in > comments and strings is something that can happen in real life for > some scripts used in those comments/strings. If it can (and I don't > know one way or the other), then I don't think we should remove all of > the 'composition' properties just because font-lock was turned off. I don't disagree (or at least, not strongly), but I think is an unlikely problem because, as I said, the set of conditions under which can happen is not that big. Currently only Perl (but not Cperl), (e)lisp and CFEngine buffers will be affected, and only if the user choses to enable prettification, which is off by default. And then s/he would have to need to turn off font-locking, which I don't think it is really a common operation while editing code, is it? So it seems to me like we have a two line fix for 95% of use cases (were 95% is a number just invented out of thin air, but you catch my meaning), where covering 100% of cases is likely to be much more complex. > You assume that representatives of affected communities track Emacs > development. But that assumption is not really guaranteed to be true. No, I'm assuming that we usually go for fixing real problems versus perceived ones. Even if we are mistaken and the affected communities discover after the fact, is not like there are no workarounds or we cannot implement a 100% fix later. But don't take that as that I'm opposing a better fix. I'm not. I just don't see the point yet. J