unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Pip Cet <pipcet@gmail.com>
Cc: 41506@debbugs.gnu.org
Subject: bug#41506: 28.0.50; RTL problem
Date: Tue, 02 Jun 2020 19:34:31 +0300	[thread overview]
Message-ID: <83tuztctpk.fsf@gnu.org> (raw)
In-Reply-To: <CAOqdjBfj26iUjzk4kKAZ45B0C-Dh7xgqqECqmjw-aQY5rTZt9g@mail.gmail.com> (message from Pip Cet on Tue, 2 Jun 2020 10:17:55 +0000)

> From: Pip Cet <pipcet@gmail.com>
> 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.





  reply	other threads:[~2020-06-02 16:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-24 13:05 bug#41506: 28.0.50; RTL problem Pip Cet
2020-05-24 14:46 ` Eli Zaretskii
2020-06-02 10:17   ` Pip Cet
2020-06-02 16:34     ` Eli Zaretskii [this message]
2020-06-02 19:07       ` Eli Zaretskii
2020-06-06  7:58         ` Pip Cet
2020-06-06  8:35           ` Eli Zaretskii
2020-06-06 13:05             ` Pip Cet
2020-06-06 13:45               ` Eli Zaretskii

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83tuztctpk.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=41506@debbugs.gnu.org \
    --cc=pipcet@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).