From: Dov Grobgeld <dov.grobgeld@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 11700@debbugs.gnu.org
Subject: bug#11700: [O] bug#11700: 24.1.50; Bad interaction between BiDi and org-tables
Date: Fri, 15 Jun 2012 09:39:35 +0300 [thread overview]
Message-ID: <CA++fsGEZ4hpgYQ=12vnHryS9LJbqycGHnuWs5JN5G0M776p6Gw@mail.gmail.com> (raw)
In-Reply-To: <837gv9y99l.fsf@gnu.org>
On Thu, Jun 14, 2012 at 10:37 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> Date: Thu, 14 Jun 2012 21:10:46 +0300
>> From: Dov Grobgeld <dov.grobgeld@gmail.com>
>> Cc: 11700@debbugs.gnu.org
>> [stuff deleted]
>> I tried inserting tabs into the buffer before the vertical bars, but
>> after reordering it still didn't come out right.
>
> ??? What exactly did you try? You need to have a TAB before and after
> each '|' that's between the cells (the outer ones do not need a TAB).
> Like this (you should see this correctly in Emacs 24.1; move cursor
> with C-f to see the logical order):
>
> | אבגד | הוזחטי |
>
> Isn't this what you wanted?
Yes. Great! This is indeed what I wanted. My mistake was that I tried
it with a tab character before OR after the vertical bar. This
solution should be really simple to implement in org-mode as it means
that instead of joining the table columns with "<space><vbar><space>"
as is currently done, you just need to use "<tab><vbar><tab>" as well
as setting the tab width to 1.
But I just wonder, is there any other character (preferably white
space character) with the same end-of-segment-boundary properties as
tab, in case tab is used for something else in org-mode? Or is it
possible to take an arbitrary character, e.g. U+E0020, and bless it
with end-of-segment boundary properties and then use that in the
org-mode buffer?
As a side note, I really like the idea of end of segment separator,
and I wasn't aware of it when I wrote fribidi a long time ago. I
wonder if the semantics of the emacs segment separator follows the
Unicode Bidi Algorithm?
next prev parent reply other threads:[~2012-06-15 6:39 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 19:26 bug#11700: 24.1.50; Bad interaction between BiDi and org-tables Dov Grobgeld
2012-06-14 3:10 ` Eli Zaretskii
2012-06-14 18:10 ` Dov Grobgeld
[not found] ` <CA++fsGEWbmfgEn1=WVd_HcqxXVySPg0P-SsPzrF2gZ0gu_-0ww@mail.gmail.com>
2012-06-14 19:37 ` Eli Zaretskii
2012-06-15 6:39 ` Dov Grobgeld [this message]
2012-06-15 8:38 ` bug#11700: [O] " Eli Zaretskii
2017-12-04 20:27 ` Nicolas Goaziou
2017-12-04 20:35 ` Dov Grobgeld
2017-12-04 20:43 ` Eli Zaretskii
2017-12-04 20:53 ` Eli Zaretskii
2017-12-04 20:45 ` Eli Zaretskii
[not found] ` <83374qxlwp.fsf@gnu.org>
2017-12-04 21:02 ` Nicolas Goaziou
2017-12-08 9:28 ` Eli Zaretskii
[not found] ` <83zi6twotx.fsf__4220.56812462888$1512725457$gmane$org@gnu.org>
2017-12-08 17:08 ` Nicolas Goaziou
[not found] ` <87mv2trvti.fsf@nicolasgoaziou.fr>
2017-12-23 13:38 ` Eli Zaretskii
2017-12-23 13:48 ` Eli Zaretskii
2017-12-23 22:51 ` Nicolas Goaziou
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='CA++fsGEZ4hpgYQ=12vnHryS9LJbqycGHnuWs5JN5G0M776p6Gw@mail.gmail.com' \
--to=dov.grobgeld@gmail.com \
--cc=11700@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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).