emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dov Grobgeld <dov.grobgeld@gmail.com>
Cc: 11710@debbugs.gnu.org
Subject: bug#11710: 24.1.50; Bidi attributes are not exported in org-mode html output
Date: Fri, 15 Jun 2012 10:55:44 +0300	[thread overview]
Message-ID: <83pq91f1q7.fsf__42706.2434413985$1339746994$gmane$org@gnu.org> (raw)
In-Reply-To: <CA++fsGEeiz7E3n7FpdYOceEeKsxX5WZr-ZKH_qFzF86t9eh29w@mail.gmail.com>

> Date: Fri, 15 Jun 2012 09:17:36 +0300
> From: Dov Grobgeld <dov.grobgeld@gmail.com>
> Cc: 11710@debbugs.gnu.org
> On Thu, Jun 14, 2012 at 10:42 PM, Eli Zaretskii
> > > [stuff deleted]
> >
> > Did you customize Emacs to dynamically determine the paragraph
> > direction in Org buffers?  By default they are forced to be
> > left-to-right.
> Yes, I changed that. Org-mode appears to me to work fine in dynamic
> Bidi mode, so I don't understand the reasoning that it was turned off
> by default.

2 reasons:

 . If you maintain Org files with mixed L2R and R2L contents, having
   some items on the left and some on the right looks messed up,
   especially if the parent item is on the other side of the window.

 . Performance.  Dynamic detection of paragraph direction can slow
   down redisplay, if you have long stretches of items without empty
   lines to separate them.  When sub-trees are hidden, this could
   cause an annoying effect whereby moving cursor past one visible
   line causes a perceptible delay (because there are many hundreds of
   hidden lines Emacs needs to move through in the buffer).  This
   punishes Org users who don't use bidirectional scripts, which are
   the majority of Org users.  So in traditions of democracy, the
   majority wins...

> >  (save-excursion
> >    (goto-char N)
> >    (current-bidi-paragraph-direction))
> Ok, thanks. Perhaps I'll have a go at it on my own.

Please consider reporting here if you get it to work, because Org
maintainers may wish to use your code.


  parent reply	other threads:[~2012-06-15  7:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CA++fsGGSgAUPUGuy6n=G0xB=7oHa3MHuDy+CxOnoNPAae3i+ug@mail.gmail.com>
2012-06-14 19:42 ` Eli Zaretskii
     [not found] ` <8362aty921.fsf@gnu.org>
2012-06-15  6:17   ` Dov Grobgeld
     [not found]   ` <CA++fsGEeiz7E3n7FpdYOceEeKsxX5WZr-ZKH_qFzF86t9eh29w@mail.gmail.com>
2012-06-15  7:55     ` Eli Zaretskii [this message]
2020-05-22 11:41 ` bug#11710: Status: " Bastien

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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to='83pq91f1q7.fsf__42706.2434413985$1339746994$gmane$org@gnu.org' \
    --to=eliz@gnu.org \
    --cc=11710@debbugs.gnu.org \
    --cc=dov.grobgeld@gmail.com \


* 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


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).