From: Ihor Radchenko <yantar92@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jnorden@math.tntech.edu, emacs-devel@gnu.org
Subject: Re: A question about overlays and performance.
Date: Sun, 26 Jul 2020 22:19:52 +0800 [thread overview]
Message-ID: <87y2n6nyt3.fsf@localhost> (raw)
In-Reply-To: <83pn8ibcs9.fsf@gnu.org>
> So what kind of guidelines did you want to hear regarding these
> issues?
Mostly wanted to know if there is a known way to solve these issues.
If there is, it may be a good idea to describe it briefly in the manual.
If not, I was thinking about writing a patch/feature request to solve
these issues.
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Ihor Radchenko <yantar92@gmail.com>
>> Cc: emacs-devel@gnu.org
>> Date: Sun, 26 Jul 2020 09:33:21 +0800
>>
>> Not directly related to the initial question here, but may I ask if
>> there are any practical guidelines to convert overlays to text
>> properties? I am specifically concerned about two issues when we want to
>> use text properties instead of overlays to hide text in buffer (pointing
>> at org-mode):
>> - text hidden via text properties is not well-handled by isearch. For
>> overlays, isearch can temporary reveal the hidden text, which is not
>> the case for text hidden using 'invisible text property.
>> - text properties are not buffer-local in indirect buffers. With
>> overlays, it is possible to have define hidden text in basic and
>> indirect buffer independently. However, text properties will always be
>> shared and the text hidden in indirect buffer will automatically be
>> hidden in the base buffer as well.
>
> So what kind of guidelines did you want to hear regarding these
> issues?
--
Ihor Radchenko,
PhD,
Center for Advancing Materials Performance from the Nanoscale (CAMP-nano)
State Key Laboratory for Mechanical Behavior of Materials, Xi'an Jiaotong University, Xi'an, China
Email: yantar92@gmail.com, ihor_radchenko@alumni.sutd.edu.sg
next prev parent reply other threads:[~2020-07-26 14:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-25 16:40 A question about overlays and performance Jeff Norden
2020-07-25 16:53 ` Eli Zaretskii
2020-07-25 17:24 ` Jeff Norden
2020-07-25 17:29 ` Eli Zaretskii
2020-07-26 1:33 ` Ihor Radchenko
2020-07-26 13:56 ` Eli Zaretskii
2020-07-26 14:19 ` Ihor Radchenko [this message]
2020-07-26 14:44 ` Stefan Monnier
2020-07-27 11:20 ` Ihor Radchenko
2020-07-28 16:43 ` Jeff Norden
2020-07-28 16:58 ` Yuan Fu
2020-07-28 17:05 ` Eric Abrahamsen
2020-07-29 1:52 ` Ihor Radchenko
2020-07-30 18:21 ` Jeff Norden
2020-07-28 23:53 ` Juri Linkov
2020-07-29 1:36 ` Ihor Radchenko
2020-07-30 23:04 ` Juri Linkov
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=87y2n6nyt3.fsf@localhost \
--to=yantar92@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jnorden@math.tntech.edu \
/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).