From: Miles Bader <miles@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: eli.osherovich@gmail.com, md5i@md5i.com, emacs-bidi@gnu.org,
emacs-devel@gnu.org
Subject: Re: improving bidi documents display
Date: Wed, 02 Mar 2011 16:06:10 +0900 [thread overview]
Message-ID: <buozkpexaql.fsf@dhlpc061.dev.necel.com> (raw)
In-Reply-To: <83k4gixj6m.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> Adding/changing text properties marks the buffer as "modified."
>>
>> One can avoid that effect by using the `with-silent-modifications' macro.
>
> Yes, but then copying the text copies the properties with it, which is
> not what you want in this case, in general.
Sure, but that's a general issue in Emacs, so there are already
mechanisms in place to help deal with it
(e.g. yank-excluded-properties).
-Miles
--
Back, n. That part of your friend which it is your privilege to contemplate in
your adversity.
next prev parent reply other threads:[~2011-03-02 7:06 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 [this message]
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
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=buozkpexaql.fsf@dhlpc061.dev.necel.com \
--to=miles@gnu.org \
--cc=eli.osherovich@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-bidi@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=md5i@md5i.com \
/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).