From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: bidi-display-reordering is now non-nil by default Date: Tue, 16 Aug 2011 09:54:18 +0200 Organization: Organization?!? Message-ID: <87y5yt94gl.fsf@fencepost.gnu.org> 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> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: dough.gmane.org 1313481285 4104 80.91.229.12 (16 Aug 2011 07:54:45 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Tue, 16 Aug 2011 07:54:45 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Aug 16 09:54:42 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 1QtETx-0007IU-7H for ged-emacs-devel@m.gmane.org; Tue, 16 Aug 2011 09:54:41 +0200 Original-Received: from localhost ([::1]:58340 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QtETw-0002sK-NU for ged-emacs-devel@m.gmane.org; Tue, 16 Aug 2011 03:54:40 -0400 Original-Received: from eggs.gnu.org ([140.186.70.92]:58650) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QtETu-0002sE-JI for emacs-devel@gnu.org; Tue, 16 Aug 2011 03:54:39 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QtETt-0004ZF-7H for emacs-devel@gnu.org; Tue, 16 Aug 2011 03:54:38 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:48175) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QtETt-0004ZA-29 for emacs-devel@gnu.org; Tue, 16 Aug 2011 03:54:37 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1QtETo-0007CM-FX for emacs-devel@gnu.org; Tue, 16 Aug 2011 09:54:32 +0200 Original-Received: from p508ed6da.dip.t-dialin.net ([80.142.214.218]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 16 Aug 2011 09:54:32 +0200 Original-Received: from dak by p508ed6da.dip.t-dialin.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 16 Aug 2011 09:54:32 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 26 Original-X-Complaints-To: usenet@dough.gmane.org X-Gmane-NNTP-Posting-Host: p508ed6da.dip.t-dialin.net X-Face: 2FEFf>]>q>2iw=B6, xrUubRI>pR&Ml9=ao@P@i)L:\urd*t9M~y1^:+Y]'C0~{mAl`oQuAl \!3KEIp?*w`|bL5qr,H)LFO6Q=qx~iH4DN; i"; /yuIsqbLLCh/!U#X[S~(5eZ41to5f%E@'ELIi$t^ Vc\LWP@J5p^rst0+('>Er0=^1{]M9!p?&:\z]|;&=NP3AhB!B_bi^]Pfkw User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) Cancel-Lock: sha1:qt3yqCBsG77EA95FilEYQCG+xqc= X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-Received-From: 80.91.229.12 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:143287 Archived-At: Andreas Schwab writes: > Eli Zaretskii writes: > >> Translated into Emacs-speak, this means we need a variable that, when >> bound to some special value, instructs the reordering engine to treat >> certain characters as segment separators. > > They already exist: comment-start and comment-end, for example. I am having a somewhat hard time imagining it as a good thing if Emacs displays source code that does no longer correspond to a reasonably straightforward manner of printing the file. reordering source into something that "makes more sense" seems quite more invasive than mere font-locking. I am not fond of the idea of writing code that gets unreadable unless you read it back with Emacs, or even a specific version of Emacs or specific settings. It may partly be the problem space of the language specification: something like HTML should likely give ways of using of directional marks as source formatting aids without affecting the content payload. -- David Kastrup