From: Eli Zaretskii <eliz@gnu.org>
To: mail@nicolasgoaziou.fr
Cc: dov.grobgeld@gmail.com, 11700@debbugs.gnu.org
Subject: bug#11700: 24.1.50; Bad interaction between BiDi and org-tables
Date: Sat, 23 Dec 2017 15:48:32 +0200 [thread overview]
Message-ID: <83vagxk11r.fsf@gnu.org> (raw)
In-Reply-To: <83y3ltk1j0.fsf@gnu.org> (message from Eli Zaretskii on Sat, 23 Dec 2017 15:38:11 +0200)
> Date: Sat, 23 Dec 2017 15:38:11 +0200
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: dov.grobgeld@gmail.com, 11700@debbugs.gnu.org
>
> I found both methods doing well, so I'm going to show both, and let
> you decide which one is better.
On second thought, I think Method 2 is better, because it does exactly
what segment separators were invented for: to separate cells in
tables. By contrast, the bidi formatting control characters are for
controlling the display order in general text, not necessarily in
tables.
next prev parent reply other threads:[~2017-12-23 13:48 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 ` bug#11700: [O] " Dov Grobgeld
2012-06-15 8:38 ` 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 [this message]
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=83vagxk11r.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=11700@debbugs.gnu.org \
--cc=dov.grobgeld@gmail.com \
--cc=mail@nicolasgoaziou.fr \
/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).