unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 68446@debbugs.gnu.org, Thamer Mahmoud <thamer.mahmoud@gmail.com>
Subject: bug#68446: 29.1.90; Bidi right-to-left paragraphs missing text in Org mode
Date: Sun, 14 Jan 2024 12:11:03 +0000	[thread overview]
Message-ID: <87zfx8ru7c.fsf@localhost> (raw)
In-Reply-To: <834jfgf984.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org> writes:

>> 1. In emacs -Q, create an empty buffer with Org mode active and type:
>> 
>> a [[link]]
>> 
>> 2. Evaluate: (setq bidi-paragraph-direction 'right-to-left)
>> 3. Note the "a" and link are no longer visible.
>
> I think it's an Org bug: it should prevent bidi reordering inside the
> "[[link]]" string.  For example, wrap the "[[link]]" thing in LRO..PDF
> bidi controls.  Because without that, the brackets can be mirrored by
> bidi reordering and the BPA algorithm, and the link is no longer in
> the form that Org expects.  The result is that the entire text becomes
> invisible.

May you please elaborate? I do not see anything unexpected in the text
properties that Org mode applies to the link and the letter "a".

In fact, after following the reproducer, and enabling visible-mode, M-x
describe-text-properties on "a" yields

    Text content at position 101:
    
    
    There are text properties here:
      fontified            t

Yet, "a" is rendered invisible.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>





  reply	other threads:[~2024-01-14 12:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-14 10:21 bug#68446: 29.1.90; Bidi right-to-left paragraphs missing text in Org mode Thamer Mahmoud
2024-01-14 11:24 ` Eli Zaretskii
2024-01-14 12:11   ` Ihor Radchenko [this message]
2024-01-14 13:00     ` Eli Zaretskii
2024-01-14 14:41       ` Ihor Radchenko
2024-01-14 14:58         ` Eli Zaretskii
2024-02-04  9:51           ` Eli Zaretskii
2024-02-04 13:10             ` Ihor Radchenko
2024-02-04 13:43               ` 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=87zfx8ru7c.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=68446@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=thamer.mahmoud@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).