From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: bidi-display-reordering is now non-nil by default Date: Thu, 18 Aug 2011 18:44:44 -0400 Message-ID: <87vctuz6eb.fsf@stupidchicken.com> References: <4E48D309.6050503@acdlabs.ru> <83hb5jujjs.fsf@gnu.org> <874o1j10zv.fsf@fencepost.gnu.org> <8362lyvcli.fsf@gnu.org> <87fwl2r0l4.fsf@stupidchicken.com> <83zkjatnkz.fsf@gnu.org> <877h6et8oi.fsf@stupidchicken.com> <83vctxua2y.fsf@gnu.org> <87r54le4rd.fsf@stupidchicken.com> <8362lxtfeb.fsf@gnu.org> <87d3g56llz.fsf@stupidchicken.com> <8339h0tur0.fsf@gnu.org> <87ippvwtwx.fsf@stupidchicken.com> <83liurruz4.fsf@gnu.org> <87k4aaej7f.fsf@stupidchicken.com> <83ippusjej.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1313707498 10680 80.91.229.12 (18 Aug 2011 22:44:58 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Thu, 18 Aug 2011 22:44:58 +0000 (UTC) Cc: monnier@iro.umontreal.ca, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Aug 19 00:44:54 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 1QuBKX-00031d-Ls for ged-emacs-devel@m.gmane.org; Fri, 19 Aug 2011 00:44:53 +0200 Original-Received: from localhost ([::1]:55313 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QuBKX-0005rG-72 for ged-emacs-devel@m.gmane.org; Thu, 18 Aug 2011 18:44:53 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:53603) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QuBKU-0005r0-OI for emacs-devel@gnu.org; Thu, 18 Aug 2011 18:44:51 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QuBKT-00024n-UK for emacs-devel@gnu.org; Thu, 18 Aug 2011 18:44:50 -0400 Original-Received: from vm-emlprdomr-04.its.yale.edu ([130.132.50.145]:57642) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QuBKS-00024P-B3; Thu, 18 Aug 2011 18:44:48 -0400 Original-Received: from furball (dhcp-128-36-14-148.central.yale.edu [128.36.14.148]) (authenticated bits=0) by vm-emlprdomr-04.its.yale.edu (8.14.4/8.14.4) with ESMTP id p7IMijXa005149 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 18 Aug 2011 18:44:46 -0400 In-Reply-To: <83ippusjej.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 18 Aug 2011 20:45:40 +0300") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) X-Scanned-By: MIMEDefang 2.71 on 130.132.50.145 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 130.132.50.145 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:143416 Archived-At: Eli Zaretskii writes: > What's wrong with using the `display' property with a special value, > as I suggested a few mails ago? It _is_ a character property, isn't > it? I'll have to think more about it, but I am not sure it's a good idea. The display property is already used for a lot of other unrelated purposes, like variable-width spaces. So if you want to mark out a bidi segment on a stretch of text that already has other display properties present, you'd currently have to do some nasty merging of display specs. Searching for the bidi display spec would be similarly annoying. It would be much nicer to have a separate text property specifically for the purpose of marking out a bidi segment. >> I don't recall the last time I ran into a problem with deferred >> font-lock. I seriously doubt this is a real issue. > > ??? Set jit-lock-defer-time to something like 2, then visit xdisp.c, > scroll, and watch the fun. Then don't do that. Obviously, there is a trade-off: exploiting font-lock means more "magically correct" segmenting; using a hack (like marking chars special) means less dependence on the font-lock machinery. I don't think the latter is worth it.