all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-bidi@gnu.org, emacs-devel@gnu.org
Subject: Re: Bidirectional editing in Emacs -- main design decisions
Date: Tue, 19 Apr 2011 10:11:33 -0300	[thread overview]
Message-ID: <jwvbp02wfnd.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <8362qbsj7p.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 18 Apr 2011 17:54:50 +0300")

> After careful thought, I changed my mind about this part.  Whenever
> the redisplay iterator finds text that is covered by a `display' text
> property or by an overlay with a `display', `before-string', or
> `after-string' property, it will not stop reordering.  Instead, it
> will treat the entire run of text covered by the text property or
> overlay as a single atomic entity, and will reorder it as if it were a
> single special character whose name in Unicode is OBJECT REPLACEMENT
> CHARACTER (u+FFFC).  This character's bidirectional category (Other
> Neutral) and other properties are designed so that it can stand for
> display features such as embedded images, and in particular it is
> reordered as appropriate for such embedded objects.

> This will reorder images and display strings in the same way wrt
> surrounding text, which I think is reasonable.  It is also in line
> with the pre-Emacs 24 unidirectional display engine, which skipped the
> text covered by such properties in one go, after displaying the image
> or a display string specified by the property.

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


        Stefan



  reply	other threads:[~2011-04-19 13:11 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 [this message]
2011-04-19 16:02     ` Eli Zaretskii
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

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

  git send-email \
    --in-reply-to=jwvbp02wfnd.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=eliz@gnu.org \
    --cc=emacs-bidi@gnu.org \
    --cc=emacs-devel@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.