From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail
From: Eli Zaretskii <eliz@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: Performance degradation from long lines
Date: Sat, 13 Jul 2019 17:14:01 +0300
Message-ID: <831ryu10pi.fsf@gnu.org>
References: <20190107065207.21793.53271@vcs0.savannah.gnu.org>
 <20190107065208.BA36C21736@vcs0.savannah.gnu.org>
 <jwvpnt4jtax.fsf-monnier+emacsdiffs@gnu.org>
 <16bb3884-c2de-b178-afe8-0b13a8b116a8@orcon.net.nz>
 <jwvfttyextd.fsf-monnier+emacsdiffs@gnu.org>
 <e2d28d85-5fef-b765-a094-32b8ddbd0612@orcon.net.nz>
 <jwv4l70k4pt.fsf-monnier+emacsdiffs@gnu.org>
 <3f78c29c0c7c01e21180be5fe4f9e70a@webmail.orcon.net.nz>
 <11eaa87e-b4e4-2cf8-e9d1-658757b97ffe@orcon.net.nz>
 <d69efd8e-591c-6847-cfe8-4f8bdd51cdfb@orcon.net.nz>
 <83muhi1hoc.fsf@gnu.org>
 <1a2d94be-a73a-7934-4ce8-5b3c4e819645@orcon.net.nz>
 <83d0ie1clx.fsf@gnu.org> <jwvwogmrrk6.fsf-monnier+emacs@gnu.org>
Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226";
	logging-data="258705"; mail-complaints-to="usenet@blaine.gmane.org"
Cc: psainty@orcon.net.nz, mithraeum@protonmail.com, emacs-devel@gnu.org
To: Stefan Monnier <monnier@iro.umontreal.ca>
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Jul 13 16:14:20 2019
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane.org
Original-Received: from lists.gnu.org ([209.51.188.17])
	by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.89)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>)
	id 1hmIn5-0015AF-K5
	for ged-emacs-devel@m.gmane.org; Sat, 13 Jul 2019 16:14:19 +0200
Original-Received: from localhost ([::1]:56458 helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.86_2)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>)
	id 1hmIn3-0006QE-VU
	for ged-emacs-devel@m.gmane.org; Sat, 13 Jul 2019 10:14:17 -0400
Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40968)
 by lists.gnu.org with esmtp (Exim 4.86_2)
 (envelope-from <eliz@gnu.org>) id 1hmIn1-0006P7-7o
 for emacs-devel@gnu.org; Sat, 13 Jul 2019 10:14:16 -0400
Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:34556)
 by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from <eliz@gnu.org>)
 id 1hmIn0-0003qW-0X; Sat, 13 Jul 2019 10:14:14 -0400
Original-Received: from [176.228.60.248] (port=4494 helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256)
 (Exim 4.82) (envelope-from <eliz@gnu.org>)
 id 1hmImz-0007ko-C8; Sat, 13 Jul 2019 10:14:13 -0400
In-reply-to: <jwvwogmrrk6.fsf-monnier+emacs@gnu.org> (message from Stefan
 Monnier on Sat, 13 Jul 2019 09:31:02 -0400)
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org
Original-Sender: "Emacs-devel" <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
Xref: news.gmane.org gmane.emacs.devel:238566
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/238566>

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Sat, 13 Jul 2019 09:31:02 -0400
> Cc: Phil Sainty <psainty@orcon.net.nz>, mithraeum@protonmail.com,
>  emacs-devel@gnu.org
> 
> >> That sounds good to me.  I wasn't aware that nil was an invalid value
> >> for bidi-display-reordering.
> >
> > It isn't invalid.  It is useful for debugging the display code, but
> > using it in production session is dangerous, because it causes the
> > code to execute control-flow paths that aren't supported in
> > general-purpose usage.
> 
> How 'bout we rename it to clarify it. 
> The new name could include "debug", "internal" and/or "--".

And then introduce an alias or it, and maintain those for years?
Doesn't sound worth the hassle.