From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eli.osherovich@gmail.com, md5i@md5i.com, emacs-devel@gnu.org,
emacs-bidi@gnu.org, Miles Bader <miles@gnu.org>
Subject: Re: improving bidi documents display
Date: Thu, 03 Mar 2011 22:58:32 -0500 [thread overview]
Message-ID: <jwv7hcfy1up.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83aahdxt74.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 02 Mar 2011 20:39:43 +0200")
> This one's different, believe me: no other text property changes the
> _order_ of characters on display in creative ways. It could easily
> render the text illegible, under just the right circumstances. Other
> text properties are either non-intrusive, or are almost immediately
> fixed by JIT Lock, or are simply rare enough to not get in our way.
But isn't it the case that the properties we'd add in this case would
also be added via jit-lock? So they'd very naturally belong in
yank-excluded-properties.
Stefan
next prev parent reply other threads:[~2011-03-04 3:58 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 ` [emacs-bidi] " Eli Zaretskii
2011-03-04 10:34 ` "Martin J. Dürst"
2011-03-04 3:58 ` Stefan Monnier [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=jwv7hcfy1up.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=eli.osherovich@gmail.com \
--cc=eliz@gnu.org \
--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 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.