From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-bidi@gnu.org, emacs-devel@gnu.org
Subject: Re: Bidirectional editing in Emacs -- main design decisions
Date: Tue, 19 Apr 2011 19:02:04 +0300 [thread overview]
Message-ID: <83y636grgj.fsf@gnu.org> (raw)
In-Reply-To: <jwvbp02wfnd.fsf-monnier+emacs@gnu.org>
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: emacs-devel@gnu.org, emacs-bidi@gnu.org
> Date: Tue, 19 Apr 2011 10:11:33 -0300
>
> It sounds very reasonable, but at the same time I don't understand in
> which way it differs from your earlier opinion that it should "stop
> reordering" (whose meaning is very unclear to me).
Well, that's my fault: "stop reordering" is simply misleading.
What I meant by that was that the reordering will completely process
all the text before (in the logical order) the part covered by a
display property, then process the display spec, and only then reorder
the text after the property.
So this buffer text
ABCDE display XYZ
will be reordered as
EDCBA display ZYX
instead of more sensible
ZYX display EDCBA
under the new plan.
next prev parent reply other threads:[~2011-04-19 16:02 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 21:18 Bidirectional editing in Emacs -- main design decisions Eli Zaretskii
2009-10-09 21:55 ` joakim
2009-10-09 22:29 ` Eli Zaretskii
2009-10-09 22:42 ` joakim
2009-10-10 7:08 ` Eli Zaretskii
2009-10-10 7:28 ` joakim
2009-10-10 8:20 ` Eli Zaretskii
2009-10-09 22:41 ` Eli Zaretskii
2009-10-10 9:16 ` Richard Stallman
2009-10-10 11:38 ` Eli Zaretskii
2009-10-11 8:41 ` Richard Stallman
2009-10-11 20:12 ` Eli Zaretskii
2009-10-11 21:11 ` Eli Zaretskii
2009-10-12 10:11 ` Richard Stallman
2009-10-12 18:40 ` Eli Zaretskii
2009-10-10 13:44 ` Sascha Wilde
2009-10-10 14:06 ` Eli Zaretskii
2009-10-10 15:54 ` Sascha Wilde
2009-10-10 14:57 ` Ehud Karni
2009-10-10 16:38 ` Eli Zaretskii
2009-10-10 15:13 ` Jason Rumney
2009-10-10 16:06 ` Eli Zaretskii
2009-10-10 16:29 ` Jason Rumney
2009-10-10 17:18 ` James Cloos
2009-10-10 18:33 ` Eli Zaretskii
2011-04-18 14:54 ` Eli Zaretskii
2011-04-19 13:11 ` Stefan Monnier
2011-04-19 16:02 ` Eli Zaretskii [this message]
2011-04-20 3:15 ` Stefan Monnier
2011-04-25 17:31 ` Mohsen BANAN
2011-04-25 17:58 ` Eli Zaretskii
2011-04-25 18:44 ` Mohsen BANAN
2011-04-25 18:59 ` Eli Zaretskii
2011-04-25 21:31 ` Now: Paragraph Direction Detection and Harmonization -- Was: " Mohsen BANAN
2011-04-25 22:00 ` Eli Zaretskii
2011-04-26 7:56 ` Mohsen BANAN
2011-04-26 18:05 ` Eli Zaretskii
2011-04-27 21:58 ` Now: Paragraph Direction Detection and Harmonization Mohsen BANAN
2011-04-26 18:24 ` Mohsen BANAN
2011-04-26 19:23 ` Eli Zaretskii
2011-04-26 1:22 ` Now: Paragraph Direction Detection and Harmonization -- Was: Re: Bidirectional editing in Emacs -- main design decisions Stephen J. Turnbull
2011-04-28 0:52 ` Requesting instructions for enabling bidi by default Mohsen BANAN
2011-04-28 1:21 ` Juanma Barranquero
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=83y636grgj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-bidi@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).