From: Eli Zaretskii <eliz@gnu.org>
To: Sean O'Halpin <sean.ohalpin@gmail.com>
Cc: emacs-orgmode@gnu.org, carsten.dominik@gmail.com
Subject: Re: Enriched/Org is a colorful Org
Date: Sat, 13 Apr 2013 18:01:52 +0300 [thread overview]
Message-ID: <8361zq8of3.fsf@gnu.org> (raw)
In-Reply-To: <CAOXM+eWzPk9FB3KdSQmmLa=UFhYT6uk5qNRr+mMh=VvbG3S6Zg@mail.gmail.com>
> Date: Sat, 13 Apr 2013 13:24:13 +0100
> From: "Sean O'Halpin" <sean.ohalpin@gmail.com>
> Cc: Carsten Dominik <carsten.dominik@gmail.com>, Org Mode <emacs-orgmode@gnu.org>
>
> In your opinion, would it be possible to reproduce the functionality
> of outline-mode using text properties rather than overlays?
This needs to be analyzed. Outline mode uses several features that
are specific to overlays, but not to text properties:
isearch-open-invisible and front-advance. (It also uses 'evaporate',
but that happens automatically with text properties.) I think
front-advance will happen automatically, but searching inside
invisible text is currently supported only for overlays (for reasons
that I consider irrelevant, but that's me).
> And in the case of org-mode, would this really make that much of a
> difference in terms of performance?
I don't know, because I didn't measure that, and neither did I see any
measurements published. If there are many overlays in a buffer,
redisplay performance will certainly be better with text properties,
but I don't know whether this improvement will be significant: there
could be other factors at work that affect performance to a much
greater effect. If we want to know for sure, there's no way around
profiling this. Luckily, we now have profiler.el to help us.
next prev parent reply other threads:[~2013-04-13 15:01 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 4:02 Enriched/Org is a colorful Org Jambunathan K
2013-04-10 9:54 ` Suvayu Ali
2013-04-10 10:16 ` Carsten Dominik
2013-04-10 10:39 ` Torsten Wagner
2013-04-10 10:48 ` Suvayu Ali
2013-04-10 10:53 ` Carsten Dominik
2013-04-10 11:20 ` Sebastien Vauban
2013-04-10 11:26 ` Carsten Dominik
2013-04-10 12:15 ` Jambunathan K
2013-04-10 11:57 ` Jambunathan K
2013-04-10 16:21 ` Eli Zaretskii
2013-04-10 16:43 ` Jambunathan K
2013-04-10 17:13 ` Eli Zaretskii
2013-04-10 19:58 ` Carsten Dominik
2013-04-10 20:16 ` Sebastien Vauban
2013-04-11 2:58 ` Carsten Dominik
2013-04-11 17:30 ` Eli Zaretskii
2013-04-11 22:49 ` Carsten Dominik
2013-04-12 6:41 ` Eli Zaretskii
2013-04-12 7:13 ` Carsten Dominik
2013-04-12 8:31 ` Eli Zaretskii
2013-04-12 10:56 ` Carsten Dominik
2013-04-12 11:49 ` Torsten Wagner
2013-04-12 13:03 ` Eli Zaretskii
2013-04-12 18:00 ` Suvayu Ali
2013-04-12 18:38 ` Eli Zaretskii
2013-04-13 10:50 ` Suvayu Ali
2013-04-12 12:36 ` Eli Zaretskii
2013-04-13 12:24 ` Sean O'Halpin
2013-04-13 14:38 ` Jambunathan K
2013-04-13 15:01 ` Eli Zaretskii [this message]
2013-04-12 8:35 ` Bastien
2013-04-12 14:45 ` François Pinard
2013-04-18 20:37 ` Samuel Wales
2013-04-11 17:27 ` Eli Zaretskii
2013-04-11 22:46 ` Carsten Dominik
2013-04-10 12:12 ` Jambunathan K
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8361zq8of3.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sean.ohalpin@gmail.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/org-mode.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).