From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#41506: 28.0.50; RTL problem Date: Tue, 02 Jun 2020 19:34:31 +0300 Message-ID: <83tuztctpk.fsf@gnu.org> References: <838shhxuff.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="130702"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 41506@debbugs.gnu.org To: Pip Cet Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jun 02 18:35:10 2020 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1jg9sc-000XtD-Sq for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 02 Jun 2020 18:35:10 +0200 Original-Received: from localhost ([::1]:39158 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jg9sb-0006Jx-S0 for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 02 Jun 2020 12:35:09 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:36188) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jg9sU-0006Is-KR for bug-gnu-emacs@gnu.org; Tue, 02 Jun 2020 12:35:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:57455) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1jg9sU-0001Gd-9M for bug-gnu-emacs@gnu.org; Tue, 02 Jun 2020 12:35:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1jg9sU-0001j4-7A for bug-gnu-emacs@gnu.org; Tue, 02 Jun 2020 12:35:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 02 Jun 2020 16:35:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 41506 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: confirmed Original-Received: via spool by 41506-submit@debbugs.gnu.org id=B41506.15911156976619 (code B ref 41506); Tue, 02 Jun 2020 16:35:02 +0000 Original-Received: (at 41506) by debbugs.gnu.org; 2 Jun 2020 16:34:57 +0000 Original-Received: from localhost ([127.0.0.1]:40768 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jg9sO-0001ig-Mb for submit@debbugs.gnu.org; Tue, 02 Jun 2020 12:34:56 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:56972) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1jg9sN-0001iT-Rh for 41506@debbugs.gnu.org; Tue, 02 Jun 2020 12:34:56 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:47891) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jg9sI-0001FS-Ht; Tue, 02 Jun 2020 12:34:50 -0400 Original-Received: from [176.228.60.248] (port=1555 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1jg9sH-0000sd-K3; Tue, 02 Jun 2020 12:34:50 -0400 In-Reply-To: (message from Pip Cet on Tue, 2 Jun 2020 10:17:55 +0000) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:181413 Archived-At: > From: Pip Cet > Date: Tue, 2 Jun 2020 10:17:55 +0000 > Cc: 41506@debbugs.gnu.org > > > It's a bug, but one that's very tricky to fix, AFAIR. If you insert > > or delete a single character, the display becomes correct. > > The attached patch seems to avoid the problem, but I'm sure I'm > missing something. This condition was added 11 years ago, when I just started integrating bidi.c with Emacs. The commit log message and the comment both say I had some real problem on my hands that this condition fixed. However, I have now thrown several use cases on the patched code, and could see no problem. So I guess whatever issues I had back then were meanwhile solved "by other means", and you should install this patch. If there is indeed some subtlety here, it will present itself sooner or later (like, in another 11 years). > I suspect what might have been meant is that narrowing an LTR > paragraph to a line containing STRONG_R text shouldn't result in RTL > display, but it does... No, this works as designed: the Emacs display engine always behaves as if there's nothing before beginning of the narrowed region. Thanks.