unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
Cc: eli.osherovich@gmail.com, md5i@md5i.com, emacs-devel@gnu.org,
	emacs-bidi@gnu.org, miles@gnu.org
Subject: Re: [emacs-bidi] Re: improving bidi documents display
Date: Thu, 03 Mar 2011 05:40:13 -0500	[thread overview]
Message-ID: <E1Pv5x7-000267-7R@fencepost.gnu.org> (raw)
In-Reply-To: <4D6F30FA.6020807@it.aoyama.ac.jp> (message from "Martin J. Dürst" on Thu, 03 Mar 2011 15:11:06 +0900)

> Date: Thu, 03 Mar 2011 15:11:06 +0900
> From: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
> CC: Miles Bader <miles@gnu.org>, eli.osherovich@gmail.com, md5i@md5i.com,
>         emacs-bidi@gnu.org, emacs-devel@gnu.org
> 
> >> But isn't the "changed order" natural for the characters it's attached
> >> to?
> >
> > Only in the context of the kind of text (e.g., TeX) it was copied
> > from.
> 
> The copying may work if the feature is switched on for all buffers.

What feature is that?

> The 
> reason for this is that things have to be reevaluated/fixed anyway every 
> time some buffer changes (e.g. insertion or deletion of a character) 
> happens. So if the text is copied to a buffer that doesn't do any 
> explicit reordering on top of the bidi algorithm, the special 
> overlays/properties/whatever will just be purged out.

This is probably a misunderstanding, prompted by the fact that we are
discussing an imaginary feature.

I was talking about a special text property which tells the display
engine to reorder the characters covered by the property.  By default,
text properties are yanked together with the text.  And since yanking
text (as any other insertion) triggers redisplay, the display engine
_will_ notice this special property and _will_ reorder the text it
covers.

As for a buffer that "doesn't do any explicit reordering", I'm not
sure what you mean.  The current plans are to turn on the bidi
reordering in all buffers by default.  Whether this constitutes
"explicit reordering", I'm not sure, so I don't understand what you
mean, and I also don't see how is that relevant to the effect of
copying the text properties.

If you suggest that this specific property should be stripped off by
yanking, i.e. to add them to yank-excluded-properties, then it's
possible, but not necessarily DWIM-ish, because yanking in the same
buffer would need to leave these properties intact.



  reply	other threads:[~2011-03-03 10:40 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-24 12:32 improving bidi documents display Eli Osherovich
2011-02-24 19:54 ` Eli Zaretskii
2011-02-27 10:01   ` Michael Welsh Duggan
2011-02-27 10:34     ` "Martin J. Dürst"
2011-02-27 21:19       ` Eli Zaretskii
2011-03-02  1:50         ` "Martin J. Dürst"
2011-03-02  4:02           ` Eli Zaretskii
2011-03-04 10:34             ` [emacs-bidi] " "Martin J. Dürst"
2011-02-27 21:15     ` Eli Zaretskii
2011-02-28  1:10       ` Miles Bader
2011-02-28  4:02         ` Eli Zaretskii
2011-03-02  0:58       ` James Cloos
2011-03-02 18:59         ` Eli Zaretskii
2011-03-02  2:09       ` [emacs-bidi] " "Martin J. Dürst"
2011-03-02  2:39         ` Miles Bader
2011-03-02  4:03           ` Eli Zaretskii
2011-03-02  7:06             ` Miles Bader
2011-03-02 18:39               ` Eli Zaretskii
2011-03-03  1:32                 ` Miles Bader
2011-03-03  4:07                   ` Eli Zaretskii
2011-03-03  6:11                     ` "Martin J. Dürst"
2011-03-03 10:40                       ` Eli Zaretskii [this message]
2011-03-04 10:34                         ` "Martin J. Dürst"
2011-03-04  3:58                 ` Stefan Monnier
2011-03-04  8:04                   ` Eli Zaretskii
2011-03-04  4:25                 ` Miles Bader
2011-03-04  9:52                   ` Eli Zaretskii

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=E1Pv5x7-000267-7R@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=duerst@it.aoyama.ac.jp \
    --cc=eli.osherovich@gmail.com \
    --cc=emacs-bidi@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=md5i@md5i.com \
    --cc=miles@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).